An Introduction to EZID

Editor's Notes

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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
7. 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
8. Let’s take a look at the UI now. (SWITCH OVER TO UI)
9. Dublin Kernel (ERC)Dublin CoreDataCite Kernel (for DOIs)API--open to othersFuture enhancements to support tagging
10. 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.
11. 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.
12. 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
13. Try it outHow to get an accountorder formEZID is available for use by all members of the UC communityLibraries/archives/museumsORU/MRUsFaculty/staff
14. The other all-important question!What happens if you stop paying? You will still be able to have access for maintenance, just not creation.
15. One of the all-important questions: how does this fit with everything else I’m doing?
16. Reiterate the testing modelUC3EZID Website