FAIR principle | Implemented | Comment |
---|---|---|
F1. (Meta)data are assigned a globally unique and persistent identifier | Yes | Internal UUID is generated for each instance of proteins, mutations, ligands and dockings. The database as a whole. the web application, and the libraries made for executing the steps of the workflow are all preserved through Zeonodo with a DOI assigned to each of them. |
F2. Data are described with rich metadata | Yes | All instances are annotated and well described from the relevant sources (PDB, UniProt, NCBI Taxon and ChEMBL) |
F3. Metadata clearly and explicitly include the identifier of the data they describe | Yes | |
F4. (Meta)data are registered or indexed in a searchable resource | Yes | The dataset will be submitted to re3data.org and Google Dataset |
A1. (Meta)data are retrievable by their identifier using a standardised communications protocol | Yes | HTTP(S) protocol is used with a REST API for all communications with the server |
A2. Metadata are accessible, even when the data are no longer available | Yes | In progress |
I1. (Meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation. | Yes | JSON-LD is used to describe main protein entities. The REST API adopts the OpenAPI specification v3 and it is described using Swagger. |
I2. (Meta)data use vocabularies that follow FAIR principles | Yes | The structured markup (JSON-LD) uses the schema.org and bioschema.org vocabularies. |
R1. (Meta)data are richly described with a plurality of accurate and relevant attributes | Yes | License, usage and provenance info are all provided. |