FAIRsharing Attribution

[allysonlister]

Greetings from FAIRsharing!

I recently had a look at https://bioregistry.io/ now that our new site and API have been released, and I noticed that you have been successful at using our new API, that's great! Please let us know if you have any questions.

We have a couple of comments in regards to your site and how FAIRsharing is represented.

• Attribution - in documentation. Thank you very much for listing FAIRsharing in a few places on your website, and clearly stating within the JSON downloads those parts of your metadata come from us (e.g. https://bioregistry.io/api/registry/abs?format=json). To fully attribute us in compliance with our CC BY-SA 4.0 licence, we also request that you mention FAIRsharing as a source of your metadata within your documentation, for example in a "data sources" section (together with the other sources you pull information from) on your summary page (https://bioregistry.io/summary) and in the acknowledgements (https://bioregistry.io/acknowledgements). Full details on attributing and licencing are here: https://fairsharing.org/licence.
• Attribution - in metadata sourced from FAIRsharing. We request that any data taken from FAIRsharing, either by the API, scraping the site or other means, is attributed and cited appropriately. We request that a link and the FAIRsharing logo is presented next to the data taken from FAIRsharing. Whenever the description (or other metadata) comes from FAIRsharing, a link/logo to us should be present next to the relevant metadata.
• Metadata registry. You state that Bioregistry is "A collection of metadata about registries and mappings between the resources they describe...So far, the Bioregistry is the only metaregistry.". For your information, according to this definition, FAIRsharing is most definitely a metadata registry, as are a number of other resources such as the OpenAIRE knowledge graph.

Thank you for using FAIRsharing, it's great to see how the community makes use of our registry.

Best wishes, Allyson

[cthoyt]

Hi @allysonlister, thanks for the feedback. We've made pull request #331 to address your comments. Please check out the description block of that PR where we went through your feedback point-by-point.