-
Notifications
You must be signed in to change notification settings - Fork 93
Add spase crosswalk #367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add spase crosswalk #367
Conversation
|
Thanks for your rapid response, @progval. @BaptisteCecconi asked me to review this, and I would like to make sure we are not missing other predicates. Please let me have a look this week and comment here. Thanks!! |
|
@dgarijo Thanks for taking a look at this, and thanks @BaptisteCecconi for working on this. One critical problem in SPASE is that external vocabularies are not supported, which is one of many reasons we cannot use SPASE as the metadata structure for the Heliophysics Software Search Interface. Perhaps the structure we design for that search interface will be what is used in SPASE 3.0 for software, but that remains to be seen. Because of those problems, I don't see much value in adding SPASE to CodeMeta's crosswalks, but it would be useful to see what other concepts are missing for software in SPASE. I expect to be in contact once we have our structure drafted in the coming months. |
|
Hi @rebeccaringuette, I agree with your statements. The crosswalk I initiated should really be seen as a way to see what is missing on our side, as you say. |
|
Hi Rebecca,
I think it is still useful because with this mapping we can convert spase
records into codemeta records (very useful eg when building a search engine
;) ). This is by no means attempting to replace spase.
And as Baptiste points out, it may inspire future fields in the spase
specification.
El mar., 15 oct. 2024 11:42 p. m., Rebecca Ringuette <
***@***.***> escribió:
… @dgarijo <https://github.com/dgarijo> Thanks for taking a look at this.
One critical problem in SPASE is that external vocabularies are not
supported, which is one of many reasons we cannot use SPASE as the metadata
structure for the Heliophysics Software Search Interface. Perhaps the
structure we design for that search interface will be what is used in SPASE
3.0 for software, but that remains to be seen. Because of those problems, I
don't see much value in adding SPASE to CodeMeta's crosswalks, but it would
be useful to see what other concepts are missing for software in SPASE. I
expect to be in contact once we have our structure drafted in the coming
months.
—
Reply to this email directly, view it on GitHub
<#367 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALTIGXLA3XGCG7LPMFZHJ3Z3WD4PAVCNFSM6AAAAABP64AQUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJVGIYTOOBWGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
dgarijo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @BaptisteCecconi can you please check my suggestions?
I completed them based on the information and definitions in https://spase-group.org/data/model/spase-2.6.1/index.html
|
@BaptisteCecconi some of my suggestions are duplicated with comments in text, sorry. I started doing suggestions halfway through since you can commit them if you like them |
|
@progval please have a quick look to see whether you approve with my suggestions whenever you have the chance. Sorry it took a bit longer than expected. |
|
What about the other suggestions?
El jue., 24 oct. 2024 11:05 p. m., Daniel Garijo ***@***.***>
escribió:
… Ok, feel free to ignore this then
El jue., 24 oct. 2024 11:04 p. m., Baptiste Cecconi <
***@***.***> escribió:
> ***@***.**** commented on this pull request.
> ------------------------------
>
> In crosswalks/spase-v2.6.1.csv
> <#367 (comment)>:
>
> > +isAccessibleForFree,
> +isPartOf,
> +hasPart,
> +position,
> +description,ResourceHeader/Description
> +identifier,ResourceID
> +name,ResourceHeader/ResourceName
> +sameAs,
> +url,
> +relatedLink,
> +givenName,
> +familyName,
> +email,
> +affiliation,
> +identifier,ResourceHeader/DOI
> +name,
>
> not sure. I checked the other cross walks, and there are duplicate name
> entries in the CSV (see, e.g., DataCite.csv). Line 47 is the resource name,
> while line 56 is the creator name. That might be an issue, indeed.
>
> —
> Reply to this email directly, view it on GitHub
> <#367 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AALTIGUPOCSVWMVUCA2KAQDZ5FOGJAVCNFSM6AAAAABP64AQUCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGOJTG4YDINRVGY>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Co-authored-by: Daniel Garijo <[email protected]>
Co-authored-by: Daniel Garijo <[email protected]>
Co-authored-by: Daniel Garijo <[email protected]>
|
Thanks @BaptisteCecconi, if you have questions/comments on the remaining ones let me know |
Update after comments from @dgarijo
|
@dgarijo I updated all fields according to your comments. The only remaining issue may be the "funding" term, which could be mapped to 2 entities in SPASE (as you propose). I put a human readable process in the CSV (probably not a good thing for you :-) |
|
Thanks! |
dgarijo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I leave this to @progval to decide. I think the line funding,ResourceHeader/Funding/AwardNumber or ResourceHeader/Funding/Project (if no AwardNumber) will likely cause problems. It's a tricky one.
|
In other crosswalks (SPDX, Leiningen, NodeJS, Cabal, CFF) we use No need for the parenthesis at the end, IMO. Translations to Codemeta can have both values. |
|
@progval if no further changes are required, can you merge this PR? |
|
@BaptisteCecconi ping so we can finalize this PR? |
Co-authored-by: Val Lorentz <[email protected]>
|
This is good to go for me. |
Co-authored-by: Daniel Garijo <[email protected]> Co-authored-by: Val Lorentz <[email protected]>
Following the presentation about CodeMeta by @dgarijo at the DASH meeting (heliophysics community) this morning, I prepared a first draft for a crosswalk between CodeMeta and SPASE (Space Physics Extract Search and Extract).
SPASE is an information model (a schema) to describe resources in heliophysics. SPASE resource types are Person, Instrument, Observatory, NumericalData, Repository, Software, etc.
The full schema is available here: https://spase-group.org/data/index.html
It is serialised as an XML schema (see here for the various versions).
An interactive web view of the Software class of the schema is available here.
I copy below the list of metadata element for the Software class in a flat view:
And here is an example of SPASE record for a Software:
https://hpde.io/CCMC/Software/Kamodo.html