Digital object identifier

<h2 id="nomenclature-and-syntax"> Nomenclature and syntax</h2>
A DOI is a type of Handle System handle, which takes the form of a <a href="/facts/String_(computer_science)/4ChJu5WS">character string</a> divided into two parts, a prefix and a suffix, separated by a slash.

prefix/suffix

The prefix identifies the registrant of the identifier and the suffix is chosen by the registrant and identifies the specific object associated with that DOI. Most legal <a href="/facts/Unicode/DDu3MfPV">Unicode</a> characters are allowed in these strings, which are interpreted in a <a href="/facts/Case-insensitive/VS2eGDmY">case-insensitive</a> manner. The prefix usually takes the form 10.NNNN, where NNNN is a number greater than or equal to 1000, whose limit depends only on the total number of registrants.<a class="footnote-ref" id="fnref:14" href="#fn:14">14</a><a class="footnote-ref" id="fnref:15" href="#fn:15">15</a> The prefix may be further subdivided with periods, like 10.NNNN.N.<a class="footnote-ref" id="fnref:16" href="#fn:16">16</a>
For example, in the DOI name 10.1000/182, the prefix is 10.1000 and the suffix is 182. The "10" part of the prefix distinguishes the handle as part of the DOI namespace, as opposed to some other Handle System namespace,<a class="footnote-ref" id="fnref:17" href="#fn:17">17</a> and the characters 1000 in the prefix identify the registrant; in this case the registrant is the International DOI Foundation itself. 182 is the suffix, or item ID, identifying a single object (in this case, the latest version of the DOI Handbook).
DOI names can identify creative works (such as texts, images, audio or video items, and software) in both electronic and physical forms, <a href="/facts/Performance/LoPW1hxp">performances</a>, and abstract works<a class="footnote-ref" id="fnref:18" href="#fn:18">18</a> such as licenses, parties to a transaction, etc.
The names can refer to objects at varying levels of detail: thus DOI names can identify a journal, an individual issue of a journal, an individual article in the journal, or a single table in that article. The choice of level of detail is left to the assigner, but in the DOI system it must be declared as part of the metadata that is associated with a DOI name, using a <a href="/facts/Data_dictionary/GyQLYd7j">data dictionary</a> based on the <a href="/facts/Indecs_Content_Model/G9BsAJ6g">indecs Content Model</a>.

<h3>Display</h3>
The official DOI Handbook explicitly states that DOIs should be displayed on screens and in print in the format doi:10.1000/182.<a class="footnote-ref" id="fnref:19" href="#fn:19">19</a>
Contrary to the DOI Handbook, <a href="/facts/Crossref/htqCmrbm">Crossref</a>, a major DOI registration agency, recommends displaying a URL (for example, https://doi.org/10.1000/182) instead of the officially specified format.<a class="footnote-ref" id="fnref:20" href="#fn:20">20</a><a class="footnote-ref" id="fnref:21" href="#fn:21">21</a> This URL is persistent (there is a contract that ensures persistence in the doi.org domain,) so it is a <a href="/facts/PURL/KKYhANhT">PURL</a>—providing the location of an <a href="/facts/Name_server/pUgmBMNW">name resolver</a> which will redirect <a href="/facts/HTTP_request/TWtvf7JD">HTTP requests</a> to the correct online location of the linked item.<a class="footnote-ref" id="fnref:22" href="#fn:22">22</a><a class="footnote-ref" id="fnref:23" href="#fn:23">23</a>
The Crossref recommendation is primarily based on the assumption that the DOI is being displayed without being hyperlinked to its appropriate URL—the argument being that without the hyperlink it is not as easy to copy-and-paste the full URL to actually bring up the page for the DOI, thus the entire URL should be displayed, allowing people viewing the page containing the DOI to copy-and-paste the URL, by hand, into a new window/tab in their <a href="/facts/Web_browser/2pfyymLs">browser</a> in order to go to the appropriate page for the document the DOI represents.<a class="footnote-ref" id="fnref:24" href="#fn:24">24</a>

<h2 id="content">Content</h2>
Major content of the DOI system currently includes:

<ul><li><a href="/facts/Scientific_literature/nJh0Bx22">Scholarly materials</a> (journal articles, books, ebooks, etc.) through <a href="/facts/Crossref/htqCmrbm">Crossref</a>, a consortium of around 3,000 publishers; <a href="/facts/Airiti/nF5xhCMy">Airiti</a>, a leading provider of Chinese and Taiwanese electronic academic journals; and the Japan Link Center (JaLC)<a class="footnote-ref" id="fnref:25" href="#fn:25">25</a> an organization providing link management and DOI assignment for electronic academic journals in Japanese.</li>
<li>Research datasets through <a href="/facts/DataCite/XbtpfYPu">DataCite</a>, a consortium of leading research libraries, technical information providers, and scientific data centers;</li>
<li><a href="/facts/European_Union/6GYcR8qM">European Union</a> official publications through the <a href="/facts/Publications_Office_(European_Union)/npUTPWCq">EU publications office</a>;</li>
<li>The <a href="/facts/CNKI/CbQ2q0ak">Chinese National Knowledge Infrastructure</a> project at <a href="/facts/Tsinghua_University/HNwjrEuU">Tsinghua University</a> and the Institute of Scientific and Technical Information of China (ISTIC), two initiatives sponsored by the Chinese government.</li>
<li>Permanent global identifiers for both commercial and non-commercial audio/visual content titles, edits, and manifestations through the Entertainment ID Registry, commonly known as <a href="/facts/EIDR/RuhlcKBD">EIDR</a>.</li></ul>
In the <a href="/facts/Organisation_for_Economic_Co-operation_and_Development/CI9W2zGv">Organisation for Economic Co-operation and Development</a>'s publication service <a href="/facts/OECD_iLibrary/cgaQmKUF">OECD iLibrary</a>, each table or graph in an OECD publication is shown with a DOI name that leads to an Excel file of data underlying the tables and graphs. Further development of such services is planned.<a class="footnote-ref" id="fnref:26" href="#fn:26">26</a>
Other registries include <a href="/facts/Crossref/htqCmrbm">Crossref</a> and the multilingual European DOI Registration Agency (mEDRA).<a class="footnote-ref" id="fnref:27" href="#fn:27">27</a> Since 2015, <a href="/facts/Request_for_Comments/esftTvE7">RFCs</a> can be referenced as doi:10.17487/rfc....<a class="footnote-ref" id="fnref:28" href="#fn:28">28</a>

<h2 id="features-and-benefits">Features and benefits</h2>
The IDF designed the DOI system to provide a form of <a href="/facts/Persistent_identifier/hsPK2mkQ">persistent identification</a>, in which each DOI name permanently and unambiguously identifies the object to which it is associated (although when the publisher of a journal changes, sometimes all the DOIs will be changed, with the old DOIs no longer working). It also associates <a href="/facts/Metadata/qt35z79C">metadata</a> with objects, allowing it to provide users with relevant pieces of information about the objects and their relationships. Included as part of this metadata are network actions that allow DOI names to be resolved to web locations where the objects they describe can be found. To achieve its goals, the DOI system combines the <a href="/facts/Handle_System/rdebSxmC">Handle System</a> and the <a href="/facts/Indecs_Content_Model/G9BsAJ6g">indecs Content Model</a> with a social infrastructure.
The Handle System ensures that the DOI name for an object is not based on any changeable attributes of the object such as its physical location or ownership, that the attributes of the object are encoded in its metadata rather than in its DOI name, and that no two objects are assigned the same DOI name. Because DOI names are short character strings, they are human-readable, may be copied and pasted as text, and fit into the <a href="/facts/Uniform_Resource_Identifier/UjyqxTpA">URI</a> specification. The DOI name-resolution mechanism acts behind the scenes, so that users communicate with it in the same way as with any other web service; it is built on <a href="/facts/Open_architecture/mou6VjUD">open architectures</a>, incorporates <a href="/facts/Computational_trust/8uqLdMRR">trust mechanisms</a>, and is engineered to operate reliably and flexibly so that it can be adapted to changing demands and new applications of the DOI system.<a class="footnote-ref" id="fnref:29" href="#fn:29">29</a> DOI name-resolution may be used with <a href="/facts/OpenURL/A3jvEf5a">OpenURL</a> to select the most appropriate among multiple locations for a given object, according to the location of the user making the request.<a class="footnote-ref" id="fnref:30" href="#fn:30">30</a> However, despite this ability, the DOI system has drawn criticism from librarians for directing users to non-free copies of documents, that would have been available for no additional fee from alternative locations.<a class="footnote-ref" id="fnref:31" href="#fn:31">31</a>
The <a href="/facts/Indecs_Content_Model/G9BsAJ6g">indecs Content Model</a> as used within the DOI system associates metadata with objects. A small kernel of common metadata is shared by all DOI names and can be optionally extended with other relevant data, which may be public or restricted. Registrants may update the metadata for their DOI names at any time, such as when publication information changes or when an object moves to a different URL.
The International DOI Foundation (IDF) oversees the integration of these technologies and operation of the system through a technical and social infrastructure. The social infrastructure of a federation of independent registration agencies offering DOI services was modelled on existing successful federated deployments of identifiers such as <a href="/facts/GS1/MNX4N5ut">GS1</a> and <a href="/facts/ISBN/15AdSPa9">ISBN</a>.

<h2 id="comparison-with-other-identifier-schemes">Comparison with other identifier schemes</h2>
A DOI name differs from commonly used Internet pointers to material, such as the <a href="/facts/Uniform_Resource_Locator/pPD5g7Wq">Uniform Resource Locator</a> (URL), in that it identifies an object itself as a <a href="/facts/First_class_(computing)/eTNn5oNe">first-class entity</a>, rather than the specific place where the object is located at a certain time. It implements the <a href="/facts/Uniform_Resource_Identifier/UjyqxTpA">Uniform Resource Identifier</a> (<a href="/facts/Uniform_Resource_Name/DCaGkLLY">Uniform Resource Name</a>) concept and adds to it a data model and social infrastructure.<a class="footnote-ref" id="fnref:32" href="#fn:32">32</a>
A DOI name also differs from standard identifier registries such as the <a href="/facts/ISBN/15AdSPa9">ISBN</a>, <a href="/facts/International_Standard_Recording_Code/24XgqCwd">ISRC</a>, etc. The purpose of an identifier registry is to manage a given collection of identifiers, whereas the primary purpose of the DOI system is to make a collection of identifiers actionable and interoperable, where that collection can include identifiers from many other controlled collections.<a class="footnote-ref" id="fnref:33" href="#fn:33">33</a>
The DOI system offers persistent, <a href="/facts/Semantic_interoperability/nNy54nb8">semantically interoperable</a> resolution to related current data and is best suited to material that will be used in services outside the direct control of the issuing assigner (e.g., public citation or managing content of value). It uses a managed registry (providing both social and technical infrastructure). It does not assume any specific business model for the provision of identifiers or services and enables other existing services to link to it in defined ways. Several approaches for making identifiers persistent have been proposed.
The comparison of persistent identifier approaches is difficult because they are not all doing the same thing. Imprecisely referring to a set of schemes as "identifiers" does not mean that they can be compared easily. Other "identifier systems" may be enabling technologies with low barriers to entry, providing an easy to use labeling mechanism that allows anyone to set up a new instance (examples include <a href="/facts/Persistent_Uniform_Resource_Locator/KKYhANhT">Persistent Uniform Resource Locator</a> (PURL), URLs, <a href="/facts/Globally_Unique_Identifier/SUtkYJPe">Globally Unique Identifiers</a> (GUIDs), etc.), but may lack some of the functionality of a registry-controlled scheme and will usually lack accompanying metadata in a controlled scheme.
The DOI system does not have this approach and should not be compared directly to such identifier schemes. Various applications using such enabling technologies with added features have been devised that meet some of the features offered by the DOI system for specific sectors (e.g., <a href="/facts/Archival_Resource_Key/KAk6MVuI">ARK</a>).
A DOI name does not depend on the object's location and, in this way, is similar to a <a href="/facts/Uniform_Resource_Name/DCaGkLLY">Uniform Resource Name</a> (URN) or PURL but differs from an ordinary URL. URLs are often used as substitute identifiers for documents on the Internet although the same document at two different locations has two URLs. By contrast, persistent identifiers such as DOI names identify objects as first class entities: two instances of the same object would have the same DOI name.

<h2 id="resolution">Resolution</h2>
To resolve a DOI name, it may be input to a DOI resolver, such as one at the official website https://doi.org/.
DOI name resolution is provided through the <a href="/facts/Handle_System/rdebSxmC">Handle System</a>, which is an infrastructure developed and operated by CNRI (<a href="/facts/Corporation_for_National_Research_Initiatives/qCnfTKpK">Corporation for National Research Initiatives</a>), and is freely available to any user encountering a DOI name. Resolution redirects the user from a DOI name to one or more pieces of typed data: URLs representing instances of the object, services such as e-mail, or one or more items of metadata. To the Handle System, a DOI name is a handle, and so has a set of values assigned to it and may be thought of as a record that consists of a group of fields. Each handle value must have a data type specified in its <type> field, which defines the syntax and semantics of its data. While a DOI persistently and uniquely identifies the object to which it is assigned, DOI resolution may not be persistent, due to technical and administrative issues.
Another approach, which avoids typing or <a href="/facts/Copying_and_pasting/eksLoJ9M">copying and pasting</a> into a resolver is to include the DOI in a document as a URL which uses the resolver as an HTTP proxy, such as https://doi.org/ (preferred)<a class="footnote-ref" id="fnref:34" href="#fn:34">34</a> or http://dx.doi.org/, both of which support HTTPS. For example, the DOI 10.1000/182 can be included in a reference or <a href="/facts/Hyperlink/LqNsa84e">hyperlink</a> as <a href="https://doi.org/10.1000/182">https://doi.org/10.1000/182</a>. This approach allows users to click on the DOI as a normal <a href="/facts/Hyperlink/LqNsa84e">hyperlink</a>. Indeed, as previously mentioned, this is how Crossref recommends that DOIs always be represented (preferring HTTPS over HTTP), so that if they are cut-and-pasted into other documents, emails, etc., they will be actionable.
An interesting consequence of the fact that DOIs depend entirely on CNRI’s Handle System infrastructure (whereby CNRI operates the global root servers and wrote the protocol) is that the proxy services DOI.org/<#> and hdl.handle.net/<#> are interoperable. For example, the following URIs resolve to the same publication:
https://doi.org/10.1016/S0021-9258(19)52451-6
https://hdl.handle.net/10.1016/S0021-9258(19)52451-6
There are other DOI resolvers and HTTP Proxies apart from NCRI's <a href="/facts/Handle_System/rdebSxmC">Handle System</a>. At the beginning of the year 2016, a new class of alternative DOI resolvers was started by http://doai.io/ (now discontinued <a class="footnote-ref" id="fnref:35" href="#fn:35">35</a>). This service was unusual in that it tried to find a <a href="/facts/Paywall/42qFQy1U">non-paywalled</a> (often <a href="/facts/Self-archiving/yPp2AAea">author archived</a>) version of a title and redirected the user to that instead of the <a href="/facts/Publisher%2527s_version/DCTgoks0">publisher's version</a>.<a class="footnote-ref" id="fnref:36" href="#fn:36">36</a> Since then, other open-access favoring DOI resolvers have been created, notably https://oadoi.org/ in October 2016<a class="footnote-ref" id="fnref:37" href="#fn:37">37</a> (rebranded in 2017 as https://unpaywall.org/). While traditional DOI resolvers solely rely on the Handle System, alternative DOI resolvers first consult multiple Open Access resources such as institutional libraries with the <a href="/facts/Open_Archives_Initiative_Protocol_for_Metadata_Harvesting/Qphlv5Dp">Open Archives Initiative Protocol for Metadata Harvesting</a> (OAI-PMH), or indexing services based in OAI-PMH, such as <a href="/facts/BASE_(search_engine)/JjMNJLvg">BASE</a> (Bielefeld Academic Search Engine).<a class="footnote-ref" id="fnref:38" href="#fn:38">38</a><a class="footnote-ref" id="fnref:39" href="#fn:39">39</a>
An alternative to HTTP proxies is to use one of a number of add-ons and plug-ins for <a href="/facts/Web_browser/2pfyymLs">browsers</a>, thereby avoiding the conversion of the DOIs to URLs,<a class="footnote-ref" id="fnref:40" href="#fn:40">40</a> which depend on domain names and may be subject to change, while still allowing the DOI to be treated as a normal hyperlink. A disadvantage of this approach for publishers is that, at least at present, most users will be encountering the DOIs in a browser, <a href="/facts/Mail_reader/pQdW9HtC">mail reader</a>, or other software which does not have one of these plug-ins installed.

<h2 id="idf-organizational-structure">IDF organizational structure</h2>

The International DOI Foundation (IDF), a non-profit organization created in 1997, is the governance body of the DOI system.<a class="footnote-ref" id="fnref:41" href="#fn:41">41</a> It safeguards all <a href="/facts/Intellectual_property/PqHW9mVP">intellectual property rights</a> relating to the DOI system, manages common operational features, and supports the development and promotion of the DOI system. The IDF ensures that any improvements made to the DOI system (including creation, maintenance, registration, resolution and policymaking of DOI names) are available to any DOI registrant. It also prevents third parties from imposing additional licensing requirements beyond those of the IDF on users of the DOI system.
The IDF is controlled by a Board elected by the members of the Foundation, with an appointed Managing Agent who is responsible for co-ordinating and planning its activities. Membership is open to all organizations with an interest in electronic publishing and related enabling technologies. The IDF holds annual open meetings on the topics of DOI and related issues.
Registration agencies, appointed by the IDF, provide services to DOI registrants: they allocate DOI prefixes, register DOI names, and provide the necessary infrastructure to allow registrants to declare and maintain metadata and state data. Registration agencies are also expected to actively promote the widespread adoption of the DOI system, to cooperate with the IDF in the development of the DOI system as a whole, and to provide services on behalf of their specific user community. A list of current RAs is maintained by the International DOI Foundation. The IDF is recognized as one of the federated registrars for the Handle System by the DONA Foundation (of which the IDF is a board member), and is responsible for assigning Handle System prefixes under the top-level 10 prefix.<a class="footnote-ref" id="fnref:42" href="#fn:42">42</a>
Registration agencies generally charge a fee to assign a new DOI name; parts of these fees are used to support the IDF. The DOI system overall, through the IDF, operates on a <a href="/facts/Not-for-profit/AmXu2c85">not-for-profit</a> cost recovery basis.

<h2 id="standardization">Standardization</h2>
The DOI system is an international standard developed by the <a href="/facts/International_Organization_for_Standardization/IacYR7Yg">International Organization for Standardization</a> in its technical committee on identification and description, TC46/SC9.<a class="footnote-ref" id="fnref:43" href="#fn:43">43</a> The Draft International Standard ISO/DIS 26324, Information and documentation – Digital Object Identifier System met the ISO requirements for approval. The relevant ISO Working Group later submitted an edited version to ISO for distribution as an FDIS (Final Draft International Standard) ballot,<a class="footnote-ref" id="fnref:44" href="#fn:44">44</a> which was approved by 100% of those voting in a ballot closing on 15 November 2010.<a class="footnote-ref" id="fnref:45" href="#fn:45">45</a> The final standard was published on 23 April 2012.<a class="footnote-ref" id="fnref:46" href="#fn:46">46</a>
DOI is a registered URI under the <a href="/facts/Info_URI_scheme/3Q8n4xnh">info URI scheme</a> specified by IETF RFC 4452.<a class="footnote-ref" id="fnref:47" href="#fn:47">47</a> info:doi/ is the infoURI Namespace of Digital Object Identifiers.<a class="footnote-ref" id="fnref:48" href="#fn:48">48</a>
The DOI syntax is a <a href="/facts/NISO/NdLoBTF1">NISO</a> standard, first standardized in 2000, ANSI/NISO Z39.84-2005 Syntax for the Digital Object Identifier.<a class="footnote-ref" id="fnref:49" href="#fn:49">49</a>
The maintainers of the DOI system have registered a DOI namespace for <a href="/facts/URN/DCaGkLLY">URNs</a>.<a class="footnote-ref" id="fnref:50" href="#fn:50">50</a>

<h2 id="see-also">See also</h2>

<ul><li><a href="/facts/ArXiv/H6EtgnBe">arXiv</a></li>
<li><a href="/facts/Bibcode/9HtdQSGB">Bibcode</a></li>
<li><a href="/facts/DataCite/XbtpfYPu">DataCite</a></li>
<li><a href="/facts/Digital_identity/HWIe84hG">Digital identity</a></li>
<li><a href="/facts/Metadata_standard/gHWYjdtB">Metadata standard</a></li>
<li><a href="/facts/Object_identifier/wEC9ubWd">Object identifier</a></li>
<li><a href="/facts/ORCID/Xe65WNUb">ORCID</a></li>
<li><a href="/facts/PMID/JlHAvMHt">PMID</a></li>
<li><a href="/facts/Publisher_Item_Identifier/lIAMekYo">Publisher Item Identifier</a> (PII)</li>
<li><a href="/facts/Permalink/Icpw95Qq">Permalink</a></li>
<li><a href="/facts/Scientific_literature/nJh0Bx22">Scientific literature</a></li>
<li><a href="/facts/Universally_unique_identifier/SUtkYJPe">Universally unique identifier</a> (UUID)</li></ul>
<h2 id="notes">Notes</h2>

<h2 id="external-links">External links</h2>

<a href="/facts/Wikidata/5Myy74K5">Wikidata</a> has the property: 
<ul><li> DOI (P356) (see <a href="https://query.wikidata.org/embed.html#SELECT%20%3FWikidata_item_%20%3FWikidata_item_Label%20%3Fvalue%20%3FvalueLabel%20%3FEnglish_Wikipedia_article%20%23Show%20data%20in%20this%20order%0A%7B%0A%09%3FWikidata_item_%20wdt%3AP356%20%3Fvalue%20.%20%23Collecting%20all%20items%20which%20have%20P356%20data%2C%20from%20whole%20Wikidata%20item%20pages%0A%09OPTIONAL%20%7B%3FEnglish_Wikipedia_article%20schema%3Aabout%20%3FWikidata_item_%3B%20schema%3AisPartOf%20%3Chttps%3A%2F%2Fen.wikipedia.org%2F%3E%20.%7D%20%23If%20collected%20item%20has%20link%20to%20English%20Wikipedia%2C%20show%20that%0A%09SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%22%20%20%7D%20%23Show%20label%20in%20this%20language.%20%22en%22%20is%20English.%20%20%20%0A%7D%0ALIMIT%201000">uses</a>)</li></ul>

<ul><li><a href="https://www.doi.org/">Official website</a></li>
<li><a href="https://www.doi.org/the-identifier/resources/">DOI Resources</a> from DOI.org, including Factsheets, FAQs, and more</li>
<li><a href="https://shortdoi.org/">shortDOI Service</a> — A shortening service offered by the <a href="/facts/DOI_Foundation/muM9Etpq">DOI Foundation</a> that creates aliases for existing DOI® names of the form 10/abcde</li>
<li><a href="https://search.crossref.org/">Crossref Metadata Search</a> from CrossRef.org</li>
<li><a href="https://apps.crossref.org/SimpleTextQuery/">Crossref Simple Text Query</a> from CrossRef.org</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">"ISO 26324:2012(en), Information and documentation – Digital object identifier system". ISO. Archived from the original on 17 June 2016. Retrieved 20 April 2016. <a href="https://www.iso.org/obp/ui/#iso:std:iso:26324:ed-1:v1:en" target="_blank">https://www.iso.org/obp/ui/#iso:std:iso:26324:ed-1:v1:en</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">"The Handle System". Handle.Net Registry. Archived from the original on 7 January 2023. <a href="https://handle.net/" target="_blank">https://handle.net/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">"Resources (including Factsheets)". DOI. Archived from the original on 25 December 2022. <a href="https://www.doi.org/the-identifier/resources/" target="_blank">https://www.doi.org/the-identifier/resources/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">Witten, Ian H.; Bainbridge, David & Nichols, David M. (2010). How to Build a Digital Library (2nd ed.). Morgan Kaufmann. pp. 352–253. ISBN 978-0-12-374857-7. <a href="978-0-12-374857-7" target="_blank">978-0-12-374857-7</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">Langston, Marc; Tyler, James (2004). "Linking to Journal Articles in an Online Teaching Environment: The Persistent Link, DOI, and OpenURL". The Internet and Higher Education. 7 (1): 51–58. doi:10.1016/j.iheduc.2003.11.004. <a href="/wiki/Doi_(identifier)" target="_blank">/wiki/Doi_(identifier)</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">"How the "Digital Object Identifier" Works". BusinessWeek. 23 July 2001. Archived from the original on 2 October 2010. Retrieved 20 April 2010. Assuming the publishers do their job of maintaining the databases, these centralized references, unlike current web links, should never become outdated or broken <a href="https://web.archive.org/web/20101002070758/http://www.businessweek.com/magazine/content/01_30/b3742032.htm" target="_blank">https://web.archive.org/web/20101002070758/http://www.businessweek.com/magazine/content/01_30/b3742032.htm</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">Liu, Jia (2021). "Digital Object Identifier (DOI) Under the Context of Research Data Librarianship". Journal of eScience Librarianship. 10 (2): Article e1180. doi:10.7191/jeslib.2021.1180. <a href="https://doi.org/10.7191%2Fjeslib.2021.1180" target="_blank">https://doi.org/10.7191%2Fjeslib.2021.1180</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">Paskin, Norman (2010), "Digital Object Identifier (DOI) System", Encyclopedia of Library and Information Sciences (3rd ed.), Taylor and Francis, pp. 1586–1592 <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">Davidson, Lloyd A.; Douglas, Kimberly (December 1998). "Digital Object Identifiers: Promise and problems for scholarly publishing". Journal of Electronic Publishing. 4 (2). doi:10.3998/3336451.0004.203. <a href="https://doi.org/10.3998%2F3336451.0004.203" target="_blank">https://doi.org/10.3998%2F3336451.0004.203</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">"Welcome to the DOI System". DOI. 28 June 2010. Archived from the original on 13 August 2010. Retrieved 7 August 2010. <a href="https://doi.org/" target="_blank">https://doi.org/</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">"What is a DOI?". DOI Foundation. Retrieved 6 February 2025. <a href="https://www.doi.org/the-identifier/what-is-a-doi/" target="_blank">https://www.doi.org/the-identifier/what-is-a-doi/</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">"Who are the Members & Users?". DOI. Retrieved 6 February 2025. "DOI News, April 2011: 1. DOI System exceeds 50 million assigned identifiers". DOI. 20 April 2011. Archived from the original on 27 July 2011. Retrieved 3 July 2011. <a href="https://www.doi.org/the-community/who-are-the-members-and-users" target="_blank">https://www.doi.org/the-community/who-are-the-members-and-users</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">"Important Alerts". DOI. <a href="https://www.doi.org/more-info" target="_blank">https://www.doi.org/more-info</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">"doi info & guidelines". CrossRef.org. Publishers International Linking Association, Inc. 2013. Archived from the original on 21 October 2002. Retrieved 10 June 2016. All DOI prefixes begin with "10" to distinguish the DOI from other implementations of the Handle System followed by a four-digit number or string (the prefix can be longer if necessary). <a href="https://web.archive.org/web/20021021021703/http://www.crossref.org/01company/15doi_info.html" target="_blank">https://web.archive.org/web/20021021021703/http://www.crossref.org/01company/15doi_info.html</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">"Factsheet—Key Facts on Digital Object Identifier System". International DOI Foundation. 6 June 2016. Archived from the original on 5 June 2016. Retrieved 1 November 2024. Over 18,000 DOI name prefixes within the DOI System <a href="https://www.doi.org/the-identifier/resources/factsheets/key-facts-on-digital-object-identifier-system" target="_blank">https://www.doi.org/the-identifier/resources/factsheets/key-facts-on-digital-object-identifier-system</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">"DOI Handbook—2 Numbering". International DOI Foundation. 1 February 2016. Archived from the original on 30 June 2014. Retrieved 10 June 2016. The registrant code may be further divided into sub-elements for administrative convenience if desired. Each sub-element of the registrant code shall be preceded by a full stop. <a href="https://web.archive.org/web/20140630181440/http://www.doi.org/doi_handbook/2_Numbering.html#2.2.2" target="_blank">https://web.archive.org/web/20140630181440/http://www.doi.org/doi_handbook/2_Numbering.html#2.2.2</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">Other registries are identified by other strings at the start of the prefix. <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">"Frequently asked questions about the DOI system: 6. What can a DOI name be assigned to?". DOI Foundation. 3 July 2018. Archived from the original on 16 February 2023. Retrieved 19 July 2018. <a href="https://www.doi.org/the-identifier/resources/faqs#8-what-can-a-doi-name-be-assigned-to" target="_blank">https://www.doi.org/the-identifier/resources/faqs#8-what-can-a-doi-name-be-assigned-to</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">"DOI Handbook – Numbering". doi.org. 13 February 2014. Section 2.6.1 Screen and print presentation. Archived from the original on 30 June 2014. Retrieved 30 June 2014. <a href="https://doi.org/doi_handbook/2_Numbering.html#2.6.1" target="_blank">https://doi.org/doi_handbook/2_Numbering.html#2.6.1</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">"DOI Display Guidelines". Archived from the original on 24 November 2016. Retrieved 19 October 2016. <a href="http://www.crossref.org/02publishers/doi_display_guidelines.html" target="_blank">http://www.crossref.org/02publishers/doi_display_guidelines.html</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">"New Crossref DOI display guidelines are on the way". Archived from the original on 19 October 2016. Retrieved 19 October 2016. <a href="http://blog.crossref.org/2016/09/new-crossref-doi-display-guidelines.html" target="_blank">http://blog.crossref.org/2016/09/new-crossref-doi-display-guidelines.html</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">Davidson, Lloyd A.; Douglas, Kimberly (December 1998). "Digital Object Identifiers: Promise and problems for scholarly publishing". Journal of Electronic Publishing. 4 (2). doi:10.3998/3336451.0004.203. <a href="https://doi.org/10.3998%2F3336451.0004.203" target="_blank">https://doi.org/10.3998%2F3336451.0004.203</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
<li id="fn:23">Powell, Andy (June 1998). "Resolving DOI Based URNs Using Squid: An Experimental System at UKOLN". D-Lib Magazine. doi:10.1045/june98-powell. ISSN 1082-9873. Archived from the original on 13 June 2010. Retrieved 23 April 2010. <a href="http://www.dlib.org/dlib/june98/06powell.html" target="_blank">http://www.dlib.org/dlib/june98/06powell.html</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></li>
<li id="fn:24">ChrissieCW. "Crossref Revises DOI Display Guidelines - Crossref". crossref.org. Archived from the original on 25 April 2018. Retrieved 25 April 2018. <a href="https://www.crossref.org/news/2011-08-02-crossref-revises-doi-display-guidelines/" target="_blank">https://www.crossref.org/news/2011-08-02-crossref-revises-doi-display-guidelines/</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></li>
<li id="fn:25">"Japan Link Center(JaLC)". japanlinkcenter.org. Archived from the original on 29 September 2020. Retrieved 6 August 2022. <a href="https://japanlinkcenter.org/top/english.html" target="_blank">https://japanlinkcenter.org/top/english.html</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></li>
<li id="fn:26">Green, T. (2009). "We Need Publishing Standards for Datasets and Data Tables". Research Information. doi:10.1787/603233448430. <a href="https://doi.org/10.1787%2F603233448430" target="_blank">https://doi.org/10.1787%2F603233448430</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></li>
<li id="fn:27">"multilingual European DOI Registration Agency". mEDRA.org. 2003. Archived from the original on 1 February 2018. Retrieved 2 February 2018. <a href="https://www.medra.org/" target="_blank">https://www.medra.org/</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></li>
<li id="fn:28">J. Levine (October 2015). Assigning Digital Object Identifiers to RFCs. Internet Architecture Board. doi:10.17487/RFC7669. RFC 7669. Informational. sec. 3.
 <a href="/wiki/John_R._Levine" target="_blank">/wiki/John_R._Levine</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></li>
<li id="fn:29">Timmer, John (6 March 2010). "DOIs and their discontents". Ars Technica. Archived from the original on 8 March 2013. Retrieved 5 March 2013. <a href="https://arstechnica.com/science/2010/03/dois-and-their-discontents-1/" target="_blank">https://arstechnica.com/science/2010/03/dois-and-their-discontents-1/</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></li>
<li id="fn:30">DeRisi, Susanne; Kennison, Rebecca; and Twyman, Nick (2003). "Editorial: The what and whys of DOIs". PLoS Biology. 1 (2): e57. doi:10.1371/journal.pbio.0000057. PMC 261894. PMID 14624257.
 <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC261894" target="_blank">https://www.ncbi.nlm.nih.gov/pmc/articles/PMC261894</a> <a href="#fnref:30" class="footnote-back-ref">↩</a></li>
<li id="fn:31">Franklin, Jack (2003). "Open access to scientific and technical information: the state of the art". In Grüttemeier, Herbert; Mahon, Barry (eds.). Open access to scientific and technical information: state of the art and future trends. IOS Press. p. 74. ISBN 978-1-58603-377-4. Archived from the original on 7 August 2022. Retrieved 7 August 2022. <a href="978-1-58603-377-4" target="_blank">978-1-58603-377-4</a> <a href="#fnref:31" class="footnote-back-ref">↩</a></li>
<li id="fn:32">"DOI System and Internet Identifier Specifications". doi.org. 18 May 2010. Archived from the original on 26 June 2010. Retrieved 7 August 2010. <a href="https://doi.org/factsheets/DOIIdentifierSpecs.html" target="_blank">https://doi.org/factsheets/DOIIdentifierSpecs.html</a> <a href="#fnref:32" class="footnote-back-ref">↩</a></li>
<li id="fn:33">"DOI System and standard identifier registries". doi.org. Archived from the original on 26 June 2010. Retrieved 7 August 2010. <a href="https://doi.org/factsheets/DOIIdentifiers.html" target="_blank">https://doi.org/factsheets/DOIIdentifiers.html</a> <a href="#fnref:33" class="footnote-back-ref">↩</a></li>
<li id="fn:34">International DOI Foundation (7 August 2014). "Resolution". DOI Handbook. Archived from the original on 31 March 2015. Retrieved 19 March 2015. <a href="https://doi.org/doi_handbook/3_Resolution.html#3.7.3" target="_blank">https://doi.org/doi_handbook/3_Resolution.html#3.7.3</a> <a href="#fnref:34" class="footnote-back-ref">↩</a></li>
<li id="fn:35">"DOAI". CAPSH (Committee for the Accessibility of Publications in Sciences and Humanities). Archived from the original on 25 August 2016. Retrieved 6 August 2016. <a href="https://web.archive.org/web/20160825222550/http://doai.io/" target="_blank">https://web.archive.org/web/20160825222550/http://doai.io/</a> <a href="#fnref:35" class="footnote-back-ref">↩</a></li>
<li id="fn:36">Schonfeld, Roger C. (3 March 2016). "Co-opting 'Official' Channels through Infrastructures for Openness". The Scholarly Kitchen. Archived from the original on 19 October 2016. Retrieved 17 October 2016. <a href="https://scholarlykitchen.sspnet.org/2016/03/03/coopting-official-channels/" target="_blank">https://scholarlykitchen.sspnet.org/2016/03/03/coopting-official-channels/</a> <a href="#fnref:36" class="footnote-back-ref">↩</a></li>
<li id="fn:37">Piwowar, Heather (25 October 2016). "Introducing oaDOI: resolve a DOI straight to OA". Archived from the original on 17 March 2017. Retrieved 17 March 2017. <a href="http://blog.impactstory.org/introducting-oadoi/" target="_blank">http://blog.impactstory.org/introducting-oadoi/</a> <a href="#fnref:37" class="footnote-back-ref">↩</a></li>
<li id="fn:38">"DOAI". CAPSH (Committee for the Accessibility of Publications in Sciences and Humanities). Archived from the original on 25 August 2016. Retrieved 6 August 2016. <a href="https://web.archive.org/web/20160825222550/http://doai.io/" target="_blank">https://web.archive.org/web/20160825222550/http://doai.io/</a> <a href="#fnref:38" class="footnote-back-ref">↩</a></li>
<li id="fn:39">Piwowar, Heather (25 October 2016). "Introducing oaDOI: resolve a DOI straight to OA". Archived from the original on 17 March 2017. Retrieved 17 March 2017. <a href="http://blog.impactstory.org/introducting-oadoi/" target="_blank">http://blog.impactstory.org/introducting-oadoi/</a> <a href="#fnref:39" class="footnote-back-ref">↩</a></li>
<li id="fn:40">"DOI System Tools". Archived from the original on 8 February 2017. Retrieved 7 February 2017. <a href="https://www.doi.org/tools.html" target="_blank">https://www.doi.org/tools.html</a> <a href="#fnref:40" class="footnote-back-ref">↩</a></li>
<li id="fn:41">"Chapter 7: The International DOI Foundation". DOI Handbook. doi.org. Archived from the original on 10 July 2015. Retrieved 8 July 2015. <a href="https://web.archive.org/web/20150710112821/http://www.doi.org/doi_handbook/7_IDF.html#7.5" target="_blank">https://web.archive.org/web/20150710112821/http://www.doi.org/doi_handbook/7_IDF.html#7.5</a> <a href="#fnref:41" class="footnote-back-ref">↩</a></li>
<li id="fn:42">"Multi-Primary Administrators". DONA Foundation. Archived from the original on 14 January 2017. Retrieved 7 February 2017. <a href="https://web.archive.org/web/20170114120514/https://dona.net/mpa/" target="_blank">https://web.archive.org/web/20170114120514/https://dona.net/mpa/</a> <a href="#fnref:42" class="footnote-back-ref">↩</a></li>
<li id="fn:43">"Digital object identifier (DOI) becomes an ISO standard". International Organization for Standardization. 10 May 2012. Archived from the original on 2 August 2012. Retrieved 10 May 2012. <a href="https://archive.today/20120802195534/http://www.iso.org/iso/news.htm?refid=Ref1561" target="_blank">https://archive.today/20120802195534/http://www.iso.org/iso/news.htm?refid=Ref1561</a> <a href="#fnref:43" class="footnote-back-ref">↩</a></li>
<li id="fn:44">"Standards and Specifications". Overviews & Standards. doi.org. 28 June 2010. Archived from the original on 26 June 2010. Retrieved 7 August 2010. <a href="https://web.archive.org/web/20100626071933/http://www.doi.org/about_the_doi.html#TC46" target="_blank">https://web.archive.org/web/20100626071933/http://www.doi.org/about_the_doi.html#TC46</a> <a href="#fnref:44" class="footnote-back-ref">↩</a></li>
<li id="fn:45">"Standards and Specifications: 1. ISO TC46/SC9 Standards". Overviews & Standards. doi.org. 18 November 2010. Archived from the original on 4 July 2011. Retrieved 3 July 2011. <a href="https://web.archive.org/web/20110704112317/http://www.doi.org/about_the_doi.html#TC46" target="_blank">https://web.archive.org/web/20110704112317/http://www.doi.org/about_the_doi.html#TC46</a> <a href="#fnref:45" class="footnote-back-ref">↩</a></li>
<li id="fn:46">"ISO 26324:2012(en), Information and documentation – Digital object identifier system". ISO. Archived from the original on 17 June 2016. Retrieved 20 April 2016. <a href="https://www.iso.org/obp/ui/#iso:std:iso:26324:ed-1:v1:en" target="_blank">https://www.iso.org/obp/ui/#iso:std:iso:26324:ed-1:v1:en</a> <a href="#fnref:46" class="footnote-back-ref">↩</a></li>
<li id="fn:47">RFC 4452 <a href="/wiki/RFC_(identifier)" target="_blank">/wiki/RFC_(identifier)</a> <a href="#fnref:47" class="footnote-back-ref">↩</a></li>
<li id="fn:48">"About "info" URIs – Frequently Asked Questions". Info-uri.info. Archived from the original on 27 September 2010. Retrieved 7 August 2010. <a href="http://info-uri.info/registry/docs/misc/faq.html#which_namespaces" target="_blank">http://info-uri.info/registry/docs/misc/faq.html#which_namespaces</a> <a href="#fnref:48" class="footnote-back-ref">↩</a></li>
<li id="fn:49">"ANSI/NISO Z39.84-2005 Syntax for the Digital Object Identifier" (PDF). National Information Standards Organization. Archived (PDF) from the original on 25 June 2021. Retrieved 25 June 2021. <a href="https://groups.niso.org/apps/group_public/download.php/14689/z39-84-2005_r2010.pdf" target="_blank">https://groups.niso.org/apps/group_public/download.php/14689/z39-84-2005_r2010.pdf</a> <a href="#fnref:49" class="footnote-back-ref">↩</a></li>
<li id="fn:50">"Namespace Registration for Digital Object Identifier (DOI)". IANA. <a href="https://www.iana.org/assignments/urn-formal/doi" target="_blank">https://www.iana.org/assignments/urn-formal/doi</a> <a href="#fnref:50" class="footnote-back-ref">↩</a></li>
</ol>

Digital object identifier open-in-new

Digital object identifier