Brief minutes from DPWG meeting June the 11th 2014
Bold Italic is minutes notes
Brief Minutes
- Welcome and presentation of the participants
- Your name and your institution or company
- Expectations for this meeting
Euan Cochrane University of Yale
Digital Preservation Manager
- Eric James University of Yale
- Developer
- Linda Newman University of Cincinnati
- Head of Digital Collections and Repositories
APTrust, Digital Preservation Network (DPN), tools, preservation events
- Head of Digital Collections and Repositories
- Carl Wilson OPF
Improving digital preservation tools
Chris Awre University of Hull
Head of Information Management
Has a repository (Hydra head).
Not yet started with long term preservation.
Anders Sparre Conrad The Royal Library, Copenhagen, Denmark (National Library and University library) (KBDK)
- Placed in the general IT infrastructure department.
- Project manager for the Hydra project at KBDK
- Claus Jensen, KBDK
- Digital preservation specialist and generalist in the department of Digital Preservation.
- Christen Hedegaard, KBDK
- Project manager in the department of Digital Preservation
- Chair for DPWG
- Discussion of focus/charter for this working group
- See Introduction and Charter for DPWG.
- Went through the introduction and Anders supplied with following questions raised on the Power Steering Meeting in April 2014:
- Does Hydra want to present itself as a preservation platform (Fedora and Islandora do)
- If yes, then what do we mean when talking about Digital Preservation?
- What's the best practice for integration of preservation tools for Hydra applications
- Is it possible to get synergy through a collaboration between Hydra and OPF
- Chris pointed out that we should not work on the same task as the working group "Hydra for archivist".
- We will need a clarification of the work area for the two Hydra work group
- An example of a preservation use case in a Hydra context.
- KBDK use case
- Claus briefly presented how KBDK have integrated Digital Preservation in their Hydra implementation as an introduction to the discussion of the following areas of interest in Digital Preservation.
- KBDK use case
- Examples of interest areas of digital preservation
- Policy and strategy
- LOC analyse
- There was a general interest in this area.
- Cost
- 4C
- This area is very interesting but also a very challenging area.
- Euan supplied with the following links to cost models that he had used with success
- 4C
- Technical Watch
- Format, tools...
- Preservation planning
- There was a discussion of the purpose of preservation planning.
- As stated by the Plato team the purpose is: "The mission of preservation planning is to ensure authentic future access for a specific set of objects and designated communities by defining the actions needed to preserve it."
- Carl noticed that it was not an easy tool to use. but it makes you think about your digital preservation material.
- There was some interest.
- Preservation tools (Characterisation, validation, normalization....)
- COPTR describes tools useful for long-term preservation and is a initiative of four preservation communities: DCC, DCE, NDSA and OPF.
- Even though COPTR describes more than 370 preservation tools and is a great imitative, Carl would like more structure to the wiki page.
- Great interest in this area.
- Metadata
- Of course there was a lengthy discussion about the use of metadata and how the various standards such as PREMIS is implemented on individual institution.
- University of Yale is also using PREMIS, but suggested to agree on a common way to use it.
- Carl suggested that we should define a best practice for the use of PREMIS although larger institutions will surely define their own best practices.
- Metadata is an area of interest for this group
- Packing format for storage
Not a major issue.
University of Yale plans to use Bagit.
- Digital preservation based on risk management
- Level of bit safety
- Level of confidentiality
- Level of functional/logical strategy (migration, emulation, technical)
- Everyone agreed that long-term digital preservation is a matter of risk management.
- How many copies, geographical distance and so on
- Also you have to consider the risk appetite of confidential data.
- What risk are you willing to take for them to be published.
- Desired level of confidentiality is often contrary to the desired level of bit safety. (Lots of copies: High level of bit safety, but the consequence is lower level of confidentiality)
- Also an area of interest.
- Retrival of preserved material (ressource and metadata)
- Not a major issue
- KBDK differentiate between full restore (ressource+metadata) and import (only ressource).
- Preservation monitoring
- Carl: Try to look at Scout which is a preservation watch system developed by the SCAPE project and can be used for monitoring your preserved content
- Other (please specify)
- It was suggested to take a closer look at standards for trusted digital repositories, such as TRAC (ISO standard) and Drambora.
- Examples of cooperation with preservation community
- Open Planets Foundation
- Digital Preservation Coalition
- NDIIP
- NDSA
- Other (Please specify)
- It was agreed to start with OPF
- Carl (OPF) suggested to create requirements for our preservation needs
OPF will then offer testing facility to ensure that the quality and performance of the Hydra implementation
- Yale has received a grant to do a requirement analysis for their digital preservation needs, due in august.
- Agree on focus area/charter for this working group
- Although there is a lot of areas of interest it was decided to focus on integrating preservation tools in the Hydra environment
- Integration could be wrapping of tools or other ways to help the Hydra community to make use of the preservation tools.
- OPF can help testing framework/infrastructure (corpora), for example with signature files
- To ensure that we don't integrate already integrated/wrapped tools we need a list of integrated tools.
- Action: Anders and Chris will ask for such a list in the next partner call.
- Carl and Anders: focus on practical implementation of one or a few tools
- All the other areas as discussed in the above are still of interest, but will not be the focus area for the next period.
- We agreed to exchange knowledge and experience using this wiki page.
- Although there is a lot of areas of interest it was decided to focus on integrating preservation tools in the Hydra environment
- Define and agree on tasks for 2014
- Who will do what at what time?
Next Partner call (Anders and Chris): Ask for a list of tools already integrated into the Hydra environment
Writing on the Hydra-tech/partner list will also be an oppotunity.
All the participants: Prioritized list of tools we get from OPF/others that we would like to be integrated/wrapped for use in the Hydra environment.
DPWG chair: Make sure that the interested partners in the DPWG gets informed of the above
Carl would like to test wrapped tools (one or two) with the OPF test framework
All the participants: Insert information about digital preservation requirements and “use cases” from the DPWG participants.
Chair of DPWG: Clarify the working area of the DPWG and the "Hydra for archivists" group
Yale offered to share part of their specification for discussion and maybe that would trigger some action?
- Meeting and communication for DPWG
- Face to face meeting (Hydra connect,... ?)
- We agreed to have the next DPWG meeting at the next Hydra connect meeting
- A short introduction to the DPWG at the Hydra connect meeting.
- Virtual meetings (Skype, ..)
- Yes if needed we'll set-up a Skype meeting
- Wiki
- We will use the wiki for knowledge exchange to the Hydra community
- Mailing list
- Use the tech list
- Regular reporting on monthly Hydra partner calls
- Face to face meeting (Hydra connect,... ?)
- Any other items
Yale would like partners for their future work with digital preservation (if they get grant for their digital preservation project)