1. UC3 Services In-Depth: Data Curation for Practitioners 2012 Workshop

2. Deep dive Who is it for? Why use it? How much does it cost? What can it do? How do I use it? Next steps Q & A

3. Who is it for? Libraries/archives/museums ORU/MRUs Faculty/staff Centrally hosted by UC3/CDL Mediated through campus libraries

4. Why use it? Curation repository – Supporting long-term preservation and access – Publish, share, preserve, discover, (re-)use “Model free” – There are no prescriptive requirements for content genre, format, structure, or accompanying metadata

5. How much does it cost? UC affiliates pricing model and service agreement available soon – Charged for storage fees only, at $390 per TB – Pay as you go (1 year) – Pay once, store for a long time (10 years) Services will be available to non-UC contributors

6. Sample pricing scenarios Pay-as-you-go (1 year) < 100 GB= $39 < 500 GB= $195 < 1 TB= $390 < 5 TB= $1,950 Paid-up (10 years) < 100 GB= $290 < 500 GB= $1,450 < 1 TB= $2,900 < 5 TB= $14,500

7. Modes of use: dark archive

8. Modes of use: bright archive "The Vault is Open" by Patrick Gage Kelley, 10/18/2008 Available on Flickr http://www.flickr.com/photos/ patrickgage/2961930014/

9. Modes of use: bright archive Provide preservation and end user access Option to designate collection as open to the public or keep restricted to designated users Can provide public access to entire object in the collection (metadata + associated files) Or can provide public access to view metadata while restricting associated files

10. There’s an option for “guest” login

11. Select a collection to browse

12. Choosing one of the collections brings you to the list of objects

13. View key citation metadata, Download individual versions... or download all versions The permanent link is listed on the object landing page for each object

14. Click-through agreements Possible to add a usage agreement at the collection level Every time someone tries to download an object from the collection, they would first be presented with the terms of use Copies sent to CDL, content owner/depositor, and end user

15. For collections using DUAs, clicking on the “Download object” button or using the download URL leads to…

16. Terms of use Personal information

17. Once the required fields are filled in, click the Accept button…

18. And the download begins

19. Modes of use: preservation “back end” eScholarship UCSF Clinical & Translational Science Institute: XTF + Merritt (DataShare) UCB Information Services and Technology: Alfresco + Merritt (Research Hub) UCLA Library: Islandora + Merritt

21. Modes of use: distributed data grids DataONE “Enable new science and knowledge creation through universal access to data about life on earth and the environment that sustains it”

22. How do I use it? Contact us for an account: uc3@ucop.eduuc3@ucop.edu Agree to service terms and fee schedule (available soon) We’ll work with you to establish and configure collection(s), for depositing content: – Level of access (dark vs. bright archive) – User accounts and permissions to deposit and access the collection

23. Depositing content User interface METS feeder API manual deposits automated deposits (METS) automated deposits

24. Depositing content User interface METS feeder API manual deposits automated deposits (METS) automated deposits See User’s Guide and online help for more information http://merritt.cdlib.org/ http://merritt.cdlib.org/

25. Deposit content through the UI The submission package is always a single file: – For a single object: A single file (image, PDF, A/V, etc.). Supply metadata through the UI A container (zip, gzip, tar.gz), comprising file(s) for a single object. Supply metadata through the UI, or include as a metadata file A manifest, enumerating file(s) for a single object. Supply metadata through the UI, or reference metadata file in the manifest – For multiple objects: A manifest, enumerating files and metadata records for multiple objects A manifest, enumerating multiple containers A manifest, enumerating multiple manifests

27. Upload a file, container, or manifest

28. Optionally supply metadata for the file or container

29. Using manifests A “packing slip” for an object, providing URLs for all object’s file components An Excel macro is available for automagically generating manifests. See User’s Guide and online help for more information http://merritt.cdlib.org/http://merritt.cdlib.org/

30. Providing metadata for objects Optional; if you don’t supply it, we’ll derive it How to supply metadata: – Provide it through the UI – Include it as part of the manifest – Include it as a metadata file: Simple Dublin Core record: mrt-dc.xml ERC record: mrt-erc.txt

31. Deposit notification You will receive two email separate notifications – Initial notification that we have received your submission, and that it is queued for subsequent processing – Final notification that we have fully processed your submission

32. Future developments Improved download for large objects Moving some functionality to object level—public option, DUAs Updating objects with just the changed components Enhanced UI to open access content in Merritt (exploring use of XTF and Solr) Drag-and-drop submission similar to Flickr, Dropbox

33. For more information Merritt repository: http://merritt.cdlib.org/ Merritt overview and resources: http://www.cdlib.org/services/uc3/merritt/ https://confluence.ucop.edu/display/Curation/ Development plans Webinars Use cases and deployment profiles Cost modeling TRAC self-audit And more...

34. Contact us uc3@cdlib.org Service Managers Perry Willett 510/987-0078 Perry.Willett@ucop.edu Adrian Turner 714/289-1822 Adrian.Turner@ucop.edu