146 Tests Available in the Registry
Generic CURL command:
curl -H "Accept: application/json" https://tools.ostrails.eu/champion/tests
FAIR Champion: Data Authorization
Test a discovered data GUID for the ability to implement authentication and authorization in its resolution protocol. Currently passes InChI Keys, DOIs, Handles, and URLs. It also searches the metadata for the Dublin Core 'accessRights' property, which may point to a document describing the data access process. Recognition of other identifiers will be added upon request by the community.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_data_authorization |
|---|
FAIR Champion: Data Identifier in Metadata
Test that the identifier of the data is an unambiguous element of the metadata. Tested options are schema:distribution, http://www.w3.org/ns/ldp#contains, iao:IAO_0000136, IAO:0000136,ldp:contains,foaf:primaryTopic,schema:distribution,schema:contentUrl,schema,mainEntity,schema:codeRepository,schema:distribution,schema:contentUrl, dcat:distribution, dcat:dataset,dcat:downloadURL,dcat:accessURL,sio:SIO_000332, sio:is-about, obo:IAO_0000136
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_data_identifier_in_metadata |
|---|
Execute Test
FAIR Champion: Data Knowlege Representation Language (Strict Test)
Test if the data uses a formal language broadly applicable for knowledge representation. This particular test takes a broad view of what defines a 'knowledge representation language'; in this evaluation, a knowledge representation language is interpreted as one in which terms are semantically-grounded in ontologies. Any form of ontologically-grounded linked data will pass this test.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_data_kr_language_strong |
|---|
Execute Test
FAIR Champion: Data Knowlege Representation Language (Weak Test)
Test if the data uses a formal language broadly applicable for knowledge representation. This particular test takes a broad view of what defines a 'knowledge representation language'; in this evaluation, a knowledge representation language is interpreted as one in which terms are semantically-grounded in ontologies. Any form of structured data will pass this test
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_data_kr_language_weak |
|---|
Execute Test
FAIR Champion: Data Protocol
Data may be retrieved by an open and free protocol. Tests data GUID for its resolution protocol. Currently passes InChI Keys, DOIs, Handles, and URLs. Recognition of other identifiers will be added upon request by the community.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_data_protocol |
|---|
Execute Test
FAIR Champion: Grounded Metadata
Tests whether a machine is able to find 'grounded' metadata. i.e. metadata terms that are in a resolvable namespace, where resolution leads to a definition of the meaning of the term. Examples include JSON-LD, embedded schema, or any form of RDF. This test currently excludes XML, even when terms are namespaced. Future versions of this test may be more flexible.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_grounded_metadata |
|---|
Execute Test
FAIR Champion: Metadata Authorization
Tests metadata GUID for the ability to implement authentication and authorization in its resolution protocol. Currently passes InChI Keys, DOIs, Handles, and URLs. Recognition of other identifiers will be added upon request by the community.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_authorization |
|---|
FAIR Champion: Metadata Identifier Explicitly In Metadata
Metric to test if the metadata contains the unique identifier to the metadata itself. This is done using a variety of 'scraping' tools, including DOI metadata resolution, the use of the 'extruct' Python tool, and others. The test is executed by searching for the predicates 'http[s]://purl.org/dc/terms/identifier','http[s]://schema.org/identifier.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_identifier_in_metadata |
|---|
Execute Test
FAIR Champion: Identifier Persistence
Metric to test if the unique identifier of the metadata resource is likely to be persistent. Known schema are registered in FAIRSharing (https://fairsharing.org/standards/?q=&selected_facets=type_exact:identifier%20schema). For URLs that don't follow a schema in FAIRSharing we test known URL persistence schemas (purl, oclc, fdlp, purlz, w3id, ark).
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_identifier_persistence |
|---|
Execute Test
FAIR Champion: Metadata Includes License (strong)
Maturity Indicator to test if the linked data metadata contains an explicit pointer to the license. Tests: xhtml, dvia, dcterms, cc, data.gov.au, and Schema license predicates in linked data, and validates the value of those properties.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_includes_license |
|---|
Execute Test
FAIR Champion: Metadata Includes License (weak)
Maturity Indicator to test if the metadata contains an explicit pointer to the license. This 'weak' test will use a case-insensitive regular expression, and scan both key/value style metadata, as well as linked data metadata. Tests: xhtml, dvia, dcterms, cc, data.gov.au, and Schema license predicates in linked data, and validates the value of those properties.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_includes_license_weak |
|---|
Execute Test
FAIR Champion: Metadata Knowledge Representation Language (weak)
Maturity Indicator to test if the metadata uses a formal language broadly applicable for knowledge representation. This particular test takes a broad view of what defines a 'knowledge representation language'; in this evaluation, anything that can be represented as structured data will be accepted.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_kr_language_weak |
|---|
Execute Test
FAIR Champion: Metadata Contains Outward Links
Maturity Indicator to test if the metadata links outward to third-party resources. It only tests metadata that can be represented as Linked Data.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_outward_links |
|---|
Execute Test
FAIR Champion: Metadata Persistence
Metric to test if the metadata contains a persistence policy, explicitly identified by a persistencePolicy key (in hashed data) or a http://www.w3.org/2000/10/swap/pim/doc#persistencePolicy predicate in Linked Data. DOIs are assumed to have metadata persistence.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_persistence |
|---|
Execute Test
FAIR Champion: Uses open free protocol for metadata retrieval
Metadata may be retrieved by an open and free protocol. Tests metadata GUID for its resolution protocol. Currently passes InChI Keys, DOIs, Handles, and URLs. Recognition of other identifiers will be added upon request by the community.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_protocol |
|---|
Execute Test
FAIR Champion: Metadata uses FAIR vocabularies (strong)
Maturity Indicator to test if the linked data metadata uses terms that resolve to linked (FAIR) data.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_uses_fair_vocabularies |
|---|
Execute Test
FAIR Champion: Searchable in major search engine
Tests whether a machine is able to discover the resource by search, using Microsoft Bing.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_searchable |
|---|
Execute Test
FAIR Champion: Structured Metadata
Tests whether a machine is able to find structured metadata. This could be (for example) RDFa, embedded json, json-ld, or content-negotiated structured metadata such as RDF Turtle.
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_structured_metadata |
|---|
Execute Test
FAIR Champion: Unique Identifier
Metric to test if the metadata resource has a unique identifier. This is done by comparing the GUID to the patterns (by regexp) of known GUID schemas such as URLs and DOIs. Known schema are registered in FAIRSharing (https://fairsharing.org/standards/?q=&selected_facets=type_exact:identifier%20schema)
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_unique_identifier |
|---|
Execute Test
Ontology minimum metadata is declared
This check verifies if the following minimum metadata are present in the ontology metadata: * title: declared using [dc:title](http://purl.org/dc/elements/1.1/title), [dcterms:title](http://purl.org/dc/terms/title) or [schema:name](http://schema.org/name) * description: declared using [dc:abstract](http://purl.org/dc/elements/1.1/abstract), [dcterms:abstract](http://purl.org/dc/terms/abstract), [dc:description](http://purl.org/dc/elements/1.1/description), [dcterms:description](http://purl.org/dc/terms/description), [schema:description](http://schema.org/description), [rdfs:comment](http://www.w3.org/2000/01/rdf-schema#comment), [doap:description](http://usefulinc.com/ns/doap#description), [doap:shortdesc](http://usefulinc.com/ns/doap#shortdesc) or [skos:note](http://www.w3.org/2004/02/skos/core#note) * license: declared using [dcterms:license](http://purl.org/dc/terms/license), [schema:license](http://schema.org/licesne), [doap:license](http://usefulinc.com/ns/doap#license) or [cc:license](http://creativecommons.org/ns#license). * version iri: declared using [owl:versionIRI](http://www.w3.org/2002/07/owl#versionIRI) * creator: declared using [dc:creator](http://purl.org/dc/elements/1.1/creator), [dcterms:creator](http://purl.org/dc/terms/creator), [pav:createdBy](http://purl.org/pav/createdBy), [pav:authoredBy](http://purl.org/pav/authoredBy), [schema:creator](http://schema.org/creator), [prov:wasAttributedTo](http://www.w3.org/ns/prov#wasAttributedTo) or [doap:developer](http://usefulinc.com/ns/doap#developer) * namespace URI: declared using [vann:preferredNamespaceUri](https://purl.org/vocab/vann/) The test will pass if all ontology metadata are present. The test will fail otherwise, indicating the properties that are missing.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/OM1 |
|---|
Execute Test
Ontology has a persistent URL
This test verifies if the ontology has a persistent URL. We do so by checking if the ontology URI follows any of the following URI schemes: * w3id.org * doi.org * purl.org (or purl.something.org) * linked.data.gov.au * dbpedia.org * www.w3.org * perma.cc * data.europa.eu
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/PURL1 |
|---|
Execute Test
Ontology uses an open protocol
This check verifies if the ontology uses an open protocol (HTTP or HTTPS). The test will pass if the ontology URI starts with http or https. It will fail otherwise.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/HTTP1 |
|---|
Execute Test
A version IRI is declared in the ontology metadata
This test verifies whether there is an id for this ontology version, and whether the id is unique (i.e., different from the ontology URI). The test will pass if: 1. The ontology has a versionIRI ([owl:versionIRI](http://www.w3.org/2002/07/owl#versionIRI)) and 2. The versionIRI used is different from the ontology URI. Otherwise the test will fail. The test will also verify whether version information is present (through [owl:versionInfo](http://www.w3.org/2002/07/owl#versionInfo)), but this is optional.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/VER1 |
|---|
Execute Test
Ontology URI is resolvable
This test verifies if the ontology URI that was found within the ontology document is resolvable. Note that the ontology URI found in the ontology may be different from the URI used in the assessment. The test will pass if the vocabulary is resolvable in any of the following RDF serializations: RDF/XML, TTL, N-Triples, JSON-LD. The test will fail if no known RDF serialization is returned, or the serialization returned is not among one of the aforementioned.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/URL1 |
|---|
Execute Test
Ontology has a license available
This test verifies if a license (or rights) are associated with the ontology. The test will pass if a license is declared using any of the following properties: [dcterms:license](http://purl.org/dc/terms/license), [schema:license](https://schema.org/license), [doap:license](http://usefulinc.com/ns/doap#license) or [cc:license](http://creativecommons.org/ns#license). If a license is not found, but rights are declared (using [dc:rights](http://purl.org/dc/elements/1.1/rights), [dcterms:rights](http://purl.org/dc/terms/rights) or [dcterms:accessRights](http://purl.org/dc/terms/accessRights)), the test will pass as well. Otherwise, the test will fail (i.e., no license or rights are declared).
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/OM1 |
|---|
Execute Test
Ontology reuses existing vocabularies for metadata annotations
This test verifies if the ontology reuses other vocabularies for declaring metadata terms (see tests OM1... OM5). The test will pass if metadata annotations using properties from any of the following vocabularies are used: * [Dublin Core](http://purl.org/dc/elements/1.1/) (dc, dcterms) * [Schema.org](https://schema.org/) (schema) * [Vocabulary for annotating vocabulary descriptions](http://purl.org/vocab/vann/) (vann) * [W3C Provenance standard](http://www.w3.org/ns/prov#) (prov) * [Bibliographic Ontology](http://purl.org/ontology/bibo/) (bibo) * [Provenance, Authoring and Versioning](http://purl.org/pav/) (pav) * [Firend of a friend](http://xmlns.com/foaf/0.1/) (foaf) * [Description of a project](http://usefulinc.com/ns/doap#) (doap) * [Metadata vocabulary for ontology descriptions](https://w3id.org/mod#) (mod) * [Web Ontology Language](http://www.w3.org/2002/07/owl#) (owl) * [Resource description framework schema](http://www.w3.org/2000/01/rdf-schema#) (rdfs) The test will also return the vocabularies that were found. If none are found, the test will fail.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/VOC1 |
|---|
Execute Test
Ontology prefix is found in prefix.cc or LOV
This test verifies whether the ontology prefix is available in [prefix.cc]((https://prefix.cc/)) or the [Linked Open Vocabularies (LOV)]((https://lov.linkeddata.es/)) registries. The test will pass if: 1. there is a prefix declared in the assessed ontology, 2. the prefix is found in [LOV](https://lov.linkeddata.es/) or [prefix.cc](https://prefix.cc/) 3. if found in [LOV](https://lov.linkeddata.es/) or [prefix.cc](https://prefix.cc/) , the namespace URI associated with the prefix is the same as the assessed ontology URI (or preferred namespace URI) Otherwise, the test will fail.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/FIND2 |
|---|
Execute Test
Ontology found in community registry
This test verifies if the ontology can be found in a public registry like the Linked Open Vocabularies (LOV) public registry. The test will pass if the assessed ontology URI is found in the list of vocabularies returned by LOV. Alternatively, if there is a [schema:includedInDataCatalog](https://schema.org/includedInDataCatalog) annotation, the test will pass. The test will fail otherwise.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/FIND3 |
|---|
Execute Test
Ontology is available in RDF (TTL, N3, RDF/XML or JSON-LD)
This test verifies if the ontology has a valid RDF serialization (TTL, N3, RDF/XML or JSON-LD are supported). The test will fail if no RDF serialization could be loaded for analysis (e.g., the ontology has typos that prevent its parsing). The test uses the OWLAPI to load ontologies or vocabularies.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/RDF1 |
|---|
Execute Test
Ontology declares detailed provenance metadata
This check verifies if detailed provenance information is available for the ontology: * issued date: declared using [dcterms:issued](http://purl.org/dc/terms/issued), [dcterms:submitted](http://purl.org/dc/terms/submitted) or [schema:datePublished](https://schema.org/datePublished) * publisher: declared using [dc:publisher](http://purl.org/dc/elements/1.1/publisher), [dcterms:publisher](http://purl.org/dc/terms/publisher) or [schema:publisher](https://schema.org/publisher) The test will pass if both metadata fields are present. The test will fail otherwise, indicating the properties that are missing.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/OM5.2 |
|---|
Execute Test
Ontology has HTML documentation
This test verifies if the ontology has an HTML documentation. The test will attempt to download an HTML representation using the ontology URI, with content negotiation
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/DOC1 |
|---|
Execute Test
Ontology declares recommended metadata
This test verifies if the following recommended metadata are present in the ontology metadata: * Namespace prefix: declared using [vann:preferredNamespacePrefix](https://purl.org/vocab/vann/) * Version info: declared using [owl:versionInfo](http://www.w3.org/2002/07/owl#versionInfo) or [schema:schemaVersion](http://schema.org/schemaVersion) * Creation date: declared using [dcterms:created](http://purl.org/dc/terms/created), [schema:dateCreated](http://schema.org/dateCreated), [doap:created](http://usefulinc.com/ns/doap#created), [prov:generatedAtTime](http://www.w3.org/ns/prov#generatedAtTime) or [pav:createdOn](http://purl.org/pav/) * Citation: declared using [dcterms:bibliographicCitation](http://purl.org/dc/terms/bibliographicCitation) * Contributor (optional): declared using [dc:contributor](http://purl.org/dc/elements/1.1/contributor), [dcterms:contributor](http://purl.org/dc/terms/contributor), schema:contributor, [doap:documenter](http://usefulinc.com/ns/doap#documenter), [doap:maintainer](http://usefulinc.com/ns/doap#maintainer), [doap:helper](http://usefulinc.com/ns/doap#helper), [doap:translator](http://usefulinc.com/ns/doap#translator) or [pav:contributedBy](http://purl.org/pav/). The test will pass if all the recommended metadata properties are available in the ontology metadata (using any of the vocabularies listed above). The test will also check if contributor is present, but with no penalty (as not all ontologies have a contributor).
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/OM2 |
|---|
Execute Test
Ontology has content negotiation for RDF in RDF/XML, TTL, NTriples or JSON-LD serializations
This test verifies whether HTML and an RDF representation is available for the target vocabulary by doing content negotiation on the ontology URI. The test will pass if the vocabulary is available in HTML and in any of the following RDF serializations: * RDF/XML (application/rdf+xml), * TTL (text/turtle), * N-Triples (text/n3), * JSON-LD (application/ld+json) The test will fail if no HTML is returned, if no known RDF serialization is returned, or the serialization returned is not among one of the aforementioned.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/CN1 |
|---|
Execute Test
Ontology declares detailed metadata
This test verifies if the ontology includes the following detailed metadata: * Digital Object Identifier (DOI): declared using [bibo:doi](http://purl.org/ontology/bibo/doi), [schema:identifier](https://schema.org/identifier) (if a doi is provided) or [dcterms:identifier](http://purl.org/dc/terms/identifier) (if a doi is provided) * publisher: declared using [dc:publisher](http://purl.org/dc/elements/1.1/publisher), [dcterms:publisher](http://purl.org/dc/terms/publisher) or [schema:publisher](https://schema.org/publisher) * logo: declared using [foaf:logo](http://xmlns.com/foaf/0.1/logo) or [schema:logo](https://schema.org/logo) * status: declared using [bibo:status](http://purl.org/ontology/bibo/status) or [mod:status](https://w3id.org/mod#status) * source: declared using [dcterms:source](http://purl.org/dc/terms/source) or [prov:hadOriginalSource](http://www.w3.org/ns/prov#hadOriginalSource) * issued date: declared using [dcterms:issued](http://purl.org/dc/terms/issued) * previous version (optional): declared using [dc:replaces](http://purl.org/dc/elements/1.1/replaces), [dcterms:replaces](http://purl.org/dc/terms/replaces), [prov:wasRevisionOf](http://www.w3.org/ns/prov#wasRevisionOf), [owl:priorVersion](http://www.w3.org/2002/07/owl#priorVersion) or [pav:previousVersion](http://purl.org/pav/previousVersion) * backward compatibility (optional): declared using [owl:backwardCompatibleWith](http://www.w3.org/2002/07/owl#backwardCompatibleWith) * modified date (optional): declared using [dcterms:modified](http://purl.org/dc/terms/modified) or [schema:dateModified](https://schema.org/dateModified) The test will pass if all the detailed metadata properties are available in the ontology metadata (using any of the vocabularies listed above). The test will also check if previosu version, backward compatibility and modified date are present, but with no penalty (as not all ontologies have a previous version).
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/OM3 |
|---|
Execute Test
Ontology version IRI resolves
This test verifies if the version IRI resolves. The test will pass if there is a version IRI for the ontology/vocabulary (detected using [owl:versionIRI](http://www.w3.org/2002/07/owl#versionIRI) in the ontology metadata) and whether doing a request to said IRI returns a resource. The test will fail if the resource is not found (404 response) or returns an error.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/VER2 |
|---|
Execute Test
Ontology documentation: all terms have labels
This test verifies the extent to which all ontology terms have labels. The test will pass if all classes, properties and data properties have either an [rdfs:label](http://www.w3.org/2000/01/rdf-schema#label) or [skos:prefLabel](http://www.w3.org/2004/02/skos/core#prefLabel). For skos vocabularies, only the skos:Concepts are assessed. Otherwise, the test will fail, indicating the level of completeness found (i.e., percentage of documented terms)
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/VOC3 |
|---|
Execute Test
Ontology documentation: all terms have definitions
This check verifies whether all ontology terms have descriptions. The test will pass if all classes, properties and data properties have at least one [rdfs:comment](http://www.w3.org/2000/01/rdf-schema#comment), [skos:definition](http://www.w3.org/2004/02/skos/core#definition) or [obo:IAO_0000118](http://purl.obolibrary.org/obo/IAO_0000118) annotation. For skos vocabularies, only the skos:Concepts are assessed. The test will fail otherwise, showing the level of completeness obtained (i.e. the percentage of documented terms).
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/VOC4 |
|---|
Execute Test
Ontology license is resolvable
This test verifies if the ontology license is resolvable. The test will pass if the license available in the ontology metadata resolves to a resource. The test will fail if no license is declared (OM4.1), if the license is not a URI/URL, or if the response when requesting is 404 or an error.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/OM4.2 |
|---|
Execute Test
Consistent ontology IDs are employed
This check verifies if the ontology URI is equal to the ontology ID. The test passes if the ontology URI used to load the ontology document is the same as the ontology id found in the document itself. Otherwise the test will fail.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/URL2 |
|---|
Execute Test
Ontology imports or reuses well established vocabularies
This test verifies if the ontology imports/extends other vocabularies (besides RDF, OWL and RDFS). The test will pass if other vocabularies are imported ([owl:imports](http://www.w3.org/2002/07/owl#imports)), or if classes, properties or data properties outside the ontology URI or namespace URI are used. The test wil fail if no terms are reused.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/VOC2 |
|---|
Execute Test
Ontology metadata are accessible, even when the ontology is not
Metadata are accessible even when the ontology is no longer available. Since the metadata is usually included in the ontology, this test verifies if the ontology can be found in the [Linked Open Vocabularies (LOV) public registry](https://lov.linkeddata.es). The test will pass if the assessed ontology/vocabulary URI is found in the LOV list of vocabularies. Alternatively, if there is a [schema:includedInDataCatalog](https://schema.org/includedInDataCatalog) annotation, the test will pass. The test will fail otherwise.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/FIND_3_BIS |
|---|
Execute Test
Ontology prefix is declared
This check verifies if an ontology prefix is declared in the ontology metadata. The test will pass if a [vann:preferredNamespacePrefix](http://purl.org/vocab/vann/) is declared. Otherwise, the test will fail.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/FIND1 |
|---|
Execute Test
Ontology declares basic provenance metadata
This check verifies if basic provenance metadata is available for the ontology: * creator: declared using [dc:creator](http://purl.org/dc/elements/1.1/creator), [dcterms:creator](http://purl.org/dc/terms/creator), [pav:createdBy](http://purl.org/pav/createdBy), [pav:authoredBy](http://purl.org/pav/authoredBy), [schema:creator](https://schema.org/creator) or [doap:developer](http://usefulinc.com/ns/doap#developer) * creation date: declared using [dcterms:created](http://purl.org/dc/terms/created), [schema:dateCreated](https://schema.org/dateCreated), [doap:created](http://usefulinc.com/ns/doap#created), [prov:generatedAtTime](http://www.w3.org/ns/prov#generatedAtTime) or [pav:createdOn](http://purl.org/pav/createdOn) * contributor (optional): declared using [dc:contributor](http://purl.org/dc/elements/1.1/contributor), [dcterms:contributor](http://purl.org/dc/terms/contributor), [schema:contributor](https://schema.org/contributor), [doap:documenter](http://usefulinc.com/ns/doap#documenter), [doap:maintainer](http://usefulinc.com/ns/doap#maintainer), [doap:helper](http://usefulinc.com/ns/doap#helper), [doap:translator](http://usefulinc.com/ns/doap#translator) or [pav:contributedBy](http://purl.org/pav/contributedBy). * previous version (optional): declared using [dc:replaces](http://purl.org/dc/elements/1.1/replaces), [dcterms:replaces](http://purl.org/dc/terms/replaces), [prov:wasRevisionOf](http://www.w3.org/ns/prov#wasRevisionOf), [owl:priorVersion](http://www.w3.org/2002/07/owl#previousVersion), [pav:previousVersion](http://purl.org/pav/previousVersion) The test will pass if creator and creation date are present. The test will fail otherwise, indicating the properties that are missing.
Additional Details
| Endpoint | https://foops.linkeddata.es/assess/test/OM5.1 |
|---|
Execute Test
FAIR Champion: Metadata Knowledge Representation Language (strong)
Maturity Indicator to test if the metadata uses a formal language broadly applicable for knowledge representation. This particular test takes a broad view of what defines a 'knowledge representation language'; in this evaluation, a knowledge representation language is interpreted as one in which terms are semantically-grounded in ontologies. Any form of RDF will pass this test (including RDF that is automatically extracted by third-party parsers such as Apache Tika).
Additional Details
| Endpoint | https://tests.ostrails.eu/assess/test/fc_metadata_kr_language_strong |
|---|
Execute Test
Software identifier follows a common schema
This test checks that the identifier associated with a software (if there’s one) follows a common schema such as URN, URL, DOI, etc. This is achieved by looking for identifiers in the README file and checking if they follow one of these schemas: URN, SWHID, DOI and URL.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-01-3 |
|---|
Execute Test
Software identifier follows a common schema
This test checks that the identifier associated with a software (if there’s one) follows a common schema such as URN, URL, DOI, etc. This is achieved by looking for identifiers in the README file and checking if they follow one of these schemas: URN, SWHID, DOI and URL.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-01-3 |
|---|
Execute Test
There is an identifier in README or CITATION.cff
This test checks if an identifier is found in the README or CITATION.cff files. This is done by looking for an identifier in the CITATION.cff and README files in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-07-1 |
|---|
Execute Test
There is an identifier in README or CITATION.cff
This test checks if an identifier is found in the README or CITATION.cff files. This is done by looking for an identifier in the CITATION.cff and README files in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-07-1 |
|---|
Execute Test
Contact and/or support metadata exists
This test checks if contact and/or support metadata is found in the repository. This is achieved by checking if there is contact or support information in the README file or any other package file ( (e.g., setup.py, setup.cfg, pom.xml, etc.).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-05-2 |
|---|
Execute Test
Contact and/or support metadata exists
This test checks if contact and/or support metadata is found in the repository. This is achieved by checking if there is contact or support information in the README file or any other package file ( (e.g., setup.py, setup.cfg, pom.xml, etc.).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-05-2 |
|---|
Execute Test
Contact and/or support metadata exists
This test checks if contact and/or support metadata is found in the repository. This is achieved by checking if there is contact or support information in the README file or any other package file ( (e.g., setup.py, setup.cfg, pom.xml, etc.).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-05-2 |
|---|
Execute Test
Software metadata refers to the software identifier
This test checks if there is a persistent identifier (i.e., Software Heritage ID, Zenodo DOI) associated with the software repository in files like CITATION.cff, codemeta.json and README. This is achieved by looking for an identifier in the files previously mentioned.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-01-2 |
|---|
Execute Test
Software metadata refers to the software identifier
This test checks if there is a persistent identifier (i.e., Software Heritage ID, Zenodo DOI) associated with the software repository in files like CITATION.cff, codemeta.json and README. This is achieved by looking for an identifier in the files previously mentioned.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-01-2 |
|---|
Execute Test
Repository is from Github/Gitlab
This test checks whether the provided URL points to a repository hosted on a source code repository such as GitHub or GitLab. It verifies both that the URL contains a known domain (e.g., "github.com" or "gitlab.com") and that it is reachable (i.e., the request returns a valid response).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-09-1 |
|---|
Execute Test
Repository is from Github/Gitlab
This test checks whether the provided URL points to a repository hosted on a source code repository such as GitHub or GitLab. It verifies both that the URL contains a known domain (e.g., "github.com" or "gitlab.com") and that it is reachable (i.e., the request returns a valid response).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-09-1 |
|---|
Execute Test
Repository is from Github/Gitlab
This test checks whether the provided URL points to a repository hosted on a source code repository such as GitHub or GitLab. It verifies both that the URL contains a known domain (e.g., "github.com" or "gitlab.com") and that it is reachable (i.e., the request returns a valid response).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-09-1 |
|---|
Execute Test
Repository is from Github/Gitlab
This test checks whether the provided URL points to a repository hosted on a source code repository such as GitHub or GitLab. It verifies both that the URL contains a known domain (e.g., "github.com" or "gitlab.com") and that it is reachable (i.e., the request returns a valid response).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-09-1 |
|---|
Execute Test
Software has releases
This test checks if the software has any releases in the source code repository. This is achieved by checking if there’s any releases created in the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-1 |
|---|
Execute Test
Software has releases
This test checks if the software has any releases in the source code repository. This is achieved by checking if there’s any releases created in the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-1 |
|---|
Execute Test
Software documentation
This test checks if documentation is found in the repository. This is achieved by looking for a README file, a ReadTheDocs URL in the README file and wikis (in case of GitHub projects).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-05-3 |
|---|
Execute Test
Software documentation
This test checks if documentation is found in the repository. This is achieved by looking for a README file, a ReadTheDocs URL in the README file and wikis (in case of GitHub projects).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-05-3 |
|---|
Execute Test
Software documentation
This test checks if documentation is found in the repository. This is achieved by looking for a README file, a ReadTheDocs URL in the README file and wikis (in case of GitHub projects).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-05-3 |
|---|
Execute Test
Repository has continuous integration workflows
This test checks if there are continuous integration workflows in the repository. This is done by looking for a .github.workflows directory in Github and .gitlab-ci.yml file in Gitlab.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-19-1 |
|---|
Execute Test
Dependencies are declared
This test checks if dependencies are declared in the repository. This is achieved by checking if there are dependencies listed in the README file or other files like requirements.txt and pom.xml.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-13-1 |
|---|
Execute Test
Dependencies are declared
This test checks if dependencies are declared in the repository. This is achieved by checking if there are dependencies listed in the README file or other files like requirements.txt and pom.xml.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-13-1 |
|---|
Execute Test
Repository active
This test checks whether the repository is active. It first looks for a repostatus badge with the value “Active” in the README file. If the badge is not present, the test verifies whether there have been any commits to the repository in the past, indicating ongoing development.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-17-1 |
|---|
Execute Test
License is SPDX compliant
This test checks if the repository license is SPDX compliant. This is done by checking if all licenses found in the repository match any of the licenses supported by SPDX.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-15-2 |
|---|
Execute Test
Software metadata exists
This test checks if a codemeta.json, CITATION.cff file or package file that includes metadata about a software component exists. This is done by looking for CITATION.cff, codemeta.json and package files (e.g., setup.py, setup.cfg, pom.xml, etc.) in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-1 |
|---|
Execute Test
Software metadata exists
This test checks if a codemeta.json, CITATION.cff file or package file that includes metadata about a software component exists. This is done by looking for CITATION.cff, codemeta.json and package files (e.g., setup.py, setup.cfg, pom.xml, etc.) in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-1 |
|---|
Execute Test
Software metadata exists
This test checks if a codemeta.json, CITATION.cff file or package file that includes metadata about a software component exists. This is done by looking for CITATION.cff, codemeta.json and package files (e.g., setup.py, setup.cfg, pom.xml, etc.) in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-1 |
|---|
Execute Test
Authors have an ORCID
This test checks if authors have an ORCID assigned. This is done by looking for authors in the codemeta.json or AUTHORS files and checking if all of them have an ORCID assigned.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-06-3 |
|---|
Execute Test
Authors have an ORCID
This test checks if authors have an ORCID assigned. This is done by looking for authors in the codemeta.json or AUTHORS files and checking if all of them have an ORCID assigned.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-06-3 |
|---|
Execute Test
Presence of tests in source code repository
This test checks if there are tests present in the repository. This is done by checking if there are files or directories that mention “test” in their names in the root and one level deep in the repository tree.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-14-1 |
|---|
Execute Test
Software identifier resolves to software
This test checks if the identifier found in the repository resolves back to the source code repository. This is done by checking if the landing page where the identifier resolves to links back to the source code repository using requests.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-07-2 |
|---|
Execute Test
Software identifier resolves to software
This test checks if the identifier found in the repository resolves back to the source code repository. This is done by checking if the landing page where the identifier resolves to links back to the source code repository using requests.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-07-2 |
|---|
Execute Test
A repostatus badge exists
This test checks if the repository has a repo status badge in the README file.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-05-1 |
|---|
Execute Test
A repostatus badge exists
This test checks if the repository has a repo status badge in the README file.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-05-1 |
|---|
Execute Test
A repostatus badge exists
This test checks if the repository has a repo status badge in the README file.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-05-1 |
|---|
Execute Test
Release identifiers follow the same scheme
This test checks if all release identifiers follow the same scheme. This is achieved by checking if there’s any releases created in the repository and that their URLs follow the same pattern or scheme.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-4 |
|---|
Execute Test
Release identifiers follow the same scheme
This test checks if all release identifiers follow the same scheme. This is achieved by checking if there’s any releases created in the repository and that their URLs follow the same pattern or scheme.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-4 |
|---|
Execute Test
Release versions follow a community established naming convention
This test checks if all version identifiers follow either SemVer or CalVer conventions. This is achieved by checking if there’s any releases created in the repository and that their version numbers (or tags) follow Semantic Versioning (SemVer) or Calendar Versioning (CalVer).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-3 |
|---|
Execute Test
Release versions follow a community established naming convention
This test checks if all version identifiers follow either SemVer or CalVer conventions. This is achieved by checking if there’s any releases created in the repository and that their version numbers (or tags) follow Semantic Versioning (SemVer) or Calendar Versioning (CalVer).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-3 |
|---|
Execute Test
Software has a persistent identifier which resolves
This test checks if there is at least one persistent identifier (i.e., Software Heritage ID, Zenodo DOI) in the README file of the source code repository and if said identifier resolves.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-01-1 |
|---|
Execute Test
Software has a persistent identifier which resolves
This test checks if there is at least one persistent identifier (i.e., Software Heritage ID, Zenodo DOI) in the README file of the source code repository and if said identifier resolves.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-01-1 |
|---|
Execute Test
Releases have an id and version number
This test checks if each release has an identifier and version number. This is achieved by checking if there’s any releases created in the repository and that they have a tag and a URL.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-2 |
|---|
Execute Test
Releases have an id and version number
This test checks if each release has an identifier and version number. This is achieved by checking if there’s any releases created in the repository and that they have a tag and a URL.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-2 |
|---|
Execute Test
Last release consistency
This test checks if the last release tag version number in the source code repository (if there is one) corresponds to the version number stated in the package file of the repository. This is achieved by checking if the version of the last release created in the repository corresponds to the version stated in the package file in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-5 |
|---|
Execute Test
Last release consistency
This test checks if the last release tag version number in the source code repository (if there is one) corresponds to the version number stated in the package file of the repository. This is achieved by checking if the version of the last release created in the repository corresponds to the version stated in the package file in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-5 |
|---|
Execute Test
Installation instructions exist
This test checks if the repository has installation instructions. This is achieved by checking in the README file of the repository if there is information about the installation of the software.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-13-2 |
|---|
Execute Test
Installation instructions exist
This test checks if the repository has installation instructions. This is achieved by checking in the README file of the repository if there is information about the installation of the software.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-13-2 |
|---|
Execute Test
Dependencies are machine-readable
This test checks if dependencies are in a machine-readable file (not just in README). This is done by checking if dependencies are available in a machine-readable format like requirements.txt or pom.xml in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-13-4 |
|---|
Execute Test
Dependencies are machine-readable
This test checks if dependencies are in a machine-readable file (not just in README). This is done by checking if dependencies are available in a machine-readable format like requirements.txt or pom.xml in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-13-4 |
|---|
Execute Test
Dependencies have version numbers
This test checks if dependencies have version numbers. This is achieved by checking if all dependencies listed in machine-readable files and in the README file have a version number.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-13-3 |
|---|
Execute Test
Dependencies have version numbers
This test checks if dependencies have version numbers. This is achieved by checking if all dependencies listed in machine-readable files and in the README file have a version number.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-13-3 |
|---|
Execute Test
A README file exists
This test checks if there is a README file in the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-2 |
|---|
Execute Test
A README file exists
This test checks if there is a README file in the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-2 |
|---|
Execute Test
A README file exists
This test checks if there is a README file in the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-2 |
|---|
Execute Test
There is a codemeta file
This test checks if a codemeta.json file exists in the repository. This is done by looking for a codemeta.json file in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-5 |
|---|
Execute Test
There is a codemeta file
This test checks if a codemeta.json file exists in the repository. This is done by looking for a codemeta.json file in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-5 |
|---|
Execute Test
There is a codemeta file
This test checks if a codemeta.json file exists in the repository. This is done by looking for a codemeta.json file in the root of the repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-5 |
|---|
Execute Test
Authors are declared
This test checks if there are authors found in the repository. This is done by looking for authors in files like AUTHORS, codemeta.json and CITATION.cff.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-06-1 |
|---|
Execute Test
Authors are declared
This test checks if there are authors found in the repository. This is done by looking for authors in files like AUTHORS, codemeta.json and CITATION.cff.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-06-1 |
|---|
Execute Test
Metadata record in Software Heritage or Zenodo
This test checks if a metadata record is found on Zenodo and/or Software Heritage. This is done by searching in the README file for a Zenodo or Software Heritage badge.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-08-1 |
|---|
Execute Test
Metadata record in Software Heritage or Zenodo
This test checks if a metadata record is found on Zenodo and/or Software Heritage. This is done by searching in the README file for a Zenodo or Software Heritage badge.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-08-1 |
|---|
Execute Test
Metadata record in Software Heritage or Zenodo
This test checks if a metadata record is found on Zenodo and/or Software Heritage. This is done by searching in the README file for a Zenodo or Software Heritage badge.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-08-1 |
|---|
Execute Test
Software has descriptive metadata
This test checks if descriptive metadata within the repository includes description, programming language, date created and keywords. This is done by looking for those fields in codemeta.json, README, CITATION.cff or any package metadata file ( (e.g., setup.py, setup.cfg, pom.xml, etc.).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-4 |
|---|
Execute Test
Software has descriptive metadata
This test checks if descriptive metadata within the repository includes description, programming language, date created and keywords. This is done by looking for those fields in codemeta.json, README, CITATION.cff or any package metadata file ( (e.g., setup.py, setup.cfg, pom.xml, etc.).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-4 |
|---|
Execute Test
Software has descriptive metadata
This test checks if descriptive metadata within the repository includes description, programming language, date created and keywords. This is done by looking for those fields in codemeta.json, README, CITATION.cff or any package metadata file ( (e.g., setup.py, setup.cfg, pom.xml, etc.).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-4 |
|---|
Execute Test
Title and description are declared
This test checks if the repository has title and description of the software available within any metadata file. This is achieved by checking if description and title are in the README file, codemeta.json file or any other package file (e.g., setup.py, setup.cfg, pom.xml, etc.).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-3 |
|---|
Execute Test
Title and description are declared
This test checks if the repository has title and description of the software available within any metadata file. This is achieved by checking if description and title are in the README file, codemeta.json file or any other package file (e.g., setup.py, setup.cfg, pom.xml, etc.).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-3 |
|---|
Execute Test
Title and description are declared
This test checks if the repository has title and description of the software available within any metadata file. This is achieved by checking if description and title are in the README file, codemeta.json file or any other package file (e.g., setup.py, setup.cfg, pom.xml, etc.).
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-04-3 |
|---|
Execute Test
There is an article citation or reference publication
This test checks if there is a referencePublication or a citation file to a paper. This is done by looking for an article citation in the README file, for a CITATION.cff file or a referencePublication field in the codemeta.json file.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-12-1 |
|---|
Execute Test
Repository has citation
This test checks if there is a CITATION.cff file or citations made in the README file. This is done by looking in the root of the repository for a CITATION.cff file and by checking if the README file contains citations in a bibtex format.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-18-1 |
|---|
Execute Test
There are actions to automate tests
This test checks if there are actions or workflows that automate tests. This is done by checking if there are workflows that mention “test” in their names in .github.workflows directory for Github and .gitlab-ci.yml file for Gitlab.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-14-2 |
|---|
Execute Test
License referenced in metadata files
This test checks if metadata files like codemeta.json, CITATION.cff and package file mention the repository license. This is done by looking if a license field is within said files.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-16-1 |
|---|
Execute Test
FAIR Test - ARK T-F1 - Persistent identifiers for database content
The 'FAIR Test ARK T-F1 - Persistent Identifiers for Database Content' is a database-level test that requires the minting of persistent identifiers for at least some of the content within the database being evaluated. FM ARK F1 expects a FAIRsharing URL or DOI as its input and evaluates that FAIRsharing record for the guaranteed persistence of the identifier schema as defined by the identifier schema record type in FAIRsharing (see our gitbook documentation linked as part of this record for more information about id schemas for databases and how to curate them in a FAIRsharing record). An important facet of FAIR for databases is that they mint persistent identifiers. As described by the GFF, global uniqueness guarantees the unambiguous referencing of the described resource; it is insufficient for it to be unique only locally. Persistence refers to the requirement that this globally unique identifier is never reused elsewhere and continues to identify the same resource over time. These features are key to the Findability of the database being evaluated. The test will return as follows: Pass: URL/DOI must point to an existing FAIRsharing database record; the record must have an 'implements' to an id_schema record; that id_schema record must have the persistent field set to 'true'. Indeterminate: URL/DOI is non-existent or malformed. Fail: if any of the conditions in 'pass' fail; specifically, if the URL/DOI is not a database record, OR if there is no 'implements' relationship to an id_schema, OR if the persistent field is set to 'false'.
Additional Details
| Endpoint | https://api.fairsharing.org/fair_tests/ft_ark_f1 |
|---|
Execute Test
FAIR Test - ARK T-F1 - Globally unique, persistent and resolvable identifiers for database content
The 'FAIR Test - ARK T-F1 - Globally unique, persistent and resolvable identifiers for database content' is a database-level test that requires the minting of community-relevant, publicly available GUPRIs for at least some of the content within the database being evaluated. FM ARK F1-GUPRI expects a FAIRsharing URL or DOI as its input and evaluates the database described by the FAIRsharing record for the guaranteed global uniqueness, persistence and resolvability of the identifier schema as defined by the identifier schema record type in FAIRsharing. As described by the GFF, global uniqueness guarantees the unambiguous referencing of the described resource; it is insufficient for it to be unique only locally. Persistence refers to the requirement that this globally unique identifier is never reused elsewhere and continues to identify the same resource over time. Resolvability of identifier makes it practically useful, with predictable identifier resolution behavior being key. These features are key to the Findability of the database being evaluated. The test will return as follows: Pass: URL/DOI must point to an existing FAIRsharing database record; the record must have an 'implements' to an id_schema record; that id_schema record must have the globally unique, persistent and resolvable fields all set to 'true'. Indeterminate: URL/DOI is non-existent or malformed. Fail: if any of the conditions in 'pass' fail; specifically, if the URL/DOI is not a database record, OR if there is no 'implements' relationship to an id_schema, OR if any of globally unique, persistent and resolvable fields are set to 'false'.
Additional Details
| Endpoint | https://api.fairsharing.org/fair_tests/ft_ark_f1gupri |
|---|
Execute Test
FAIR Test - ARK T-A2 - Database has a preservation policy
The 'FAIR Test - ARK T-A2 - Database has a preservation policy' is a database-level test that requires the presence of a data preservation policy for the database being evaluated. FM ARK A2-Preservation expects a FAIRsharing URL or DOI as its input and evaluates the database described by the FAIRsharing record: the record must have a URL in the data preservation policy field and may optionally also have a non-empty value in the name field. As described by the GFF, there should at least be access to high quality and machine actionable metadata that describes those resources sufficiently to minimally understand their nature and their provenance, even when the relevant data are not available anymore. There are a number of ways to implement this, however this metric deals with preservation of information relating to an identifier by determining if there is a preservation policy in place with the database being evaluated. The test will return as follows: Pass: URL/DOI must point to an existing FAIRsharing database record; the record must have a value in the URL section of the data preservation policy field that resolves (i.e. does not give an error code). Indeterminate: URL/DOI is non-existent, returns an error code of some kind, or is malformed. Fail: if any of the conditions in 'pass' fail; specifically, if the URL/DOI is not a database record, OR if there is an empty URL value for the data preservation policy field.
Additional Details
| Endpoint | https://api.fairsharing.org/fair_tests/ft_ark_a2preservation |
|---|
Execute Test
Version number in metadata
This test checks if there is a version stated for the software in metadata files. This is done by looking for a version number in metadata files like package files, codemeta.json and CITATION.cff.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-6 |
|---|
Execute Test
Version number in metadata
This test checks if there is a version stated for the software in metadata files. This is done by looking for a version number in metadata files like package files, codemeta.json and CITATION.cff.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-03-6 |
|---|
Execute Test
Authors have roles
This test checks if authors have their roles stated in a codemeta.json. This is achieved by looking for authors in the codemeta.json file and checking if all of them have a role assigned. This process follows the codemeta v2 and v3 standards.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-06-4 |
|---|
Execute Test
Authors have roles
This test checks if authors have their roles stated in a codemeta.json. This is achieved by looking for authors in the codemeta.json file and checking if all of them have a role assigned. This process follows the codemeta v2 and v3 standards.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-06-4 |
|---|
Execute Test
Repository has an issue tracker
This test checks if the repository has an issue tracker. This is done by checking if the URL for the issues resolves.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-20-1 |
|---|
Execute Test
Commit history
This test checks if the repository has a commit history. This is done by looking for commits in the software’s repository.
Additional Details
| Endpoint | https://rsfc.linkeddata.es/assess/test/RSFC-17-2 |
|---|
Execute Test
FAIR Test - Metadata Contains CESSDA Provenance Information
Verifies that a record contains provenance metadata elements. The test examines three elements: distrbtr (distributor/publisher) in the distribution statement (/codeBook/stdyDscr/citation/distStmt/distrbtr) AuthEnty (author/authoring entity) in the responsibility statement (/codeBook/stdyDscr/citation/rspStmt/AuthEnty) grantNo (grant number) in the production statement (/codeBook/stdyDscr/citation/prodStmt/grantNo) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/provenance |
|---|
Execute Test
FAIR Test - Metadata Contains CESSDA Provenance Information
Verifies that a record contains provenance metadata elements. The test examines three elements: distrbtr (distributor/publisher) in the distribution statement (/codeBook/stdyDscr/citation/distStmt/distrbtr) AuthEnty (author/authoring entity) in the responsibility statement (/codeBook/stdyDscr/citation/rspStmt/AuthEnty) grantNo (grant number) in the production statement (/codeBook/stdyDscr/citation/prodStmt/grantNo) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/provenance |
|---|
Execute Test
FAIR Test - Metadata Uses DDI Time Method Vocabulary
Validates that a record uses DDI Time Method controlled vocabulary. The test examines timeMeth (time method) elements in the data collection method section (/codeBook/stdyDscr/method/dataColl/timeMeth) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/ddi-time-method |
|---|
Execute Test
FAIR Test - Metadata Uses DDI Time Method Vocabulary
Validates that a record uses DDI Time Method controlled vocabulary. The test examines timeMeth (time method) elements in the data collection method section (/codeBook/stdyDscr/method/dataColl/timeMeth) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/ddi-time-method |
|---|
Execute Test
FAIR Test - Metadata Uses DDI Mode Of Collection Vocabulary
Confirms that a record uses DDI Mode of Collection controlled vocabulary. The test examines collMode (collection mode) elements in the data collection method section (/codeBook/stdyDscr/method/dataColl/collMode) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/ddi-collection-mode |
|---|
Execute Test
FAIR Test - Metadata Uses DDI Mode Of Collection Vocabulary
Confirms that a record uses DDI Mode of Collection controlled vocabulary. The test examines collMode (collection mode) elements in the data collection method section (/codeBook/stdyDscr/method/dataColl/collMode) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/ddi-collection-mode |
|---|
Execute Test
FAIR Test - Metadata Uses DDI Sampling Procedure Vocabulary
Checks whether a record uses DDI Sampling Procedure controlled vocabulary. The test examines sampProc (sampling procedure) elements in the data collection method section (/codeBook/stdyDscr/method/dataColl/sampProc) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/ddi-sampleproc |
|---|
Execute Test
FAIR Test - Metadata Uses DDI Sampling Procedure Vocabulary
Checks whether a record uses DDI Sampling Procedure controlled vocabulary. The test examines sampProc (sampling procedure) elements in the data collection method section (/codeBook/stdyDscr/method/dataColl/sampProc) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/ddi-sampleproc |
|---|
Execute Test
FAIR Test – Metadata Uses DDI Analysis Unit Vocabulary
Verifies that a record uses DDI Analysis Unit controlled vocabulary. The test examines anlyUnit (analysis unit) elements in the study description's summary description section (/codeBook/stdyDscr/stdyInfo/sumDscr/anlyUnit) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/ddi-analysis-unit |
|---|
Execute Test
FAIR Test – Metadata Uses DDI Analysis Unit Vocabulary
Verifies that a record uses DDI Analysis Unit controlled vocabulary. The test examines anlyUnit (analysis unit) elements in the study description's summary description section (/codeBook/stdyDscr/stdyInfo/sumDscr/anlyUnit) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/ddi-analysis-unit |
|---|
Execute Test
FAIR Test - Metadata Uses CESSDA Topic Vocabulary
Checks whether a record uses CESSDA Topic Classification controlled vocabulary. The test examines topcClas (topic classification) elements in the study information subject section (/codeBook/stdyDscr/stdyInfo/subject/topcClas) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/topic-class |
|---|
Execute Test
FAIR Test - Metadata Uses CESSDA Topic Vocabulary
Checks whether a record uses CESSDA Topic Classification controlled vocabulary. The test examines topcClas (topic classification) elements in the study information subject section (/codeBook/stdyDscr/stdyInfo/subject/topcClas) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/topic-class |
|---|
Execute Test
FAIR Test - Metadata Uses CESSDA ELSST Keywords
Validates that a record contains properly attributed ELSST (European Language Social Science Thesaurus) keywords. The test examines keyword elements in the study information subject section (/codeBook/stdyDscr/stdyInfo/subject/keyword) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/elsst-keywords |
|---|
Execute Test
FAIR Test - Metadata Uses CESSDA ELSST Keywords
Validates that a record contains properly attributed ELSST (European Language Social Science Thesaurus) keywords. The test examines keyword elements in the study information subject section (/codeBook/stdyDscr/stdyInfo/subject/keyword) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/elsst-keywords |
|---|
Execute Test
FAIR Test - Metadata Uses CESSDA Access Rights Vocabulary
Verifies that a record contains approved access rights terminology. The test examines the conditions element within the data access section (/codeBook/stdyDscr/dataAccs/useStmt/conditions) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/access-rights |
|---|
Execute Test
FAIR Test - Metadata Uses CESSDA Access Rights Vocabulary
Verifies that a record contains approved access rights terminology. The test examines the conditions element within the data access section (/codeBook/stdyDscr/dataAccs/useStmt/conditions) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/access-rights |
|---|
Execute Test
FAIR Test – Identifiers use ARK, DOI, HANDLE or URN PID schemas
Confirms that a DDI 2.5 metadata record uses an approved persistent identifier scheme. The test examines IDNo elements with agency attributes in the citation's title statement section (/codeBook/stdyDscr/citation/titlStmt/IDNo) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/pid |
|---|
Execute Test
FAIR Test – Identifiers use ARK, DOI, HANDLE or URN PID schemas
Confirms that a DDI 2.5 metadata record uses an approved persistent identifier scheme. The test examines IDNo elements with agency attributes in the citation's title statement section (/codeBook/stdyDscr/citation/titlStmt/IDNo) of DDI 2.5 metadata.
Additional Details
| Endpoint | https://fair-tests.cessda.eu/assess/test/pid |
|---|
Execute Test
Funding information registered in DOI metadata
Test a DOI to determine if funder information is available in the datacite or crossref metadata
Additional Details
| Endpoint | https://tests.ostrails.eu/community-tests/assess/test/community_funding_information_registered |
|---|
Execute Test
License information found in DOI metadata
Test a DOI to determine if license information is available in the datacite or crossref metadata
Additional Details
| Endpoint | https://tests.ostrails.eu/community-tests/assess/test/community_license_information |
|---|
Execute Test
Metadata includes author affiliation
Use Crossref and Datacite APIs to scan a metadata record for author affiliation. Also check landing page for citation_author_institution meta property
Additional Details
| Endpoint | https://tests.ostrails.eu/community-tests/assess/test/community_metadata_includes_author_affiliation |
|---|
Resource is Open-Access output
Test a DOI against OpenAlex to determine if the resource output is open-access
Additional Details
| Endpoint | https://tests.ostrails.eu/community-tests/assess/test/community_open_access_publication |
|---|