implementing rosetta while integrating with a dam
DESCRIPTION
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 - PowerPoint PPT PresentationTRANSCRIPT
Implementing Rosettawhile integrating with a DAM
A little background…Digitization began in 2000No thought of preservationNow have 130 TB Adding 5 TB per monthDigitize for internal and external clients
Leading up to RosettaFiles somewhat organizedMoved to archival serversPolicies createdDPS softwares evaluated Rosetta recommended, end of 2012
Digitization CDM
Pre-Rosetta workflow
PrimoDigital Archive – folders/files
Project Client
Archival images
Coll. and m’data admin
Web display
NO LINK BETWEEN ARCHIVE AND CDMNo preservation m’data
Deriv. imagesTech. m’dataSome desc. m’data
Most desc. m’data
Clients’ Items
Initial implementation goals
1. Create semi-dark archive connected to DAM
a. Master files in Rosettab. Derivative files in DAM
2. Input descriptive metadata in DAM to be mirrored in Rosetta
3. Create new collections workflow 4. Create legacy collections workflow
How did scope creep start?Communication problemsSales reps vs developers/trainersWere we clear enough during needs assessmentLack of pre-implementation knowledge Digital Preservation and Digital Operations with different needsWhich metadata where? Why?Rosetta as DAM?Every item in both systems or no?
Revised goals1. Create Submission Information &
Metadata (SIMP) ingest tool • Ingest IEs into both Rosetta and DAM
2. Archival Resource Key (ARK) to keep items connected
3. Move descriptive metadata to SIMP, input only in DAM• Title, ARK only metadata in Rosetta
4. Focus on new collections workflow
Digitization
CDM
Rosetta Workflow 1
PrimoRosetta
Project Client
Archival images
ARKNo desc.
m’data
Coll. and m’data admin
Web displayDeriv. imagesARKTech. m’dataSome desc. m’data
SIP/ARK
ML App
ARK
• 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
Digital Operations*Metadata ServicesDigital Preservation SIMP Tool
https://simp.lib.utah.edu
Staging
Folders
Digitized Content
Workflow 1
Digital Operations*Metadata ServicesDigital Preservation
Derivatives
Gallery
PACKAGING1.Select Content
(IEs)
2.Specify Package Title
3.Copy from Staging» Extract
Technical Metadata
» Create Derivatives
4.Mint ARK
Staging
Folders
Digitized Content
SIMP Toolhttps://simp.lib.utah.edu
Workflow 1
Staging
Folders
Digital Operations*Metadata ServicesDigital Preservation
Digitized Content
SIMP Toolhttps://simp.lib.utah.edu
METADATA EDITING
5.Set Metadata Template
6.Edit Metadata» Spreadshe
et» Save Data
7.Approve
PACKAGING1.Select Content
(IEs)
2.Specify Package Title
3.Copy from Staging» Extract
Technical Metadata
» Create Derivatives
4.Mint ARK
Derivatives Gallery
Descriptive
Metadata
Workflow 1
Staging
Folders
Digital Operations*Metadata ServicesDigital Preservation
Digitized Content
SIMP Toolhttps://simp.lib.utah.edu
SEND TO ROSETTA
9.Send to Rosetta» Checksum
s» METS
Record» Copy to
Digarch (UIT)
METADATA EDITING
5.Set Metadata Template
6.Edit Metadata» Spreadshe
et» Save Data
7.Approve
PACKAGING1.Select Content
(IEs)
2.Specify Package Title
3.Copy from Staging» Extract
Technical Metadata
» Create Derivatives
4.Mint ARK
DOWNLOAD .TSV
8.Download Metadata
Derivatives Gallery
Descriptive
Metadata
Workflow 1
SIMP: Administration
SIMP: Browse Servers
SIMP: Navigate collections
SIMP: Create Packages
What’s in those packages?
Thumbnail images
SIMP: Send to Rosetta
Rosetta view
DAM view
Rosetta ingests so far…
Where are we now?Rolling out SIMP to Library depts for testingGauging preservation needs/size by deptCoordinating workflows to ingest legacy filesPlanning Rosetta expansion beyond Library
Our biggest obstaclesBuilding the SIMP tool to work with a DAM as well as Rosetta before going LiveChanging the ways & order items are ingested into DAMMaking sure Rosetta wasn’t forgotten due to DAM focusCoordination with Ex Libris implementation team
Scope creep: the bad
Lengthened implementation periodStrained communicationMuddied Rosetta implementation with DAM concerns
Scope creep: the good
Created a more robust ingest toolMultiple platforms servedLibrary divisions came together, more cohesive
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!
Questions?
Tawnya KellerDigital Preservation Archivist, J. Willard Marriott
801.581.8594