1 / 6

EZID long-term identifiers made easy

Understand the minimal micro-service philosophy, agnostic identifier schemes, metadata uniform interface, and implementation decisions for broad applicability in repository batch operations and individual one-offs. Learn about identifier scheme differences, technical characteristics, scope and policies, cost considerations, and community acceptance. Explore the guiding principles, end-user UI, ownership, access control, and policy enforcement in the EZID system for DataCite N2T resolution and metadata binding, ensuring high availability and replication.

makya
Télécharger la présentation

EZID long-term identifiers made easy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EZIDlong-term identifiers made easy Greg Janée University of California Curation CenterCalifornia Digital Library July 31, 2012

  2. Minimal Micro-service philosophy Agnostic Identifier schemes Metadata Uniform interface Identifier scheme is a choice Broad applicability Repository batch operationsand individual one-offs Publication time and earlierin workflows • How do identifier schemes differ? • Technical characteristics • – E.g., partial resolution • Implementation • – Local server vs. central service • Scope & policies • – Metadata, citation support • Cost • – Per-identifier, or not • Community acceptance • – E.g., LSIDs Guiding principles

  3. End-user UI, API • Ownership, access control • External service communication • Services (minting, reservation, tombstoning, metadata mapping) • Policy enforcement • Notification, reporting DataCite EZID N2T “name-to-thing” • Resolution (ARKs and others) • Metadata binding • Replicated; high-availability Architecture OCA

  4. Issue: is metadata required? • Yes • DOI standard, DataCite require citation metadata • No • EZID: not absolute requirement • Other use cases (e.g., dataset granules), extra burden • Sure is nice, though • Metadata reflects intention • Without it, must rely on identifier (hopefully opaque) and target URL (may be inscrutable or ambiguous)

  5. Issue: what does an identifier resolve to? • Something human-readable? • DataCite requires “landing page” • (What if there isn’t one?) • Something machine-readable? • RDF, OAI-ORE, ERC,… • If yes to both, selection mechanism? • CrossRef/DataCite: HTTP content negotiation • imperfect • ARK proposal: “inflections” (decorators) • http://resolver/identifier?

  6. For more information EZID http://n2t.net/ezid UC Curation Center http://www.cdlib/uc3 People Greg Janée <gjanee@ucop.edu> John Kunze <jak@ucop.edu>

More Related