Figshare supports version control of all publicly available data. Any privately stored data can also be altered or deleted as you wish.

The act of minting an LSID indicates that you intend to try to make it permanent or at least never re-use it for another resource.

Governance

Persistence

Trust

Available Handle-based PID schemes

Scalability

Collectively the IDF and its RA members assume the long-term responsibility to maintain and sustain the DOI PID scheme for everyone.

Which identifiers are FAIR enough?

Compact identifiers are a longstanding informal convention in bioinformatics. To be used as globally unique, persistent, web-resolvable identifiers, they require a commonly agreed namespace registry with maintenance rules and clear governance; a set of redirection rules for converting namespace prefixes, provider codes and local identifiers to resolution URLs; and deployed production-quality resolvers with long-term sustainability.

Wittenburg, P., Hellström, M., Zwölf, C.-M., Abroshan, H., Asmi, A., Di Bernardo, G., Couvreur, D., Gaizer, T., Holub, P., Hooft, R., Häggström, I., Kohler, M., Koureas, D., Kuchinke, W., Milanesi, L., Padfield, J., Rosato, A., Staiger, C., van Uytvanck, D., & Weigel, T. (2017). Persistent identifiers: Consolidated assertions. Status of November, 2017. Zenodo. https://doi.org/10.5281/zenodo.1116189

Archives. The Member shall use best efforts to contract with a third-party archive or other content host (an "Archive") (a list of which can be found here) for such Archive to preserve the Member's Content and, in the event that the Member ceases to host the Member's Content, to make such Content available for persistent linking.

Maintaining and Updating Metadata.

Commitment to data persistence

Maintaining and Updating Metadata.

ePIC PID service, and an organisation, that provides a PID service and is not an ePIC member, can ask for a certification, that it provides its PID service along the lines of the ePIC rules and policies.

ePIC has rules and policies, how to provide PID services and how to ensure the reliability, that is necessary for the persistency of access to digital objects via ePIC PIDs.

Registered production PIDs will not be deleted. They are used as a kind of tombstone even if the underlying data is not available anymore.

Scalability – in the data/metadata stored;

To resolve a Compact ARK (ie, an ARK beginning "ark:") it must initially be promoted to a Mapping ARK so that it becomes actionable. On the web, this means finding a suitable web Resolver Service to prepend to the compact form of the identifier in order to convert it to a URL (cf [CURIE]). (This is more or less true for any type of identifier not already in URL form.)

When content underlying a DOI is updated, we recommend updating the DOI metadata and, for major changes, assigning a new DOI. For minor content changes, the same DOI may be used with updated metadata. A new DOI is not required. For major content changes, we recommend assigning a new DOI and linking the new DOI to the previous DOI with related identifiers.

To enable easy usability for both humans and machines, a DOI should resolve to a landing page that contains information about the DOI being resolved. It is the responsibility of the entity creating the DOI to provide such a landing page. The following are best practices for creating well-formed DOI landing pages.

there may be infrequent cases where it is not desirable for the item described by a DOI to be available publicly, such as in the case of research retraction. In these cases, it is best practice to still provide a "tombstone page", which is a special type of landing page describing the item that has been removed.

certification: If certified, acronym for certification organization or standard (e.g., TRAC, TDR, DSA) and year of certification.

succession: The plan for dealing with sudden loss of provider viability, including set-aside funding and length of time that operations would be able to support continued operation while a successor provider is found to keep references intact.

mission: One sentence mission statement of the organization.

business model: For profit (FP) or not for profit (NP).

name: Full name of the provider organization. identifier: Unique identifier for the organization.

inflection: a change to the ending of an object’s id string in order to obtain a reference to content related to the originally referenced content.

landing: content intended mostly for human consumption, such as an object description and links to primary information (e.g., an image file or a spreadsheet), to alternate versions and formats, and to related information; from “landing page”, this is intended to support a browsing experience of an abstract overall view of the object.

plunging: content intended as primary object information, often required or directly usable by software; from “below the landing page”, this is intended to support an immersive object experience that bypasses any browsing step.

introversioned: a kind of intraversioned content for which the version identifier (within the object identifier) is opaque, e.g., “http://doi.org/10.2345/678”, which happens to be version 4.

intraversioned: a version identifier is part of the id string, e.g., “http://doi.org/10.2345/67.V4”.

extraversioned: a version identifier is separate from the id string, so that the actionable id does not lead to specific version without human intervention, e.g., “http://doi.org/10.2345/67”, Version 4.

Precisely when such assignment will be triggered depends on policy that will differ across objects, collections, and providers.

waxing: change that is limited to appending content in a way that does not in itself disrupt or displace previously recorded content. Examples of waxing objects include live sensor-based data feeds, citation databases, and serial publications.

subinfinite: due to succession arrangements, the object is expected to be available beyond the provider organization’s lifetime.

lifetime: the object is expected to be available as long as the provider exists.

indefinite: the provider has no particular commitment to the object.

finite: availability is expected to end on or around a given date (e.g., limited support for software versions not marked “long term stable”) or trigger event (e.g., single-use link).

finite: availability is expected to end on or around a given date (e.g., limited support for software versions not marked “long term stable”) or trigger event (e.g., single-use link). indefinite: the provider has no particular commitment to the object. lifetime: the object is expected to be available as long as the provider exists. subinfinite: due to succession arrangements, the object is expected to be available beyond the provider organization’s lifetime.

We define content variance to be a description of the ways in which provider policy or practice anticipates how an object’s content will change over time. Approaches to content variance differ depending on the object, version, service, and provider.

molting: Previously recorded content may be entirely overwritten at any time with content that preserves thematic continuity. For example, an organization’s homepage may be completely reworked while continuing to be its homepage, and a weather or financial service page may reflect dramatic changes in conditions several times a day.

rising: Previously recorded content may be improved at any time, for example, with better metadata (datasets), new features (software), or new insights (pre- and post-prints). This encompasses any change under “fixing”

fixing: Previously recorded content may be corrected at any time, in addition to any change under “keeping”

keeping: Previously recorded content will not change, but character, compression, and markup encodings may change during a format migration, and high-priority security concerns will be acted upon (e.g., software virus decontamination, security patching).

frozen: The bit stream representing previously recorded content will not change

id string: the sequence of characters that is the identifier string itself, possibly modified by adding a well-known prefix (often starting with http://) in order to turn it into a URL. identifier: an association between an id string and a thing; e.g., an identifier “breaks” when the association breaks, but to act on an identifier requires its id string. actionable identifier: an identifier whose id string may be acted upon by widely available software systems such as web browsers; e.g., URLs are actionable identifiers.

At a minimum it implies a prediction about an archive’s commitment and capacity to provide some specific kind of long-term functionality

persistence is purely a matter of service

We propose a novel approach relying on persistent, timestamped, adapted queries to versioned and timestamped data sources

If a published dataset is improved by amendments to thedata files of the dataset, a major version increment iscreated with a record of changes. In cases where it isnecessary to disable access to earlier versions, these can bedeaccessioned

Once a DOI is registered in the DOI System server, or repository, it will be stored there virtually forever.

These findings provide strong indicators that scholarly contentproviders reply to DOI requests differently, depending on the request method,the originating network environment, and institutional subscription levels

DOIs are a great solution for the problem of URIs that change over time, but this approach does depend on journal publishers, repositories, libraries, and other major hosting organization to be responsible for maintaining current link information within the DOI records that they have created

identifiers will continue to resolve indefinitely.

All PID Registration Agencies must have highly redundant storage and hosting infrastructure in order to ensure that services are globally available 24-7

Persistent

Machine-Readable

Globally Unique Names

Systems such as DOI can thus support resolution mechanisms that are likely to be able to maintain the resolution of identifiers regardless of changes in technology or to one particular system.

Supported Schemes