Recommended for final products, published materials, and citation. Use for objects under good long-term management.
Recommended for projects requiring more flexibility, early or unpublished versions of material.
Recommended for final products, published materials, and citation. Use for objects under good long-term management. Cannot be deleted.
Recommended for projects requiring more flexibility, early or unpublished versions of material. Can be deleted.
EZID will create a unique string for you. If you choose to create a custom remainder, best practice is to not include information that is subject to change, which impairs persistence. Please check Custom Remainder Rules for permitted characters.
Required for DOIs. More here: http://schema.datacite.org
More here: http://dublincore.org/documents/dces/
Electronic Resource Citation, default for ARKs. More here: http://dublincore.org/groups/kernel/spec/
A public status means the identifier is viewable by anyone. The reserved status means it is viewable only by owners, so “reserved” is a great way to save a DOI or ARK for use later. Reserved IDs can be deleted.
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 choosing "No" removes the possibility.
About Proxy Users
An EZID user account may designate another EZID user account as a proxy user of the first account's identifiers. This gives the second EZID user account the right to manage and edit detailed information about an identifier.
No wildcards allowed (i.e. asterisks, question marks)
The current location (URL) of the identified object
ID Create Date
Date when identifier was created. Format: YYYYY-MM-DD
ID Update Date
Date when identifier was last updated. Format: YYYYY-MM-DD
A value indicating the visibility of the identifier and its referenced object
A value indicating that the metadata is or is not available for harvesting and/or indexing
A value indicating the presence of metadata
Enter coordinates of the polygon using either GeoJSON or Keyhole Markup Language (KML) formatted text. Each point is defined by a longitude‐latitude pair. The last point should be the same as the first point.