DLSC Minutes 5/19/2009 Attending: Sue Davis (guest), Jody Combs, David Carpenter, Sue Erickson, Ronee Francis, Bill Hook, Julie Loder, Rick Stringer-Hye, Dale Poulter Regrets: Marshall Breeding, Suellen Stringer-Hye

1.-Change to meeting schedule

There being no objections, we will start meeting once a month rather than once a week. Jody will send out suggested Tuesdays for us to meet monthly at 11:00am. [Decision, based on email conversation: the standing meeting will be the last Tuesday of the month]

2.-Digital preservation research

The group will divide into teams to research four different options for digital preservation using a list of questions developed by the group as a guideline. The results of the research will be put into a spreadsheet (Google document). Additional information will be put into separate documents.

• Hathitrust (consortial model)
• MetaArchive (Consortial module using CLOCKSS)
• CLOCKSS (controlled local installation of LOCKSS)
• Rosetta (ExLibris' Digital Preservation system)
• OCLC's Digital Presevation System

The groups are:

• Hathitrust: Jody and Sue Davis
• MetaArchive and CLOCKSS: Bill, Julie, David, Ronee
• Rosetta: Rick, Marshall, Suellen
• OCLC: Sue Erickson, Dale

The group discussed the need to extend the conversation to the entire campus beyond the library after the initial research is completed--but that this will need to be coordinated with the broader library planning efforts.

List of Questions to be answered for each option (we will review this list for completeness):

• Name
• Short description
• Type (example distributed archive, cooperative, alliance, vendor)
• What protections are in place to ensure content survivability?
• Number of mirror sites
• When established?
• Quality criteria? (TRAC)
• Models? (OAIS)
• Independent party verification of services?
• Number of participating libraries?
• Number of supporting libraries?
• Number of participating publishers?
• Specific types of materials (datasets, administrative, published, etc.)?
• Can accept multiple formats?
• Is content modified on ingest or later?
• Are reports generated?
• Who has access and how?
• Other possible users on campus (collaborators)?
• Metadata format?
• How are preserved materials made publically accessible?
• Can things be removed and how?
• Cost measurement (some type of cost measurement here)
• URL
• Policy URL
• Is the system scalable?
• How is authentication handled?
• What hardware/os platform does it run on?
• What is the base for licensing costs (number of items, access points, storage space used, etc)?
• Does the system track the age of items?
• Does the system provide a way to migrate file types in batch?
• How is ingestion done –batch, open api, etc?
• How does it check for bit rot (end-to-end checksum or another method)
• How does the system test for age of the data for reporting processes?

Additional resources:

Library of Congress http://www.digitalpreservation.gov/partners/resources/tools/index.html ARL http://www.arl.org/news/pr/preservation-14may09.shtml Blue Ribbon Task Force http://brtf.sdsc.edu/biblio/BRTF_Interim_Report.pdf

3. -The first DiscoverLibrary Town Hall meeting will be Thursday at 2:00pm in the Electronic Classroom

The group discussed what will be open for discussion and what the desired outcome is.

Some of the questions for the attendees are:

• What obstacles remain to widespread adoption of DL?
• What are seen as the major bugs?
• What reported issues are local and which are ExLibris issues?
• What to do when the current two tab metaphor breaks down?
• How can we start a sustainable dialog concerning DL and possible changes?

The question was asked if changes to the interface and default settings will be considered. Jody indicated that anything can be discussed constructively during the session.

Once the Town hall meetings are over the DLSC will create a survey containing all of the suggestions. The top 4 to 6 items receiving votes will be addressed as priorities. The DLSC will respond to all issues mentioned during the sessions, not just to those voted as top priorities--but the top priorities will be addressed sooner.