Skip to Content

doi: relevant content on this site

A digital object identifier (DOI) is a character string used to uniquely identify an electronic document or other object. Metadata about the object is stored in association with the DOI name and this metadata may include a location, such as a URL, where the object can be found. The DOI for a document is permanent, whereas its location and other metadata may change. Referring to an online document by its DOI provides more stable linking than simply referring to it by its URL, because if its URL changes, the publisher need only update the metadata for the DOI to link to the new URL. However, unlike URLs, the DOI system is not open to all comers; only organizations that can meet the contractual obligations of the DOI system and that are willing to pay to become a member of the system can assign DOIs. The DOI system is implemented through a federation of registration agencies coordinated by the International DOI Foundation, which developed and controls the system. The DOI system has been developed and implemented in a range of publishing applications since 2000; by late 2009 approximately 43 million DOI names had been assigned by some 4,000 organizations. (Excerpt from Wikipedia article: DOI)

Note: This page displays most recently updated content first. You can use the RSS link (bottom left of this page) to receive alerts as content is added or updated.

Confidence, and the business of persistent identification

The persistent identification of resources is a foundational element of the JISC Information Environment. There are several schemes and technologies available to support this, with one of the most prominently used in the JISC IE being the Digital Object Identifier (DOI). Built on the Handle technology, the DOI, under the stewardship of the not-for-profit International DOI Foundation (IDF), adds the important element of collective commitment and management, based on straightforward business interests.

Consuming and producing linked data in a content management system

At this summer's Institutional Web Management Workshop in Sheffield (IWMW 2010), I demonstrated how it is becoming feasible for a content management system both to consume and to produce linked data resources.

Syndicate content

Dr. Radut