Uploaded on

EZID makes it simple for researchers and others to obtain and manage long-term identifiers for their digital content. The service can create and resolve identifiers, and it also allows entry and …

EZID makes it simple for researchers and others to obtain and manage long-term identifiers for their digital content. The service can create and resolve identifiers, and it also allows entry and maintenance of information about the identifier (metadata). This presentation was given as part of a webinar series.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • To understand what EZID can do, let’s first look at what needs it addresses.EZID helps researchers in a number of different scenarios. Let’s take a look at a few of them.
  • Researchers doing data-intensive research and writing. Want to refer to the dataset right now even though they haven't yet found a permanent "home" for the data. If they register the dataset now with EZID, and they will get a clickable reference that can be used in the paper. When the papers are published and the data is moved, the researcher simply updates the target URL, and the clickable reference will still work.
  • RESEARCH TEAMS, work ACROSS REGIONS OR COUNTRIES where a data is hosted REMOTELY. Let’s assume the database is stored on someone’s departmental web server, but the server is getting old, soon to be replaced. The team can use the EZID services to register an identifier now +circulate that clickable address to colleagues + the entire data federation. When the infrastructure is replaced, the team can use EZID again to update the location details so that references to the database continues to work perfectly.
  • Researchers who have published extensively and who want to be able to move around in their career, also may want to take their data with them.They can use EZID services to get identifiers for the work AND the datasets that go with it. With persistent identifiers, the references are never broken, because the researcher can keep the target URLs and other metadata up to date even as she moves.
  • As the NSF and other funders issue requirements for data management plans, scientists have to be able to answer basic questions like, How will you name and organize the data files? EZID provides a ready answer to this requirement.
  • So EZID is a tool for extending library services….by extending our historic collection-building activities to datasetsallowing us to preserve our institution’s research investments
  • A service to make and manage actionable idsIds for anything: digital, physical, living, abstractCan manage identifiers under different schemes:ARKs, DOIs, and more to comeUser and programming interfacesPartnering for replication
  • Let’s take a look at the UI now. (SWITCH OVER TO UI)
  • Dublin Kernel (ERC)Dublin CoreDataCite Kernel (for DOIs)API--open to othersFuture enhancements to support tagging
  • I think of ARKs as the flexible alternative…“suffix passthrough” featureAssume you have many objects stored in a file system, many levels.You can register the TARGET URL at the TOP LEVEL and the NOID server (ARK resolver) will PASS-THROUGH the remainder of the target to the other server for resolution. The HANDLE server (the DOI resolver) will not do this.
  • DOIs should be assigned to objects that are under good long-term management, and where there is an intention is to make the object persistently available.DOIs must be registered exclusively with metadata that is available to public view.Can DOIs and ARKs work together?Yes. For example, researchers may choose to use ARKs for unpublished materials associated with an object that has been registered with a DOI. These two identifier schemes can work well together, and EZID offers them both, along with policy support consistent across both schemes.
  • A tombstone page is a web page returned for a resource no longer found at its target location of record. The tombstone may provide “last known” metadata, including the original owner.Full DataCitw metadata scheme support is available via the EZID API
  • Try it outHow to get an accountorder formEZID is available for use by all members of the UC communityLibraries/archives/museumsORU/MRUsFaculty/staff
  • The other all-important question!What happens if you stop paying? You will still be able to have access for maintenance, just not creation.
  • One of the all-important questions: how does this fit with everything else I’m doing?
  • Reiterate the testing modelUC3EZID Website


  • 1. UC3 Summer Webinar Series
    An Introduction to EZID
    University of California Curation Center Team
    California Digital Library
    August, 2011
  • 2. About the webinar series…
    Some logistics…
    Participant phones on mute
    We’re monitoring chat
    We’ll post slides, Q&A, and web & voice recordings after each presentation
    Schedule available at http://www.cdlib.org/uc3/uc3webinars.html
    Teleconference +1 (866) 740-1260, access code 9879016#
  • 3. Today’s topic: EZID
    EZID: Extending library services
    A tool for researchers
    A close look at EZID
    Demo, Metadata, Choosing identifiers, Next steps
    Getting started
    Accounts, Cost model, Workflows, Help
  • 4. EZID: A tool for extending library services
    Meeting researchers’ needs
    Early in the research life cycle
    Working on a federated team
    Making a career move
    Meeting funder requirements
    ©All rights reserved by University of California, http://www.flickr.com/photos/universityofcalifornia/5098256828
  • 5. Early in the research life cycle
    Data-intensive research
    Writing up the results
    Where’s the data?
    What if I move it?
    With EZID: all your references, citations, links, etc. will be stable!
    by Dave Rogers http://www.flickr.com/photos/dave-rogers/2815036285/
  • 6. Working on a federated team
    Data-intensive research
    Regional research center
    Aging infrastructure
    Where’s the data?
    We have to move it!
    With EZID: all your references, citations, links, etc. will be stable!
    ©All rights reserved by University of California, http://www.flickr.com/photos/universityofcalifornia/5405812887
  • 7. Making a career move
    • Researcher(s) on the move
    Data-intensive research
    I know where my data is
    and I’m taking it with me!
    With EZID: all your references, citations, links, etc. will be stable!
    ©All rights reserved by University of California,
  • 8. Meeting funder requirements
    • Grantor requirements for data management plan
    Data-intensive research
    What do we put here?
    How do we track the data?
    With EZID: track your data from capture to publication and beyond.
    By David Mellis, http://www.flickr.com/photos/mellis/7675610/
  • 9. EZID: Meeting library needs
    • New kinds of scholarlyoutput
    • 10. Continued need to build collections
    With EZID: you can extend your historic activities & preserve your institution’s research investment.
    ©All rights reserved by University of California, http://www.flickr.com/photos/universityofcalifornia/5098256828
  • 11. Create a persistent identifier: DOI or ARK
    Add object location
    Add metadata
    Update object location
    Update object metadata
  • 12. http://n2t.net/ezid
  • 13. EZID and Metadata
  • 14. ARK vs DOI
    • both can work like regular hyperlinks.
    • 15. both can refer to a subset or portion of a resource.
    • 16. both become persistentwhen the target URL is maintained.
    Courtesy of the Anaheim Public Library
  • 17. ARK vs DOI
    • Flexible
    • 18. Case-sensitive
    • 19. Special features support granularity
    • 20. Can be deleted
    • 21. Inexpensive
  • 22. ARKvsDOI
    • Established brand in publishing
    • 23. Indexed by major A&I citation databases 
    • 24. DataCite policies apply
    • 25. Cannot be deleted
    • 26. More costly
  • Next steps for EZID
    Enhanced persistence support
    Automated link checking
    Tombstone pages
    Exposure for citations
    Thomson-Reuters (Web of Knowledge)
    Elsevier (Scopus)
    More metadata support
    full DataCite metadata scheme
    cross scheme mapping
    UI redesign
    Activity reporting
    Browse & search
  • 27. Getting started
    Try it! UI and API test options
    Contact Joan Starr, EZID Service Manager
  • 28. EZID Cost Model
    UC3:technical infrastructure, staff, monitoring, maintenance, enhancements, help, outreach, consultation, etc.
    UC clients: a small annual subscription fee entitling them to unlimited identifiers, either ARKs only or ARKs and DOIs.
  • 29. Campus-EZID Workflows
    Plan A: Library as service provider
    Consult, support, reach out.
    Use EZID Order Form.
    Pass along account requests.
    Plan B: Library as information hub
    Distribute information, pass along questions, etc.
    Plan C: You shape it…
    We’ll work with you to match your workflow!
  • 30. Where to find help
    Understanding identifiers
    Choosing the right identifier (ARK vs DOI? ARK and DOI?)
    EZID Service Guidelines
    EZID Handout/brochure
    October 2010 webinar & slides
    Contact Joan Starr at uc3@ucop.edu
  • 31. For (even) more information
    http://n2t.net/ezid/ http://www.cdlib.org/services/uc3/ezid/
    UC Curation Center
    UC3 webinar series
    Stephen Abrams David Loy
    Lisa Colvin Mark Reyes
    Patricia Cruse Abhishek Salve
    Scott Fisher Tracy Seneca
    Erik Hetzner Carly Strasser
    Greg Janée Joan Starr
    John Kunze Marisa Strong
    Margaret Low Perry Willett
  • 32. Questions?
    by Florian http://www.flickr.com/photos/fboyd/2897598148/