1 / 28

Implementing Rosetta while integrating with a DAM

Implementing Rosetta while integrating with a DAM . A little background…. Digitization began in 2000 No thought of preservation Now have 130 TB Adding 5 TB per month Digitize for internal and external clients. Leading up to Rosetta. Files somewhat organized

kura
Download Presentation

Implementing Rosetta while integrating with a DAM

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. Implementing Rosettawhile integrating with a DAM

  2. A little background… • Digitization began in 2000 • No thought of preservation • Now have 130 TB • Adding 5 TB per month • Digitize for internal and external clients

  3. Leading up to Rosetta • Files somewhat organized • Moved to archival servers • Policies created • DPS softwares evaluated • Rosetta recommended, end of 2012

  4. Pre-Rosetta workflow Digitization Clients’ Items CDM Web display Deriv. images Tech. m’data Some desc. m’data Project Client Most desc. m’data Coll. and m’data admin NO LINK BETWEEN ARCHIVE AND CDM No preservation m’data Archival images Primo Digital Archive – folders/files

  5. Initial implementation goals • Create semi-dark archive connected to DAM • Master files in Rosetta • Derivative files in DAM • Input descriptive metadata in DAMto be mirrored in Rosetta • Create new collections workflow • Create legacy collections workflow

  6. How did scope creep start? • Communication problems • Sales reps vs developers/trainers • Were we clear enough during needs assessment • Lack of pre-implementation knowledge • Digital Preservation and Digital Operations with different needs • Which metadata where? Why? • Rosetta as DAM? • Every item in both systems or no?

  7. Revised goals • Create Submission Information & Metadata (SIMP) ingest tool • Ingest IEs into both Rosetta and DAM • Archival Resource Key (ARK) to keep items connected • Move descriptive metadata to SIMP, input only in DAM • Title, ARK only metadata in Rosetta • Focus on new collections workflow

  8. Rosetta Workflow 1 Digitization ML App Deriv. images ARK Tech. m’data Some desc. m’data CDM Web display Project Client Coll. and m’data admin SIP/ARK Archival images ARK No desc. m’data ARK Primo Rosetta • Dual ingestions – but data not replicated • CDM ingestion process remains as-is • ARK is new m’data field • ARK is THE link between Rosetta and CDM

  9. Workflow 1 Digital Operations* Metadata Services Digital Preservation SIMP Tool https://simp.lib.utah.edu Digitized Content Staging Folders

  10. Workflow 1 Digital Operations* Metadata Services Digital Preservation SIMP Tool https://simp.lib.utah.edu Digitized Content • PACKAGING • Select Content (IEs) • Specify Package Title • Copy from Staging • Extract Technical Metadata • Create Derivatives • Mint ARK Staging Folders Derivatives Gallery

  11. Workflow 1 Digital Operations* Metadata Services Digital Preservation SIMP Tool https://simp.lib.utah.edu Digitized Content • METADATA EDITING • Set Metadata Template • Edit Metadata • Spreadsheet • Save Data • Approve • PACKAGING • Select Content (IEs) • Specify Package Title • Copy from Staging • Extract Technical Metadata • Create Derivatives • Mint ARK Staging Folders Descriptive Metadata Derivatives Gallery

  12. Workflow 1 Digital Operations* Metadata Services Digital Preservation SIMP Tool https://simp.lib.utah.edu Digitized Content • METADATA EDITING • Set Metadata Template • Edit Metadata • Spreadsheet • Save Data • Approve • PACKAGING • Select Content (IEs) • Specify Package Title • Copy from Staging • Extract Technical Metadata • Create Derivatives • Mint ARK • SEND TO ROSETTA • Send to Rosetta • Checksums • METS Record • Copy to Digarch (UIT) Staging Folders • DOWNLOAD .TSV • Download Metadata Descriptive Metadata Derivatives Gallery

  13. SIMP: Administration

  14. SIMP: Browse Servers

  15. SIMP: Navigate collections

  16. SIMP: Create Packages

  17. What’s in those packages?

  18. Thumbnail images

  19. SIMP: Send to Rosetta

  20. Rosetta view

  21. DAM view

  22. Rosetta ingests so far…

  23. Where are we now? • Rolling out SIMP to Library depts for testing • Gauging preservation needs/size by dept • Coordinating workflows to ingest legacy files • Planning Rosetta expansion beyond Library

  24. Our biggest obstacles • Building the SIMP tool to work with a DAM as well as Rosetta before going Live • Changing the ways & order items are ingested into DAM • Making sure Rosetta wasn’t forgotten due to DAM focus • Coordination with Ex Libris implementation team

  25. Scope creep: the bad • Lengthened implementation period • Strained communication • Muddied Rosetta implementation with DAM concerns

  26. Scope creep: the good • Created a more robust ingest tool • Multiple platforms served • Library divisions came together, more cohesive

  27. What did I learn? • Communication is key! • No one cares about long-term preservation as much as you (it’s not their job to). • Internal education is important. • If a project gets too stressful, take a couple months off!

  28. Questions? Tawnya Keller Digital Preservation Archivist, J. Willard Marriott Library tawnya.keller@utah.edu 801.581.8594

More Related