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

Tracking features for RDA checks: Interoperability #115

Open
12 of 17 tasks
PalomoIFCA opened this issue Jan 25, 2024 · 0 comments
Open
12 of 17 tasks

Tracking features for RDA checks: Interoperability #115

PalomoIFCA opened this issue Jan 25, 2024 · 0 comments

Comments

@PalomoIFCA
Copy link
Contributor

PalomoIFCA commented Jan 25, 2024

RDA-I1-01M

  • Check which of the metadata terms use controled vocabularies
    • license complies with SDPX codes (currently available in EPOS prod API -> license)
    • probably not a vocabulary, but a format organisation complies with ROR and PIC (to be implemented in prototype)
  • Check whether or not the metadata values comply with the vocabularies

FAIR-eva current implementation: tries to find a known controlled vocabulary in a subset of metadata elements (those defined in terms_cv), but does not check the compliance of the value with the vocabulary

RDA-I1-01D

  • file/data format metadata value complies with Internet Media Types (currently available in EPOS prod API -> availableFormats)
  • Additionally use downloadURL to check the format of the data corresponds to the file/data format

RDA-I1-02M

  • EPOS uses RDF/TTL for the knowledge representation model for the metadata. Try the current implementation of FAIR-eva (see utils.oai_metadataFormats()) knows about 'RDF/TTL' or similar

RDA-I1-02D

FAIR-eva current implementation: copies I1-02m [old]

RDA-I2-01M

  • Check if the vocabularies used have a documentation file through the configuration file
  • Check if those vocabularies have a PID (Persistent IDentifier) through the configuration file

RDA-I2-01D

  • Will not be implemented. We should choose between: (i) score = 0, or (ii) NotImplementedError
    FAIR-eva current implementation: copies I2-01m [old]

RDA-I3-01M

  • Reuse current implementation for ORCID
  • Try to find additional metadata elements that use qualified metadata: In the spreashets -> license, Related DA and Related publications

FAIR-eva current implementation: Checks a list of terms that are considered qualified references and looks if they have an ORCID [old]

RDA-I3-01D

  • Will not be implemented. We should choose between: (i) score = 0, or (ii) NotImplementedError

FAIR-eva current implementation: Copies I3-02M

RDA-I3-02M

FAIR-eva current implementation: Looks at a list of related terms and checks wheter or not they reference other digital objects

RDA-I3-02D

  • Will not be implemented. We should choose between: (i) score = 0, or (ii) NotImplementedError

FAIR-eva current implementation: Copies I3-03M [old]

RDA-I3-03M

  • Look for some qualified references: shoud be clear which metadata we consider qualifed references.
  • Add more qualified references

FAIR-eva current implementation: Looks at a list of related terms and checks wheter or not they reference other digital objects (copy/paste code)

RDA-I3-04M

  • Run RDA-I3-02M
    FAIR-eva current implementation (wrongly): Copies i3-03M
@PalomoIFCA PalomoIFCA added this to the DT-GEO D4.2 milestone Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants