Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Check compatibility with relevant schemes and standards #13

Closed
joncison opened this issue Feb 19, 2016 · 10 comments
Closed

Check compatibility with relevant schemes and standards #13

joncison opened this issue Feb 19, 2016 · 10 comments
Assignees
@joncison @albangaignard

Comments

@joncison
Copy link
Member

joncison commented Feb 19, 2016 •
edited
Loading

Including:
@joncison
Copy link
Member Author

NB @matuskalas & @hmenager : this would be required for the publication I think

@joncison
Copy link
Member Author

joncison commented Nov 30, 2017 •
edited
Loading

cc @albangaignard - see above!

Also see the spreadsheet on the mapping work done within BioSchema:
https://docs.google.com/spreadsheets/d/1D0aQl-Ocp8Fi7a-drKV1Faed6tYUgGwzEM8xypa8S2Y/edit#gid=1261485211

And the closely related #21

@joncison
Copy link
Member Author

joncison commented Dec 4, 2017 •
edited
Loading

Chris Morris says ...
"Have you considered making bio.tools compatible with OpenAIRE? It already has more or less the right metadata, but would probably need to present it differently:
https://guidelines.openaire.eu/en/latest/data/index.html
This would benefit depositors by providing an automated route for software outputs to appear on their project dashboard along with publications - and therefore provide an incentive to deposit a description on bio.tools.

I have suggested to OpenAIRE that they add "web application" as a new category of project output."

@joncison
Copy link
Member Author

joncison commented Dec 4, 2017

@albangaignard OpenAIRE makes heavy use of Dublin Core so I think is very useful for the analysis of other vocabularies / mapping in biotoolsSchema being done in context of https://github.com/bio-tools/biotoolsRdf. cc @matuskalas FHI.

@alessiabardi
Copy link

Hi all, this is Alessia from OpenAIRE. As @joncison requested by email I am adding here the list of fields that will be available in the OpenAIRE guidelines for software:
Property (optionality) | Datacite metadata field
where optionality is one of M(andatory), R(ecommended), O(ptional):

  1. Identifier (M) | datacite:identifier
  2. Author (M) | datacite:creator
  3. Contact Person (O) | datacite:contributor
  4. Contact Group (O) | datacite:contributor
  5. Name (M) | datacite:title
  6. Repository (R) | datacite:publisher
  7. Software Type (M) | datacite:resourceType
  8. Subject (R) | datacite:subject
  9. Release date (R) | datacite:date
  10. Description language (O) | datacite:language
  11. Alternate identifier (O) | datacite:alternateIdentifier
  12. Landing page (R) | datacite:alternateIdentifier
  13. Distribution location (R) | datacite:alternateIdentifier
  14. Documentation (R) | datacite:relatedIdentifier
  15. RelatedIdentifier (O) | datacite:relatedIdentifier
  16. Programming Language (R) | datacite:format
  17. Version Number (R) | datacite:version
  18. Access Rights (M) | datacite:rights
  19. Licence Condition (R) | datacite:rights
  20. Description (R) | datacite:description
  21. Tool (R) | datacite:description
  22. Funding Reference (R) | datacite:fundingReference
  23. Distribution form (O) | datacite:description

@joncison
Copy link
Member Author

joncison commented Dec 6, 2017

Thanks Alessia, very helpful! In the 1st instance we'll look at mapping this to biotoolSchema fields and then formally annotating that mapping in the XSD itself (which is a prelude to other things, that can come later...)

@joncison joncison mentioned this issue Nov 16, 2018
Open
@joncison
Copy link
Member Author

Hi @alessiabardi

Quick question: which of these should I be looking at:

  1. https://guidelines.openaire.eu/en/latest/data/application_profile.html
  2. https://software-guidelines.readthedocs.io/en/latest/application_profile.html

?

I assume the first is more up-to-date?

Cheers !

@alessiabardi
Copy link

The first link is for the guideline for Data Archive managers.
The second link is for the guideline for Software Software Repository Managers.
We also have a third guideline for "other types of research products" (https://guidelines-other-products.readthedocs.io), which is meant for research products that are not scientific publication, software and datasets. Examples are tools, methods, protocols, research objects, workflows.

On OpenAIRE side, we are already collecting from bio.tools API and we are considering the metadata to be descriptions of software. If you think that's correct, then you should use the software guideline. The guidelines for software and other products are not yet finalised and we welcome feedback and suggestion, so feel free to open issues on the relative github project (you'll find the link at the top of the guideline pages) or write to me and @mirima2.

@joncison
Copy link
Member Author

OK .. thanks a a lot for the clarification. Software Guidelines look good, but I'll get back on a few points soon.

@joncison
Copy link
Member Author

joncison commented Nov 30, 2018 •
edited
Loading

UPDATE

closing this cc @matuskalas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joncison joncison

@albangaignard albangaignard

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@joncison @albangaignard @alessiabardi