Overview (Digital Object Identifier Server 1.0.5 API)

Core Packages
Package	Description
fr.cnes.doi.application	Data Object Identifier managing a coherent set of resources and services.
fr.cnes.doi.resource	Provides base resources
fr.cnes.doi.resource.admin	Provides resources for the AdminApplication.
fr.cnes.doi.resource.citation	Provides resources for cross cite application.
fr.cnes.doi.resource.mds	Provides resources for Meta Data Store application.
fr.cnes.doi.security	Provides classes to secure the server.
fr.cnes.doi.server	Provides classes to create the server and start it.
fr.cnes.doi.services	Provides classes to monitor the speed of `Meta Data Store application`.

Extension Packages
Package	Description
fr.cnes.doi.db	Provides interfaces to request external databases.
fr.cnes.doi.plugin	Provides classes to loads a plugin in the classpath.
fr.cnes.doi.plugin.impl.db	Provides concrete classes implementing the interfaces of the external databases.
fr.cnes.doi.plugin.impl.db.impl	Provides database access implementation using JDBC connector.
fr.cnes.doi.plugin.impl.db.service	Provides the database access that stores the DOI, project and tokens

Utility Packages
Package	Description
fr.cnes.doi.client	Provides classes to request external web services.
fr.cnes.doi.exception	All current Exceptions.
fr.cnes.doi.logging.api	Provides log Handler, Filter, Formatter and monitoring system for the API.
fr.cnes.doi.logging.business	Provides Handler for handle application logs.
fr.cnes.doi.logging.security	Provides a filter to log security event such as login to the administration page.
fr.cnes.doi.settings	Provides settings for the server.
fr.cnes.doi.utils	Provides utility class.
org.datacite.schema.kernel_4

Other Packages
Package	Description
fr.cnes.doi.db.model	Provides the data models for: `DOIProject` representing the project data model `DOIUser` representing the user data model
fr.cnes.doi.utils.spec
org.restlet.ext.httpclient4	Provides a Bridge to JSPNego library, which supports different kind of proxies.
org.restlet.ext.wadl	Provides classes to patch WADL feature from Restlet

A Digital Object Identifier or DOIs are in use mainly to identify academic, professional, and government information, such as journal articles, research reports and data sets, and official publications.
doi reason

The DOI for a document remains fixed over the lifetime of the document, whereas its location and other metadata may change. Referring to an online document by its DOI provides more stable linking than simply using its URL, because if its URL changes, the publisher only needs to update the metadata for the DOI to link to the new URL.

A DOI is a persistent identifier, represented by an alphanumeric string assigned to uniquely identify an object. It is tied to a metadata description of the object as well as to a digital location, such as a URL, where all the details about the object are accessible.
DOI model

A DOI name is divided into three parts, separated by the first two slashes ('/'):
DOI parts
A DOI aims to be "resolvable" by the proxy. This is achieved by binding the DOI to metadata about the object, such as a URL, indicating where the object can be found. Thus, by being actionable and interoperable, a DOI differs from identifiers such as ISBNs and ISRCs which aim only to uniquely identify their referents.

A DOI prefix always starts with '10.' and continues with a number (e.g. '10.1234' or '10.20865'). The DOI prefix is used as a namespace so that DOIs are globally unique without requiring global coordination for every new identifier. Prefixes in the handle system and therefore all DOIs prefixes are numbers without any semantic meaning. The prefix is a unique number attributed by DataCite for a given organization.

The suffix for a DOI can be (almost) any string. Each suffix must be unique within the organization and is defined by the following list of characters : A-Z a-z 0-9 - . _ : / +

This document provides the description of the DOI server. it aims is to provide a common service to an organization so that each project of this organization can manage its own DOI according to their own access rights. The access rights are defined by the DOI server whereas the real creation of a DOI is handled between the DOI server and the DataCite API by a unique login/password. Moreover, the DOI server guarantees an unique identifer in the whole organization at condition that the project guarantees an unique identifier in its own project.
architecture