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.

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

Link to FAIRSharing metrics #156

Open
dgarijo opened this issue Feb 18, 2025 · 4 comments
Open

Link to FAIRSharing metrics #156

dgarijo opened this issue Feb 18, 2025 · 4 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@dgarijo
Copy link
Member

dgarijo commented Feb 18, 2025

They are ingesting some of our tests. I would like to explicitly state that some of our metrics have equivalents in fairsharing.
We need to figure out how to do this.

@dgarijo dgarijo added documentation Improvements or additions to documentation enhancement New feature or request labels Feb 18, 2025
@allysonlister
Copy link

I am happy to start making some records, but we need to decide on OSTrails/FAIR_assessment_output_specification#34 before I can. I see there have not been any additional comments after I created the ticket, I will ping people on there and we can hopefully talk about it at one of the meetings we have for OSTrails this week. Thanks!

@allysonlister
Copy link

allysonlister commented Mar 4, 2025

(Note that records in FAIRsharing are not the things themselves, but descriptions of the thing. So a metric record in FAIRsharing describes one of @dgarijo's metrics, but is not equivalent to it). However I, too, wish to start explicitly linking metrics in FAIRsharing with @dgarijo's metrics, so let's get to it!

In the interests of getting this moving, I have used the consensus so far in the hierarchy ticket mentioned above to start creating records; modifications can be made to all FAIR principles, metrics and benchmarks records in FAIRsharing if final decisions vary from what is already there. I have marked the records in FAIRsharing as 'in development' to prevent the creation of DOIs until we're happy.

Note that I have updated and extended the mapping between FOOPS! metrics and FAIRsharing metrics records within our sharepoint document. We need to address the outstanding issues within this mapping in order to progress to automated pushing/pulling of metrics records into FAIRsharing.

Here's a small snippet of the FAIR principles together with two example metrics, with metadata taken according to conversations within OSTrails and with GO-FAIR (via Erik Schultes) to ensure community consensus around how principles are represented in FAIRsharing.

  • FAIR Principles - Findable (Abbreviation FAIR - F) - https://fairsharing.org/6269
    • FAIR Principles F1: (Meta)data are assigned globally unique and persistent identifiers (Abbreviation: FAIR F1). https://fairsharing.org/6273 Note: If a test ran this as a compound principle, but the code failed on one, we wouldn't know which one it would fail on. Further the actual implemented tests for globally unique and persistent would quite often be different. Therefore these have been separated into sub-principles.
    • FAIR Principles F2: Data are described with rich metadata (Abbreviation: FAIR F2) https://fairsharing.org/6276
    • FAIR Principles F3: Metadata clearly and explicitly include the identifier of the data they describe (Abbreviation: FAIR F3) https://fairsharing.org/6277
    • FAIR Principles F4: (meta)data are registered or indexed in a searchable resource: https://fairsharing.org/6278

Outstanding questions:

  1. consensus on mapping of metrics (see onedrive link above)
  2. final FAIR hierarchy discussion and resolution of FAIR Principles Hierarchy - discussion requested OSTrails/FAIR_assessment_output_specification#34
  3. How to link out to tests related to a metric from a FAIRsharing metrics record.

What do you think so far? Happy to talk about this during this week, as I am NOT attending the GA in person.

Referencing @knirirr for his information.

@dgarijo
Copy link
Member Author

dgarijo commented Mar 9, 2025

Thanks @allysonlister.
Let me have a look at the issues and come back to you. I am sad to hear you won't be at the GAM :(

@allysonlister
Copy link

I wish I could go @dgarijo but I have various family appointments and events that cannot be postponed, otherwise I would have enjoyed attending and seeing you and everyone in person. @knirirr and Susanna will be there.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants