EZID Logo

Create Demo Identifier

Step 1: Choose an identifier type




Step 2: Describe the identified object

    Click for additional help
 

Clicking "Create" will create the identifier and make it public. To defer making it public, use the Advanced form.

Once created, an identifier cannot be renamed or deleted.

    Click for additional help

About Demo Identifiers

Demo identifiers, indicated on EZID screens by yellow highlighting, are temporary identifiers for use in testing the EZID service. They last for two weeks.

About custom remainders

Custom remainders (suffixes) should be unique and opaque. By opaque, it is meant that the alphanumeric string has no meaning. EZID strongly discourages placing brand strings in the remainder because successor organizations do not often honor previous brand and name assignments.

Because it is difficult to do this manually, it is recommended that EZID generate new identifiers in order to guarantee that they are unique and opaque.

Which citation profile should I use?

DataCite: the DataCite profile is required for DOIs. It is fully documented here: http://schema.datacite.org. EZID online help is also available.

Dublin Core: the Dublin Core profile is provided for interoperability. It is fully documented here: http://dublincore.org/documents/dces/

ERC (aka, Dublin Kernel): the Electronic Resource Citation (ERC) profile is the EZID UI default for ARKs. It is fully documented here: http://dublincore.org/groups/kernel/spec/ Metadata features developed for the ARK resolver are aimed at records stored with this format first.

Status

public: the identifier is viewable by anyone.

reserved: the identifier is known only to EZID. May be used to reserve an identifier name within EZID without advertising the identifier's existence to resolvers and other external services. May be deleted.

unavailable: The identifier is public, but only insofar as it redirects to an EZID-provided "tombstone" page, displaying the identifier's citation metadata and the reason for the object's unavailability.

Reason for Unavailability

The reason you supply will appear on the identifier's manage page, through the API, and on an EZID-provided "tombstone" page (an HTML page that displays the identifier's citation metadata and the reason for the object's unavailability) regardless of its target URL.

About co-ownership

Co-ownership is when one EZID user account designates another EZID user account as co-owner of the first account's identifiers. This gives the second EZID user account the right to manage and edit detailed information about an identifier.

Why is the edit button disabled?

This identifier is currently editable only through the EZID API.

Unable to enter a creator?

A creator value is required in the datacite profile. If one is unavailable, we recommend using one of the following standard machine-recognizable codes. Selecting the code from the list below will automatically insert it in the form for you.

Unable to enter a title?

A title value is required in the datacite profile. If one is unavailable, we recommend using one of the following standard machine-recognizable codes. Selecting the code from the list below will automatically insert it in the form for you.

Unable to enter a publisher?

A publisher value is required in the datacite profile. If one is unavailable, we recommend using one of the following standard machine-recognizable codes. Selecting the code from the list below will automatically insert it in the form for you.

Unable to enter a publication year?

A 4-digit publication year value is required in the datacite profile. If one is unavailable, we recommend using one of the following standard machine-recognizable codes. Selecting the code from the list below will automatically insert it in the form for you.

About harvesting/indexing

Your choice pertains to making the metadata available for harvesting and/or indexing. Choosing "Yes" does not guarantee that the metadata will be harvested or indexed, but if you choose "No," it removes the possibility. See the online Help for more information about harvesting and indexing.