OpenAIRE Metric v4 F1 – (Meta)data are assigned a globally unique and persistent identifier.Metadata
F1 – (Meta)data are assigned a globally unique and persistent identifier. Evidenced by: Resource Identifier (datacite:identifier with a persistent identifier type such as DOI, Handle, ARK, PURL, URL, or URN). A missing or malformed identifier means the resource cannot be reliably located or cited.
OpenAIRE Metric v4 F2 – (Meta)data are described with rich metadata so they can be found by relevant attributes.Metadata
F2 – (Meta)data are described with rich metadata so they can be found by relevant attributes. Evidenced by 9 checks: Title (human-readable name), Creator (authorship), Publisher (responsible organisation), Publication Date (temporal context), Resource Type (nature of the resource using COAR vocabulary), Subject (keywords or classification codes), Description (abstract), Language (content language), Format (MIME type). Mandatory checks (Title, Creator, Publication Date, Resource Type) must pass for F2 to succeed; recommended checks contribute to the score but do not cause failure if absent.
OpenAIRE Metric v4 F3 – Metadata clearly and explicitly include the identifier of the data it describes.Metadata
F3 – Metadata clearly and explicitly include the identifier of the data it describes. Evidenced by: Resource Identifier (datacite:identifier). The identifier must be embedded in the metadata record itself, not just resolvable externally, so that the link between metadata and data object is unambiguous.
OpenAIRE Metric v4 A1.1 – The protocol used to access the data is open, free, and universally implementable.Metadata
A1.1 – The protocol used to access the data is open, free, and universally implementable. Evidenced at schema level: compliance with the OAI-PMH protocol (XML) or a publicly documented REST API (Crossref, DataCite) is assumed when a valid record is submitted. This principle always passes; it is not assessed through individual metadata field checks.
OpenAIRE Metric v4 A1.2 – The protocol allows for an authentication and authorisation procedure where necessary.Metadata
A1.2 – The protocol allows for an authentication and authorisation procedure where necessary. Evidenced by: Access Rights (datacite:rights with a COAR access right URI and label, e.g. open access, embargoed access, restricted access), and License Condition (oaire:licenseCondition with a license URI and start date). These fields declare under what conditions the resource can be accessed and reused.
OpenAIRE Metric v4 I1 – (Meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation.Metadata
I1 – (Meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation. Evidenced at schema level: the record conforms to the OpenAIRE Guidelines schema (DataCite metadata kernel + OAIRE extensions) or an equivalent published standard (DataCite XML, Crossref JSON, DCAT-AP). This principle always passes; it is not assessed through individual field checks.
OpenAIRE Metric v4 I2 – (Meta)data use vocabularies that follow FAIR principles.Metadata
I2 – (Meta)data use vocabularies that follow FAIR principles. Evidenced by 4 checks: Resource Type (COAR resource type concept URI, a FAIR-compliant vocabulary), Access Rights (COAR access right URI), Creator (datacite:nameIdentifier with a persistent author identifier such as ORCID — use of a FAIR-compliant person identifier vocabulary), Funding Reference (oaire:funderIdentifier with funderIdentifierType such as Crossref Funder ID or ISNI).
OpenAIRE Metric v4 I3 – (Meta)data include qualified references to other (meta)data.Metadata
I3 – (Meta)data include qualified references to other (meta)data. Evidenced by: Related Identifier (datacite:relatedIdentifier with relatedIdentifierType and relationType). Qualified links (e.g. IsVersionOf, IsPartOf, IsSupplementTo, IsCitedBy) make relationships between resources machine-readable and interoperable. This check is mandatory if applicable — it passes without penalty when no related resources exist.
OpenAIRE Metric v4 R1 – (Meta)data are richly described with a plurality of accurate and relevant attributes.Metadata
R1 – (Meta)data are richly described with a plurality of accurate and relevant attributes. Evidenced by 4 checks: Description (abstract or summary providing context for reuse), Subject (keywords or classification codes enabling thematic discovery), Resource Type (precise COAR type enabling format-aware reuse), Funding Reference (grant information enabling reproducibility and provenance tracking). Resource Type is mandatory; Description, Subject, and Funding Reference are recommended.
OpenAIRE Metric v4 R1.1 – (Meta)data are released with a clear and accessible data usage license.Metadata
R1.1 – (Meta)data are released with a clear and accessible data usage license. Evidenced by 2 checks: Access Rights (COAR-coded statement of who can access the resource), License Condition (explicit license URI, e.g. Creative Commons, with a start date). Without these, downstream users cannot determine whether and how they may legally reuse the resource.
OpenAIRE Metric v4 R1.2 – (Meta)data are associated with detailed provenance.Metadata
R1.2 – (Meta)data are associated with detailed provenance. Evidenced by 2 checks: Funding Reference (grant and funder information enabling traceability of the research that produced the resource), Related Identifier (links to source data, prior versions, or companion publications that establish the scholarly lineage of the work). Both checks are recommended or mandatory-if-applicable; R1.2 status is always SUCCESS.
OpenAIRE Metric v4 R1.3 – (Meta)data meet domain-relevant community standards.Metadata
R1.3 – (Meta)data meet domain-relevant community standards. Evidenced at schema level: conformance to the OpenAIRE Guidelines (DataCite + OAIRE schema), DataCite Metadata Schema, or Crossref JSON schema is assumed when a valid record is submitted. This principle always passes; it is not assessed through individual field checks.
OpenAIRE Metric v3 F1 – (Meta)data are assigned a globally unique and persistent identifier.Metadata
F1 – (Meta)data are assigned a globally unique and persistent identifier. Evidenced by: Resource Identifier (dc:identifier; should be a DOI, Handle, URN, or URL). A missing identifier means the resource cannot be reliably located or cited.
OpenAIRE Metric v3 F2 – (Meta)data are described with rich metadata so they can be found by relevant attributes.Metadata
F2 – (Meta)data are described with rich metadata so they can be found by relevant attributes. Evidenced by 9 checks: Title (dc:title), Creator (dc:creator), Publisher (dc:publisher), Publication Date (dc:date), Publication Type M (first dc:type, eu-repo vocabulary), Subject (dc:subject), Description (dc:description), Language (dc:language, ISO 639), Format (dc:format, IANA media type). Title, Creator, Publication Date, and Publication Type M are mandatory.
OpenAIRE Metric v3 F3 – Metadata clearly and explicitly include the identifier of the data it describes.Metadata
F3 – Metadata clearly and explicitly include the identifier of the data it describes. Evidenced by: Resource Identifier (dc:identifier). The identifier must be embedded in the metadata record itself so the link between metadata and data object is unambiguous.
OpenAIRE Metric v3 A1.1 – The protocol used to access the data is open, free, and universally implementable.Metadata
A1.1 – The protocol used to access the data is open, free, and universally implementable. Evidenced at schema level: compliance with the OAI-PMH protocol (Dublin Core XML) is assumed when a valid record is submitted. This principle always passes; it is not assessed through individual metadata field checks.
OpenAIRE Metric v3 A1.2 – The protocol allows for an authentication and authorisation procedure where necessary.Metadata
A1.2 – The protocol allows for an authentication and authorisation procedure where necessary. Evidenced by: Access Level (dc:rights with an info:eu-repo/semantics/ access right URI) and License Condition (dc:rights with a license URL or CC identifier). These fields declare under what conditions the resource can be accessed and reused.
OpenAIRE Metric v3 I1 – (Meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation.Metadata
I1 – (Meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation. Evidenced at schema level: the record conforms to the Dublin Core Metadata Element Set as profiled by the OpenAIRE Guidelines for Literature Repositories V3. This principle always passes; it is not assessed through individual field checks.
OpenAIRE Metric v3 I2 – (Meta)data use vocabularies that follow FAIR principles.Metadata
I2 – (Meta)data use vocabularies that follow FAIR principles. Evidenced by 2 checks: Publication Type M (value from the OpenAIRE eu-repo/semantics/ publication types vocabulary — a community-maintained, publicly documented vocabulary) and Access Level (value from the eu-repo/semantics/ access rights vocabulary).
OpenAIRE Metric v3 I3 – (Meta)data include qualified references to other (meta)data.Metadata
I3 – (Meta)data include qualified references to other (meta)data. Evidenced by 4 checks: Project Identifier (dc:relation with info:eu-repo/grantAgreement/ — a qualified link to the funding project), Alternative Identifier (dc:relation with info:eu-repo/semantics/altIdentifier/ — a qualified link to an alternative form of the resource), Publication Reference (dc:relation with info:eu-repo/semantics/reference/ — a qualified link to a related publication), Dataset Reference (dc:relation with info:eu-repo/semantics/dataset/ — a qualified link to a related dataset). All checks are recommended or mandatory-if-applicable.
OpenAIRE Metric v3 R1 – (Meta)data are richly described with a plurality of accurate and relevant attributes.Metadata
R1 – (Meta)data are richly described with a plurality of accurate and relevant attributes. Evidenced by 4 checks: Description (dc:description — abstract or summary), Subject (dc:subject — keywords or classification codes), Publication Type M (precise eu-repo type enabling format-aware reuse), Project Identifier (dc:relation/grantAgreement — funding/grant information).
OpenAIRE Metric v3 R1.1 – (Meta)data are released with a clear and accessible data usage license.Metadata
R1.1 – (Meta)data are released with a clear and accessible data usage license. Evidenced by 2 checks: Access Level (COAR-style access rights URI via eu-repo vocabulary) and License Condition (explicit license URL or CC identifier in dc:rights). Without these, downstream users cannot determine how they may legally reuse the resource.
OpenAIRE Metric v3 R1.2 – (Meta)data are associated with detailed provenance.Metadata
R1.2 – (Meta)data are associated with detailed provenance. Evidenced by 2 checks: Project Identifier (dc:relation/grantAgreement — funder and grant information establishing the research origin of the work) and Alternative Identifier (dc:relation/altIdentifier — links to other representations that establish the scholarly lineage).
OpenAIRE Metric v3 R1.3 – (Meta)data meet domain-relevant community standards.Metadata
R1.3 – (Meta)data meet domain-relevant community standards. Evidenced at schema level: conformance to the OpenAIRE Guidelines for Literature Repositories V3 (Dublin Core + eu-repo extensions) is assumed when a valid record is submitted. This principle always passes; it is not assessed through individual field checks.
OpenAIRE Metric data F1 – (Meta)data are assigned a globally unique and persistent identifier.Metadata
F1 – (Meta)data are assigned a globally unique and persistent identifier. Evidenced by: Identifier (datacite:identifier with a persistent identifier type such as DOI, Handle, ARK, PURL, URL, or URN). A missing or malformed identifier means the dataset cannot be reliably located or cited.
OpenAIRE Metric data F2 – (Meta)data are described with rich metadata so they can be found by relevant attributes.Metadata
F2 – (Meta)data are described with rich metadata so they can be found by relevant attributes. Evidenced by 9 checks: Title (human-readable name), Creator (authorship), Publisher (responsible organisation), Publication Year (temporal context), Resource Type (type of data resource using DataCite vocabulary), Subject (keywords or classification codes), Description (abstract), Language (content language), Format (MIME type or format description). Mandatory checks (Identifier, Creator, Title, Publisher, Publication Year) must pass for F2 to succeed; recommended checks contribute to score but do not cause failure if absent.
OpenAIRE Metric data F3 – Metadata clearly and explicitly include the identifier of the data it describes.Metadata
F3 – Metadata clearly and explicitly include the identifier of the data it describes. Evidenced by: Identifier (datacite:identifier). The identifier must be embedded in the metadata record itself, not just resolvable externally, so that the link between metadata and the data object is unambiguous.
OpenAIRE Metric data A1.1 – The protocol used to access the data is open, free, and universally implementable.Metadata
A1.1 – The protocol used to access the data is open, free, and universally implementable. Evidenced at schema level: compliance with the OAI-PMH protocol (XML) or a publicly documented REST API (DataCite) is assumed when a valid record is submitted. This principle always passes; it is not assessed through individual metadata field checks.
OpenAIRE Metric data A1.2 – The protocol allows for an authentication and authorisation procedure where necessary.Metadata
A1.2 – The protocol allows for an authentication and authorisation procedure where necessary. Evidenced by: Rights (datacite:rights with an access rights URI such as info:eu-repo/semantics/openAccess, embargoedAccess, restrictedAccess, or closedAccess). This field declares under what conditions the resource can be accessed and reused.
OpenAIRE Metric data I1 – (Meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation.Metadata
I1 – (Meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation. Evidenced at schema level: the record conforms to the DataCite Metadata Schema or an equivalent published standard (DataCite JSON, Schema.org, DCAT-AP). This principle always passes; it is not assessed through individual field checks.
OpenAIRE Metric data I2 – (Meta)data use vocabularies that follow FAIR principles.Metadata
I2 – (Meta)data use vocabularies that follow FAIR principles. Evidenced by 3 checks: Resource Type (DataCite resourceTypeGeneral vocabulary, a FAIR-compliant controlled vocabulary for data types), Rights (standardised access rights URIs, e.g. info:eu-repo/semantics/ namespace), Creator (datacite:nameIdentifier with a persistent author identifier such as ORCID — use of a FAIR-compliant person identifier vocabulary).
OpenAIRE Metric data I3 – (Meta)data include qualified references to other (meta)data.Metadata
I3 – (Meta)data include qualified references to other (meta)data. Evidenced by: Related Identifier (datacite:relatedIdentifier with relatedIdentifierType and relationType such as IsCitedBy, IsPartOf, IsNewVersionOf, HasMetadata, IsMetadataFor). Qualified links make relationships between datasets machine-readable and interoperable. This check is mandatory if applicable — it passes without penalty when no related resources exist.
OpenAIRE Metric data R1 – (Meta)data are richly described with a plurality of accurate and relevant attributes.Metadata
R1 – (Meta)data are richly described with a plurality of accurate and relevant attributes. Evidenced by 4 checks: Description (abstract or summary providing context for reuse), Subject (keywords or classification codes enabling thematic discovery), Resource Type (precise type enabling format-aware reuse), Contributor (additional persons or roles that contributed to the data — enables attribution and reproducibility). Resource Type is recommended; Description, Subject, and Contributor are recommended or mandatory-if-applicable.
OpenAIRE Metric data R1.1 – (Meta)data are released with a clear and accessible data usage license.Metadata
R1.1 – (Meta)data are released with a clear and accessible data usage license. Evidenced by: Rights (access rights URI and optionally a license URI enabling downstream users to determine whether and how they may legally reuse the dataset). Without this, reuse rights are undefined.
OpenAIRE Metric data R1.2 – (Meta)data are associated with detailed provenance.Metadata
R1.2 – (Meta)data are associated with detailed provenance. Evidenced by 2 checks: Date (date(s) relevant to the data lifecycle — issued, created, accepted, collected — enabling traceability), Related Identifier (links to source data, prior versions, or companion publications that establish the scholarly lineage of the dataset). Date is mandatory; Related Identifier is mandatory-if-applicable.
OpenAIRE Metric data R1.3 – (Meta)data meet domain-relevant community standards.Metadata
R1.3 – (Meta)data meet domain-relevant community standards. Evidenced at schema level: conformance to the OpenAIRE Guidelines for Data Archives V2 (DataCite Metadata Schema) or DataCite JSON / Schema.org / DCAT-AP schema is assumed when a valid record is submitted. This principle always passes; it is not assessed through individual field checks.
