Skip to content

FAIR score maximization #2942

@carlinmack

Description

@carlinmack

Tasks identified from issues

    "application/marcxml+xml": ResponseHandler(MARCXMLSerializer(), headers=etag_headers),
    "application/vnd.datacite.datacite+xml": ResponseHandler(DataCite43XMLSerializer(), headers=etag_headers),
    "application/x-dc+xml": ResponseHandler(DublinCoreXMLSerializer(), headers=etag_headers),
    "application/dcat+xml": ResponseHandler(DCATSerializer(), headers=etag_headers),
  • Could not find dcterms:accessRights information in metadata
    I don't think this is applicable. I could imagine "Open metadata, restricted files" and variations thereof but I'm not sure if that would be expected
Image - I will check what other people do
  • No info about file size available in given metadata for files
    Tested with ngrok from local system, adding file size to the headers did not work. The test here seems to suggest that it is picked up from the header.

    • Implement DataCite's size and format fields (and see if that's something that their code detects)
  • Could not verify content type from downloaded files
    Could not find how to modify the current content type. (Will look into this further) This is only valid for datasets.

    • Implement DataCite's size and format fields (and see if that's something that their code detects)
  • Formal provenance metadata is unavailable

  • Predicates metadata should resolve to Linked Data data

  • Persistence policy not identified

  • GUID does not conform with any known permanent-URL system

  • dcat: Missing discoverability oriented metadata


Using:

Issue F-UJI FAIR Checker FAIR Evaluator FAIR Enough OpenAIRE Validator
Score (averaged) 79% 92% 64% 72% 80%
F1: Persistence of identifier
F2A: Structured metadata
F3: Metadata identifier in metadata
F4: Searchable ⏺️ (no fix needed) ⏺️ (no fix needed)
A1.1 Uses an open free protocol for data retrieval, Data authentication and authoriazatio
A2: Metadata persistence
FsF-I2-01M - Metadata uses semantic resources
I1: Machine readable format
I2: Metadata users FAIR vocabularies
FsF-R1-01MD - Metadata specifies the content of the data.
R1.1 Metadata includes license
FsF-R1.2-01M - Metadata includes provenance information about data creation or generation.
FsF-R1.3-02D - Data is available in a file format recommended by the target research community.
Notes:
  • F-UJI
  • FAIR Checker
    • Score: 91.67%
    • F: 87.5%
      • F2A: Structured metadata
        • You should provide discoverability oriented metadata with one of the following properties: dct:title dct:description dcat:accessURL dcat:downloadURL dcat:endpointDescription dcat:endpointURL
    • A: 100%
    • I: 83.3%
      • I1: Machine readable format
        • You should provide discoverability oriented metadata with one of the following properties: dct:title dct:description dcat:accessURL dcat:downloadURL dcat:endpointDescription dcat:endpointURL
    • R: 100%
  • FAIR Evaluator
    • Evaluation: https://fairsharing.github.io/FAIR-Evaluator-FrontEnd/#!/evaluations/17230
    • Score: 14/22 64%
    • F
      • Data Identifier Persistence - FAILURE: The GUID does not conform with any known permanent-URL system.
      • FAILURE: While (apparent) metadata record identifiers were found (["www.biorxiv.org/content/10.1101/2020.04.11.037093v2", "www.biorxiv.org/content/10.1101/2020.04.11.037093v2"]) none of them matched the initial GUID provided to the test (https://doi.org/10.5281/zenodo.3723281). Exact identifier match is required.
      • FAILURE: Was unable to discover the metadata record by search in Bing using any method
        • I feel like this isn't going to work as we use concept ID to test
    • A:
    • I:
      • FAILURE: The url https://zenodo.org/api/records/7559361/files/articles_by_influence.csv/content failed to resolve via a HEAD call with headers {"Accept"=>"text/turtle, application/ld+json, application/rdf+xml, text/xhtml+xml, application/n3, application/rdf+n3, application/turtle, application/x-turtle, text/n3, text/turtle, text/rdf+n3, text/rdf+turtle, application/n-triples"}, therefore we cannot continue FAILURE: the data could not be found, or does not appear to be in a recognized knowledge representation language.
      • FAILURE: 0 of a total of 33 predicates discovered in the metadata resolved to Linked Data data. The minimum to pass this test is 2/3 (with a minimum of 3 predicates in total).
    • R:
      • FAILURE: No License property was found in the metadata.
  • FAIR Enough
    • fair-enough-metadata, fair-evaluator-maturity-indicators, fair-enough-data
    • Score: 87.5%, 63.6%, 63.6%
    • F:
      • WARN: Unable to resolve https://doi.org/10.5281/zenodo.3723281 using HTTP Accept header {"Accept"=>"text/xhtml,text/xml"}. FAILURE: The GUID does not conform with any known permanent-URL system.
      • FAILURE: [2024-12-12T13:14:21] Could not find links to the metadata identifier None in the RDF metadata
      • WARN: HTTP error 406 Not Acceptable encountered when trying to resolve https://doi.org/10.5281/zenodo.3723281. WARN: Unable to resolve https://doi.org/10.5281/zenodo.3723281 using HTTP Accept header {"Accept"=>"text/xhtml,text/xml"}. FAILURE: While (apparent) metadata record identifiers were found (["www.biorxiv.org/content/10.1101/2020.04.11.037093v2", "www.biorxiv.org/content/10.1101/2020.04.11.037093v2"]) none of them matched the initial GUID provided to the test (https://doi.org/10.5281/zenodo.3723281). Exact identifier match is required.
      • FAILURE: Was unable to discover the metadata record by search in Bing using any method
    • A:
      • FAILURE: [2024-12-12T13:14:20] Could not find a persistence policy in the metadata. Searched for the following predicates: ['http://www.w3.org/2000/10/swap/pim/doc#persistencePolicy']
      • FAILURE: [2024-12-12T13:31:45] Could not find the data URI in the subject metadata.
      • FAILURE: [2024-12-12T13:31:45] Could not find the data URI in the subject metadata. WARN: [2024-12-12T13:31:45] Could not find dcterms:accessRights information in metadata. Make sure your metadata contains informations about access rights using one of those predicates: http://purl.org/dc/terms/accessRights
    • I:
      • WARN: Unable to resolve https://doi.org/10.5281/zenodo.3723281 using HTTP Accept header {"Accept"=>"text/xhtml,text/xml"}. FAILURE: The url https://zenodo.org/api/records/7559361/files/articles_by_influence.csv/content failed to resolve via a HEAD call with headers {"Accept"=>"text/turtle, application/ld+json, application/rdf+xml, text/xhtml+xml, application/n3, application/rdf+n3, application/turtle, application/x-turtle, text/n3, text/turtle, text/rdf+n3, text/rdf+turtle, application/n-triples"}, therefore we cannot continue. FAILURE: the data could not be found, or does not appear to be in a recognized knowledge representation language.
      • WARN: Unable to resolve https://doi.org/10.5281/zenodo.3723281 using HTTP Accept header {"Accept"=>"text/xhtml,text/xml"}. WARN: predicate http://schema.org/affiliation was not found as the SUBJECT of a triple, indicating that it did not resolve to its definition. WARN: predicate http://ogp.me/ns#description did not resolve to linked data. WARN: predicate http://ogp.me/ns#description was not found as the SUBJECT of a triple, indicating that it did not resolve to its definition. FAILURE: 0 of a total of 33 predicates discovered in the metadata resolved to Linked Data data. The minimum to pass this test is 2/3 (with a minimum of 3 predicates in total).
    • R:
      • WARN: Unable to resolve https://doi.org/10.5281/zenodo.3723281 using HTTP Accept header {"Accept"=>"text/xhtml,text/xml"}. WARN: did not find a schema:license predicate that followed the Schema.org license range structure. FAILURE: No License property was found in the metadata.
  • OpenAIRE Validator
    • Score for content: 88%
      • Metadata uses knowledge representation expressed in standardised format.
      • Metadata refers to a reuse license
    • Score for usage: 72%
      • OpenAIRE expects metadata to be encoded in the OpenAIRE metadata format (metadataPrefix oai_openaire) .
      • OpenAIRE expects metadata to be encoded in the CERIF_OPENAIRE metadata format (metadataPrefix oai_cerif_openaire) .

Metadata

Metadata

Assignees

No one assigned

    Labels

    staleNo activity for more than 60 days.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions