comprehensive policies supporting community-agreed practices

Providing data services e.g. portal and machine interfaces, data download or server-side processing.

A TRUSTworthy repository needs to focus on serving its target user community. Each user community likely has differing expectations from their community repositories, depending in part on the community’s maturity regarding data management and sharing. A TRUSTworthy repository is embedded in its target user community’s data practices, and so can respond to evolving community requirements

TRUSTworthy repositories take responsibility for the stewardship of their data holdings and for serving their user community.

Terms of use, both for the repository and for the data holdings.

The adoption of technological capabilities should be completed in conjunction with the organizational, managerial and stewardship capabilities that facilitate the continuing use of a data repository’s holdings

Adhering to the designated community’s metadata and curation standards, along with providing stewardship of the data holdings e.g. technical validation, documentation, quality control, authenticity protection, and long-term persistence.

A repository depends on the interaction of people, processes, and technologies to support secure, persistent, and reliable services. Its activities and functions are supported by software, hardware, and technical services.

Implementing relevant and appropriate standards, tools, and technologies for data management and curation

Implementing relevant data metrics and making these available to users.

Having plans and mechanisms in place to prevent, detect, and respond to cyber or physical security threats

Providing (or contributing to) community catalogues to facilitate data discovery.

To fulfill this role, TDRs must demonstrate essential and enduring capabilities necessary to enable access and reuse of data over time for the communities they serve

10.5281/zenodo.4084762

As oil becomes more expensive to extract, less and less energy will be available.

Efficient - process management includes deliberate process optimization/improvement.

Capable - the process is quantitatively managed in accordance with agreed-upon metrics.

Defined - the process is defined/confirmed as a standard business process

Repeatable - the process is at least documented sufficiently such that repeating the same steps may be attempted.

Initial (chaotic, ad hoc, individual heroics) - the starting point for use of a new or undocumented repeat process.

ISO 24619:2011 specifies requirements for the persistent identifier (PID) framework and for using PIDs for referencing and citing documents, files and language resources (e.g digital dictionaries, text corpora, linguistic annotated corpora). A PID is an electronic identification referring to or citing electronic documents, files, resources, resource collections such as books, articles, papers, images etc. ISO 24619:2011 also addresses issues of persistence and granularity of references to resources, first by requiring that persistent references be implemented by using a PID framework and further by imposing requirements on any PID frameworks used for this purpose.

All Systems Operational

The Anatomy of References

We cannot guarantee persistence of identifiers, because we do not generate and maintain the data

DataCite

Managing the intellectual property rights of data producers

and the security of the system and its content

Ensuring sustainability of a TRUSTworthy repository is necessary to ensure uninterrupted access to its valuable data holdings for current and future user communities. Continued access to data is dependent upon the ability of the repository to provide services over time, and to respond with new or improved services to meet evolving user community requirements.

Planning sufficiently for risk mitigation, business continuity, disaster recovery, and succession.

Continued access to data is dependent upon the ability of the repository to provide services over time, and to respond with new or improved services to meet evolving user community requirements

Managing the intellectual property rights of data producers, the protection of sensitive information resources, and the security of the system and its content.

repositories should ensure that, at a minimum, the mission statement and scope of the repository are clearly stated

free open-source software to load and write chemical structures

It was created in 2001

4,463,574

2,400,000

The International Standard Language Resource Number (ISLRN) is a new, unique and universal identification schema for Language Resources which provides Language Resources with unique names using a standardized nomenclature. It also ensures Language Resources are identified, and consequently recognized with proper references in activities within Human Language Technologies, as well as in documents and scientific papers.

Green spectrum also penetrates deep into plants driving photosynthesis where other spectrum cannot.

The ORCID Researcher Advisory Council (ORAC) is a diverse group of researchers who provide valuable perspectives and advice to ORCID staff and the ORCID Board to ensure that ORCID provides value and utility to researchers and facilitates research and innovation.

Mr. Wittenburg started by thanking the Executive Director who had provided useful inputs relating to EOSCdiscussions in Western Europe. In Mr. Wittenburg's view the DO Architecture technology was now facingtwo main challenges: (i) building such infrastructure was taking more time than it had initially beenexpected; and (ii) building such infrastructure was still a highly dynamic issue as there were many differentsuggestions and positions among the players. For Mr. Wittenburg, a DONA strength was that it was an islandof stability in this dynamic environment

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

The artist looked at the producerThe producer sat backHe said, "What we have got here, is a perfect trackBut we don't have a vocalAnd we don't have a songIf we could get these things accomplishedNothing else could go wrong"So he balanced the ashtrayAs he picked up the phoneAnd said, "Send me a songwriterWho's drifted far from homeAnd make sure that he's hungryMake sure he's aloneSend me a cheeseburgerAnd a new Rolling Stone"

In a journal article or manuscript a sample identified by IGSN SSH000SUA may look like this (tagged IGSN): IGSN:SSH000SUA

Unlike many other persistent identifiers, an IGSN is used not only used by machines but also needs to be handled by humans.

DOIs have a business model. LSIDs currently do not. Without a business model (read funding) we should stick to something that doesn’t have the implementation/adoption impediment of LSIDs and make the best of it (i.e. just have a usage policy for HTTP URIs).

Without some kind of persistence mechanism the only advantage of LSIDs is that they look like they are supposed to be persistent. Unfortunately, because many people are using UUIDs as their object identifiers LSIDs actually look like something you wouldn’t want to look at let alone expose to a user! CoL actually hide them because they look like this: urn:lsid:catalogueoflife.org:taxon:d755ba3e-29c1-102b-9a4a-00304854f820:ac2009

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.

The preferred PID scheme In consideration of the foregoing, the strongest option across the studied major dimensions of the available Handle System PID schemes and operational modes is for DiSSCo to use DOIs to identify Digital Specimens. The case for choosing DOI comes out slightly more strongly than choosing ePIC for reasons related to the substantial achievements, operational experience and reputation of DOI/ IDF to date. Operating under another Handle-system prefix than those used by IDF and ePIC is the substantially weakest option because of the difficulties associated with introducing an identifier that is not perceived to be a DOI. The term ‘DOI’ is trademarked by the IDF and thus not available for describing other identifiers. The practical and sensible avenue to explore further are the options to establish and become an RA member of the DOI Foundation (option A5) and to enter a strategic alliance at the level of the DOI Foundation (option A1). These options are likely most effective when actioned in combination.

When digitized, each resulting ‘Digital Specimen’ must be persistently and unambiguously identified. Subsequent events or transactions associated with the Digital Specimen, such as annotation and/or modification by a scientist must be recorded, stored and also unambiguously identified.

Persistent identifiers (PID) to identify digital representations of physical specimens in natural science collections (i.e., digital specimens) unambiguously and uniquely on the Internet are one of the mechanisms for digitally transforming collections-based science.

Information quality is the strongest factor to influence organizational benefits through perceived usefulness and user satisfaction

Digital Specimen

Appropriate identifiers Requirement: PIDs appropriate to the digital object type being persistently identified.

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?

digital or physical objects, or concepts

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

Breaking of links is mostly due to administrative changes at the referencedInternet node

Over time the risk grows that the document is no longer accessible at the loca-tion given as reference. Web servers that follow the HTTP protocol then givethe notorious reply: ‘404 not found’. This resembles the situation of a book in a– very large – library that is not on the shelf at the position indicated in the cata-logue. How is it to be found?

In the mid 1990s, a number of schemes were developed that, rather than rely-ing on the precise address of a document, introduced the idea of name spaces forrecording the names and locations of documents.

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.

withdrawing content withoutposting a notification (“Tombstone Page”) andupdating the record's URL/metadata with DataCite

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.

Persistent identifiers (PIDs) are an abstraction layer that arbitrates between the reference of a digital object and its location.

Scalability – in the data/metadata stored;

ORCID was first announced in 2009

The developer and administrator of the DOI system is the International DOI Foundation (IDF), which introduced it in 2000

5.2. Key ? was(DESCRIPTION) when(DATE) resync This "metadata" command form provides nothing more than a way to carry a Key along with its description. The form is a "no-op" (except when "resync" is present) in the sense that the Key is treated as an adorned URL (as if no THUMP request were present). This form is designed as a passive data structrue that pairs a hyperlink with its metadata so that a formatted description might be surfaced by a client-side trigger event such as a "mouse-over". It is passive in the sense that selecting ("clicking on") the URL should result in ordinary access via the Key-as-pure-link as if no THUMP request were present. The form is effectively a metadata cache, and the DATE of last extraction tells how fresh it is. The "was" pseudo-command takes multiple arguments separated by "|", the first argument identifying the kind of DESCRIPTION that follows, e.g,

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.)

CLARIN: European Research Infrastructure for Language Resources and Technology CNIC: Computer Network Information Center, Chinese Academy of Sciences, China CSC: IT Center for Science CSCS: Swiss National Supercomputing Centre DKRZ: Deutsches Klimarechenzentrum GRNET: Greek Research and Technology Network GWDG: Gesellschaft für wissenschaftliche Datenverarbeitung Göttingen SND: Swedish National Data Center SURF: SURF is the collaborative ICT organization for higher education and research in the Netherlands

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.

check character (CC): A check character is incorporated in the assigned identifier to guard against common transcription errors.

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.

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

Datafiles can be published with a suitable embargo period, forinstance to allow completion of publications or research basedon the dataset, or to respect contracts made by the depositorwith third parties concerning intellectual property rights.DANS encourages embargo periods of 6 months or less.

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