110 likes | 220 Vues
Since its inception in 2000, the Digital Repository Service (DRS) has evolved through various iterations, with DRS2 being introduced to modernize preservation practices at Harvard Library. This workshop on June 13, 2013, outlines the motivations for DRS2, which include updating aging infrastructure, improving metadata preservation, and enhancing access to diverse digital content such as images, audio, and documents. Key features include new data models, better support for modern formats, and lessons learned from project development, aiming to streamline digital preservation and manage evolving library needs.
E N D
DRS 2 Project (2008 – Present!) Andrea Goethals, Harvard Library Digital Preservation Management Workshop, MIT June 13, 2013
Digital Repository Service (DRS) • 2000 - • Preservation and access repository • Used by 50 Harvard units (most libraries, archives, museums) • Digitized & born-digital content (images, text, page-turned, audio, geospatial, web sites, document, email)
Why DRS 2? • Modernize aging infrastructure • Implement digital preservation best practices and standards • Preserve metadata better • Improve collection management • Support preservation planning & activities • Improve access to content & metadata • Support more formats & genres
Repository Evolution DRS2 development DRS2 in production DRS1 in production DRS1 enhancements 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014
Key DRS 2 Features • New data model, schemas, AIPs, content models • Support for modern audio formats, playlists • Enhanced deposit, ingest, delivery apps • New audio delivery, indexing, management interface, WordShack, back end services • Metadata migration
Challenges • Library reorganization! • New administration / new priorities • Split DRS team • Different reporting structure • Staff attrition • Projects competing for the same resources • Size of project
Lessons Learned • Deadlines vs. functionality • Decide what matters to you and what doesn’t • Be flexible especially where it doesn’t matter • Need clear roles & responsibilities • People need to be migrated too
Lessons Learned • Have to have support & champions in higher administration • If you don’t broadly report status people will make their own assumptions
Lessons Learned • It gets better – even big projects end • June 3, 2013: beta release • ~ Sept. 1: production release