Preservation working group 2013

From Dryad wiki
Revision as of 07:42, 26 February 2013 by Elenafeinstein (talk | contribs) (Kickoff meeting, 26 Feb 2013, 11:00am EST/16:00GMT)

Jump to: navigation, search

Working Group Charge

To develop a state-of-the-art preservation plan for Dryad, with an emphasis on recommendations that are immediately useful and feasible to implement.

Working Group Members


  • Jane Greenberg, professor, SILS/UNC-CH, director, MRC
  • Elena Feinstein, Dryad curator, SILS/UNC-CH & MRC


  • Alex Ball, Research Officer, UKOLN, University of Bath
  • Robin Dale, Director of Digital and Preservation Services, LYRASIS
  • Michael Day, Digital Curation Centre, UKOLN, University of Bath
  • Ruth Duerr, Principal Investigator/Project Manager, Data Management and Cyberinfrastructure Manager, Data Stewardship, National Snow & Ice Data Center
  • Cal Lee, Associate Professor, SILS/UNC-CH
  • Robin Rice, Data Librarian, EDINA and Data Library, University of Edinburgh
  • Ayoung Yoon, SILS doctoral student

Working Group Meetings

Kickoff meeting, 26 Feb 2013, 11:00am EST/16:00GMT

  • Connection information sent via email


  1. Introductions (brief)
  2. Overview of working group goals
    • Creation of Dryad policy statement on preservation (strategic, long term)
    • Plan for implementation (priorities, immediate actions and long term goals)
  3. Quick, preservation-related facts about Dryad
    • size of collection: more than 7000 files and growing every day, see Dryad homepage for current stats
    • daily ingest of new content
    • heterogeneous files types, some non-preferred for preservation (e.g., proprietary formats), see this text file for a snapshot of formats in Dryad on Feb 5 2013
    • backups and checksums (Ryan will describe)
    • currently no real preservation activities beyond the basics
    • in process of joining CLOCKSS
  4. Questions from the group
  5. Action item for group members
    • Send us one to three examples of model preservation policy documents from other organizations, that are relevant to Dryad
    • Send us one to three other resources, such as templates, best practices documents, or preferred format documentation