diff --git a/docs/data-model/pids-and-identifiers.md b/docs/data-model/pids-and-identifiers.md index dfafe16..4e891c8 100644 --- a/docs/data-model/pids-and-identifiers.md +++ b/docs/data-model/pids-and-identifiers.md @@ -7,28 +7,21 @@ Not only, but the mappings applied to the original contents may also change and ## PID Authorities -One of the fronts regards the attribution of the identity to the objects populating the graph. The basic idea is to build the identifiers of the objects in the graph from the PIDs available in some authoritative sources while considering all the other sources as by definition “unstable”. Examples of authoritative sources are Crossref and DataCite. Examples of non-authoritative ones are institutional repositories, aggregators, etc. PIDs from the authoritative sources would form the stable OpenAIRE ID skeleton of the Graph, precisely because they are immutable by construction. +One of the fronts, regards the attribution of the identity to the objects populating the Graph. The basic idea is to build the identifiers of the objects in the Graph from the PIDs available in some authoritative sources, while considering all the other sources as by definition “unstable”. +For instance, Crossref and DataCite are considered to be authoritative sources for results, +contrary to institutional repositories, aggregators, etc. +PIDs from the authoritative sources would form the stable OpenAIRE ID skeleton of the Graph, precisely because they are immutable by construction. Such a policy defines a list of data sources that are considered authoritative for a specific type of PID they provide, whose effect is twofold: -* OpenAIRE IDs depend on persistent IDs when they are provided by the authority responsible to create them -* PIDs are included in the graph according to a tight criterion: the PID Types declared in the table below are considered to be mapped as PIDs only when they are collected from the relative PID authority data source. - -[PID authorities table was removed from here] +* OpenAIRE IDs depend on persistent IDs when they are provided by the authority responsible to create them. +* PIDs are included in the Graph according to a tight criterion: + +PIDs are considered valid only when they are collected from a relative PID authority data source. +For each entity, we outline the PID authorities per PID Type in the [following section](#pid-authorities-per-entity). +[TODO: refine this part if not accurate] There is an exception though: Handle(s) are minted by several repositories; as listing them all would not be a viable option, to avoid losing them as PIDs, Handles bypass the PID authority filtering rule. -In all other cases, PIDs are be included in the graph as alternate Identifiers. - -## Delegated authorities - -When a record is aggregated from multiple sources considered authoritative for minting specific PIDs, different mappings could be applied to them and, depending on the case, -this could result in inconsistencies in the attribution of the field values. -To overcome the issue, the intuition is to include such records only once in the graph. To do so, the concept of "delegated authorities" defines a list of datasources that -assigns PIDs to their scientific products from a given PID minter. - -This "selection" can be performed when the entities in the graph sharing the same identifier are grouped together. The list of the delegated authorities currently includes - -[deletated authorities table was removed from here] - +In all other cases, PIDs are be included in the Graph as alternate Identifiers. ## Identifiers in the Graph @@ -37,9 +30,8 @@ By default, the internal identifier is generated as `sourcePrefix::md5(localId)` * `sourcePrefix` is a namespace prefix of 12 chars assigned to the data source at registration time * `localId` is the identifier assigned to the object by the data source -[so, the openaire id of objects with no pid is based on this local id; is this always available?] -After years of operation, we can say that: +After years of operation, we can conclude that: * `localId` are generally unstable * objects can disappear from sources @@ -54,47 +46,51 @@ When the record is collected from a source which is not authoritative for any ty * the identity of the record is forged as usual using the local identifier * the PID, if available, is added as `alternateIdentifier` -Currently, the following data sources are used as "PID authorities": +You can review the list of the PID authorities per entity in the [following section](#pid-authorities-per-entity). -[PID authorities table was removed from here] - - - -OpenAIRE also perform duplicate identification (see the [dedicated section for details](/graph-production-workflow/deduplication)). +OpenAIRE also performs duplicate identification (see the [dedicated section for details](/graph-production-workflow/deduplication)). All duplicates are **merged** together in a **representative record** which must be assigned a dedicated OpenAIRE identifier (i.e. it cannot have the identifier of one of the aggregated record). ## PID authorities per entity +This section gathers all PID Types and their respective authorities for each entity in the Graph. + ### Result -| PID Type | Authority | -|-----------|-----------------------------------------------------------------------------------------------------| -| doi | [Crossref](https://www.crossref.org), [Datacite](https://datacite.org) | -| pmc, pmid | [Europe PubMed Central](https://europepmc.org/), [PubMed Central](https://www.ncbi.nlm.nih.gov/pmc) | -| arXiv | [arXiv.org e-Print Archive](https://arxiv.org/) | -| uniprot | [Protein Data Bank](http://www.pdb.org/) | -| ena | [Protein Data Bank](http://www.pdb.org/) | -| pdb | [Protein Data Bank](http://www.pdb.org/) | +| PID Type | Authority | OpenAIRE ID prefix (12 chars) | +|-----------|------------------------|-----------------------| +| doi | [Crossref](https://www.crossref.org), [Datacite](https://datacite.org), Zenodo | `doi_________` +| pmid | [Europe PubMed Central](https://europepmc.org/), [PubMed Central](https://www.ncbi.nlm.nih.gov/pmc) | `pmid________` +| pmc | [Europe PubMed Central](https://europepmc.org/), [PubMed Central](https://www.ncbi.nlm.nih.gov/pmc) | `pmc_________` +| arXiv | [arXiv.org e-Print Archive](https://arxiv.org/) | `arXiv_______` +| uniprot | [Protein Data Bank](http://www.pdb.org/) [ or EMBL-EBI ?] | `uniprot_____` +| ena | [Protein Data Bank](http://www.pdb.org/) [ or EMBL-EBI ?] | `ena_________` +| pdb | [Protein Data Bank](http://www.pdb.org/) [ or EMBL-EBI ?] | `pdb_________` +| handle | Any repository | `handle______` + +#### Delegated authorities + +[TODO: the problem that this solves is that we can get a specific PID from more than one auhtoritative sources right ? For example, if we get DOIs from Crossref, Datacite, and Zenodo (btw Zenodo was not mentioned in the first table). +Can't we mention those sources by priority in the first table and simply mention in the text that we prefer to collect those PIDs starting from the first till the last one? Is this the problem or I am missing something else here?] + +When a record is aggregated from multiple sources considered authoritative for minting specific PIDs, different mappings could be applied to them and, depending on the case, +this could result in inconsistencies in the attribution of the field values. +To overcome the issue, the intuition is to include such records only once in the Graph. To do so, the concept of "delegated authorities" defines a list of datasources that +assigns PIDs to their scientific products from a given PID minter. + +This "selection" can be performed when the entities in the Graph sharing the same identifier are grouped together. +The list of the delegated authorities currently includes the following: -| Datasource delegated | Datasource delegating | Pid Type | +| PID Type | Datasource delegated | Datasource delegating | |--------------------------------------|----------------------------------|-----------| -| [Zenodo](https://zenodo.org) | [Datacite](https://datacite.org) | doi | -| [RoHub](https://reliance.rohub.org/) | [W3ID](https://w3id.org/) | w3id | +| doi | [Zenodo](https://zenodo.org) | [Datacite](https://datacite.org) | +| w3id [is not mentioned in the table above] | [RoHub](https://reliance.rohub.org/) | [W3ID](https://w3id.org/) | -| PID Type | Prefix (12 chars) | Authority | -|-----------|------------------------|-------------------------------------------| -| doi | `doi_________` | Crossref, Datacite, Zenodo | -| pmc | `pmc_________` | Europe PubMed Central, PubMed Central | -| pmid | `pmid________` | Europe PubMed Central, PubMed Central | -| arXiv | `arXiv_______` | arXiv.org e-Print Archive | -| handle | `handle______` | any repository | -| ena | `ena_________` | EMBL-EBI | -| pdb | `pdb_________` | EMBL-EBI | -| uniprot | `uniprot_____` | EMBL-EBI | ### Data source +[TODO] ### Organization @@ -104,5 +100,9 @@ All duplicates are **merged** together in a **representative record** which must
* explain what is "pending" in the openaire id of some organizations
### Project +[TODO] + ### Community +[TODO] +