{"_id":"568fb2cc94c5030d002880ac","category":{"_id":"5624e1195a86b423009462ec","project":"5613d8fc6a092921004c30b9","__v":5,"pages":["568faefa21fcf0190071d890","568fb2cc94c5030d002880ac","568fb484769f210d001324d6","568fb4c89ebef90d008727f4","568fdc9b769f210d00132547"],"version":"5613d8fc6a092921004c30bc","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-10-19T12:24:57.625Z","from_sync":false,"order":1,"slug":"case-studies","title":"Case studies"},"user":"5624dd1472ac510d00e4919c","__v":26,"version":{"_id":"5613d8fc6a092921004c30bc","__v":10,"project":"5613d8fc6a092921004c30b9","createdAt":"2015-10-06T14:21:48.908Z","releaseDate":"2015-10-06T14:21:48.908Z","categories":["5613d8fd6a092921004c30bd","5614ef94a4ccab0d00e698b5","5614ef9abeee6f0d009df1a2","5614efb2a4ccab0d00e698b6","5624cb406ff1010d009b1611","5624ce8772ac510d00e4918b","5624e1195a86b423009462ec","568e68490844350d002ffa47","568e6b010844350d002ffa4a","568e6b65d892e80d00a5d37a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"project":"5613d8fc6a092921004c30b9","parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-01-08T12:59:56.898Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"There are three important uses for linking persistent identifiers:\n  * linking between [versions](#section-versions) of research outputs, particularly data\n  * linking between articles and their [supporting data](#section-related-works) and code\n  * linking between research outputs and their [contributors, institutions and funding sources](#section-linking-creators-and-contributors).\n\nThese links are important for navigating the research landscape, but also allow us to look at the far reaching impact of each individual contributor, paper, dataset and grant.\n\nHere we will give examples of how data repositories have linked identifiers to give us a much better view of research networks and dependencies.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Versions and related works\"\n}\n[/block]\nMany repositories using DataCite to assign DOIs to their content use their metadata to make links between resources. The [DataCite metadata schema](doc:datacite-metadata-schema) contains the field RelatedIdentifier which makes this possible. This field explains the relationship and gives the identifier locating the related item.\n\n##Versions\nThe UK's [Archaeology Data Service](http://archaeologydataservice.ac.uk) uses the RelatedIdentifier to show the relationship between different versions of a dataset. More information on versioning data can be found in [Examples of versioning with identifiers](doc:examples-of-versioning-with-identifiers).\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"<relatedIdentifiers>\\n\\t<relatedIdentifier relatedIdentifierType=\\\"DOI\\\" relationType=\\\"IsNewVersionOf\\\">10.5284/1000417</relatedIdentifier>\\n\\t<relatedIdentifier relatedIdentifierType=\\\"DOI\\\" relationType=\\\"IsNewVersionOf\\\">10.5284/1000341</relatedIdentifier>\\n</relatedIdentifiers>\",\n      \"language\": \"xml\",\n      \"name\": \"XML showing related identifiers for http://doi.org/10.5284/1011897\"\n    }\n  ]\n}\n[/block]\n##Related works\nThis dataset from [Durham University](http://durham.ac.uk) links to the paper that has cited the data, as well as the software that was used during creation of the data.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"<relatedIdentifiers>\\n    <relatedIdentifier relatedIdentifierType='URL' relationType='IsCitedBy'>http://dx.doi.org/10.1016/j.ssnmr.2015.05.003</relatedIdentifier>\\n    <relatedIdentifier relatedIdentifierType='URL' relationType='Cites'>https://www.dur.ac.uk/solids.nmr/software/pnmrsim/</relatedIdentifier>\\n</relatedIdentifiers>\",\n      \"language\": \"xml\",\n      \"name\": \"XML showing related identifiers for http://doi.org/10.15128/KK991FK96D\"\n    }\n  ]\n}\n[/block]\nIn order to make this a bi-directional link, the persistent identifier, expressed as a URI, should also be used by papers citing data and code.\n\nOutside of DOIs, the [EBI](http://www.ebi.ac.uk) provides a number of life science data resources. Many of these link to related data across the EBI services, as shown in the image below.\n[block:image]\n{\n  \"images\": [\n    {\n      \"caption\": \"Cross-linking of major life science resources at EMBL-EBI (source: EMBL-EBI)\",\n      \"image\": [\n        \"https://files.readme.io/UIuwpcLREqpGFD39RDnA_ebilinks.png\",\n        \"ebilinks.png\",\n        \"590\",\n        \"576\",\n        \"#b8956e\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n##Alternate identifiers\nThe DataCite metadata schema also allows for secondary identifiers that relate to the exact same object. These alternate identifiers tend to be internal IDs or local accession numbers, which are not necessarily globally unique, but may provide additional context. For instance, the InChI for data relating to specific chemical compound:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"<alternateIdentifiers>\\n\\t<alternateIdentifier alternateIdentifierType=\\\"InChI\\\">InChI=1S/C6H10NO2.2H2O/c1-3-4(2)6(9)7-5(3)8;;/h3-4H,1-2H3,(H2,7,8,9);2*1H2/t3-,4-;;/m0../s1</alternateIdentifier>\\n  <alternateIdentifier alternateIdentifierType=\\\"InChIKey\\\">UQPNWVSPCKRRTR-RGVONZFCSA-N</alternateIdentifier>\\n  <alternateIdentifier alternateIdentifierType=\\\"Handle\\\">10042/132754</alternateIdentifier>\\n</alternateIdentifiers>\",\n      \"language\": \"xml\",\n      \"name\": \"XML showing alternative identifiers for http://doi.org/10.14469/CH/127757\"\n    }\n  ]\n}\n[/block]\nFor more on how to integrate DataCite in to you repository, see [Examples of DataCite integration](doc:examples-of-datacite-integration-1).\n\nAcross the EBI, many services have multiple identifiers, which can reflect the evolution of a resource. A small group of services have DOIs alongside original accession numbers, although practice is not widespread.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Linking creators and contributors\"\n}\n[/block]\nThe metadata for an item can also be used to link to the identity of its creators and contributors. The DataCite metadata also supports name identifiers. The example below is for data held in [PANGAEA](https://www.pangaea.de/).\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"<creator>\\n  <creatorName>Dengler, Marcus</creatorName>\\n  <nameIdentifier nameIdentifierScheme=\\\"ORCID\\\" schemeURI=\\\"http://orcid.org\\\">0000-0001-5993-9088</nameIdentifier>\\n</creator>\",\n      \"language\": \"xml\",\n      \"name\": \"XML showing nameIdentifiers for http://doi.org/10.1594/PANGAEA.858896\"\n    }\n  ]\n}\n[/block]\nIn many cases, contributors are individuals, but the vocabulary for the Contributor field allows exploration of organisational relationships. Contributors and Creators can be organisations, but there are contributorTypes that relate specifically to organisations. These are:\n  * Distributor\n  * Funder\n  * HostingInstitution\n  * RegistrationAgency\n  * RegistrationAuthority\n  * ResearchGroup\n\nThe question of appropriate identifiers for organisations is an open one, but there are examples of organisation identifiers in DataCite:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"<creators>\\n    <creator>\\n      <creatorName>UCD Archives</creatorName>\\n      <nameIdentifier nameIdentifierScheme=\\\"ISNI\\\">0000000404462544</nameIdentifier>\\n    </creator>\\n</creators>\",\n      \"language\": \"xml\",\n      \"name\": \"XML showing the organisation ID included in http://doi.org/10.7925/DRS1.UCDLIB_38829\"\n    }\n  ]\n}\n[/block]\nORCID has been using ISNIs as organisation identifiers for some time, and so it is possible to link datasets without organisational information to relevant organisations via the ORCID records of its individual creators and contributors. For instance, for our ORCID example in PANGAEA above, we can see that the creator is employed by the Helmholtz Centre for Ocean Research Kiel and so the data is related to that organisation (ISNI:0000-0000-9056-9663). \n\n##Versions of identities\nThere are disciplines where people may wish to create separate identities and have separate identifiers and records for them. In such cases, ORCID does not link between identifiers. However, unintentional duplicate ORCID iDs do occur. To deal with this, ORCID depreciates one iD and ensures that it points to the primary record.This ensures the persistence of the depreciated ORCID iD, but allows users to navigate to the appropriate record.\n\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"body\": \"Fenner, Martin et al.. (2016). THOR: Conceptual Model of Persistent Identifier Linking. Zenodo. http://doi.org/10.5281/zenodo.48705\",\n  \"title\": \"Content for this article was drawn from:\"\n}\n[/block]","excerpt":"","slug":"examples-of-linking-across-identifiers","type":"basic","title":"Examples of linking across identifiers"}

Examples of linking across identifiers


There are three important uses for linking persistent identifiers: * linking between [versions](#section-versions) of research outputs, particularly data * linking between articles and their [supporting data](#section-related-works) and code * linking between research outputs and their [contributors, institutions and funding sources](#section-linking-creators-and-contributors). These links are important for navigating the research landscape, but also allow us to look at the far reaching impact of each individual contributor, paper, dataset and grant. Here we will give examples of how data repositories have linked identifiers to give us a much better view of research networks and dependencies. [block:api-header] { "type": "basic", "title": "Versions and related works" } [/block] Many repositories using DataCite to assign DOIs to their content use their metadata to make links between resources. The [DataCite metadata schema](doc:datacite-metadata-schema) contains the field RelatedIdentifier which makes this possible. This field explains the relationship and gives the identifier locating the related item. ##Versions The UK's [Archaeology Data Service](http://archaeologydataservice.ac.uk) uses the RelatedIdentifier to show the relationship between different versions of a dataset. More information on versioning data can be found in [Examples of versioning with identifiers](doc:examples-of-versioning-with-identifiers). [block:code] { "codes": [ { "code": "<relatedIdentifiers>\n\t<relatedIdentifier relatedIdentifierType=\"DOI\" relationType=\"IsNewVersionOf\">10.5284/1000417</relatedIdentifier>\n\t<relatedIdentifier relatedIdentifierType=\"DOI\" relationType=\"IsNewVersionOf\">10.5284/1000341</relatedIdentifier>\n</relatedIdentifiers>", "language": "xml", "name": "XML showing related identifiers for http://doi.org/10.5284/1011897" } ] } [/block] ##Related works This dataset from [Durham University](http://durham.ac.uk) links to the paper that has cited the data, as well as the software that was used during creation of the data. [block:code] { "codes": [ { "code": "<relatedIdentifiers>\n <relatedIdentifier relatedIdentifierType='URL' relationType='IsCitedBy'>http://dx.doi.org/10.1016/j.ssnmr.2015.05.003</relatedIdentifier>\n <relatedIdentifier relatedIdentifierType='URL' relationType='Cites'>https://www.dur.ac.uk/solids.nmr/software/pnmrsim/</relatedIdentifier>\n</relatedIdentifiers>", "language": "xml", "name": "XML showing related identifiers for http://doi.org/10.15128/KK991FK96D" } ] } [/block] In order to make this a bi-directional link, the persistent identifier, expressed as a URI, should also be used by papers citing data and code. Outside of DOIs, the [EBI](http://www.ebi.ac.uk) provides a number of life science data resources. Many of these link to related data across the EBI services, as shown in the image below. [block:image] { "images": [ { "caption": "Cross-linking of major life science resources at EMBL-EBI (source: EMBL-EBI)", "image": [ "https://files.readme.io/UIuwpcLREqpGFD39RDnA_ebilinks.png", "ebilinks.png", "590", "576", "#b8956e", "" ] } ] } [/block] ##Alternate identifiers The DataCite metadata schema also allows for secondary identifiers that relate to the exact same object. These alternate identifiers tend to be internal IDs or local accession numbers, which are not necessarily globally unique, but may provide additional context. For instance, the InChI for data relating to specific chemical compound: [block:code] { "codes": [ { "code": "<alternateIdentifiers>\n\t<alternateIdentifier alternateIdentifierType=\"InChI\">InChI=1S/C6H10NO2.2H2O/c1-3-4(2)6(9)7-5(3)8;;/h3-4H,1-2H3,(H2,7,8,9);2*1H2/t3-,4-;;/m0../s1</alternateIdentifier>\n <alternateIdentifier alternateIdentifierType=\"InChIKey\">UQPNWVSPCKRRTR-RGVONZFCSA-N</alternateIdentifier>\n <alternateIdentifier alternateIdentifierType=\"Handle\">10042/132754</alternateIdentifier>\n</alternateIdentifiers>", "language": "xml", "name": "XML showing alternative identifiers for http://doi.org/10.14469/CH/127757" } ] } [/block] For more on how to integrate DataCite in to you repository, see [Examples of DataCite integration](doc:examples-of-datacite-integration-1). Across the EBI, many services have multiple identifiers, which can reflect the evolution of a resource. A small group of services have DOIs alongside original accession numbers, although practice is not widespread. [block:api-header] { "type": "basic", "title": "Linking creators and contributors" } [/block] The metadata for an item can also be used to link to the identity of its creators and contributors. The DataCite metadata also supports name identifiers. The example below is for data held in [PANGAEA](https://www.pangaea.de/). [block:code] { "codes": [ { "code": "<creator>\n <creatorName>Dengler, Marcus</creatorName>\n <nameIdentifier nameIdentifierScheme=\"ORCID\" schemeURI=\"http://orcid.org\">0000-0001-5993-9088</nameIdentifier>\n</creator>", "language": "xml", "name": "XML showing nameIdentifiers for http://doi.org/10.1594/PANGAEA.858896" } ] } [/block] In many cases, contributors are individuals, but the vocabulary for the Contributor field allows exploration of organisational relationships. Contributors and Creators can be organisations, but there are contributorTypes that relate specifically to organisations. These are: * Distributor * Funder * HostingInstitution * RegistrationAgency * RegistrationAuthority * ResearchGroup The question of appropriate identifiers for organisations is an open one, but there are examples of organisation identifiers in DataCite: [block:code] { "codes": [ { "code": "<creators>\n <creator>\n <creatorName>UCD Archives</creatorName>\n <nameIdentifier nameIdentifierScheme=\"ISNI\">0000000404462544</nameIdentifier>\n </creator>\n</creators>", "language": "xml", "name": "XML showing the organisation ID included in http://doi.org/10.7925/DRS1.UCDLIB_38829" } ] } [/block] ORCID has been using ISNIs as organisation identifiers for some time, and so it is possible to link datasets without organisational information to relevant organisations via the ORCID records of its individual creators and contributors. For instance, for our ORCID example in PANGAEA above, we can see that the creator is employed by the Helmholtz Centre for Ocean Research Kiel and so the data is related to that organisation (ISNI:0000-0000-9056-9663). ##Versions of identities There are disciplines where people may wish to create separate identities and have separate identifiers and records for them. In such cases, ORCID does not link between identifiers. However, unintentional duplicate ORCID iDs do occur. To deal with this, ORCID depreciates one iD and ensures that it points to the primary record.This ensures the persistence of the depreciated ORCID iD, but allows users to navigate to the appropriate record. [block:callout] { "type": "success", "body": "Fenner, Martin et al.. (2016). THOR: Conceptual Model of Persistent Identifier Linking. Zenodo. http://doi.org/10.5281/zenodo.48705", "title": "Content for this article was drawn from:" } [/block]