Last week, members of the Data Vault project got together for the kickoff meeting. Â Hosted at the University of Manchester Library, we were able to discuss the project plan, milestones for the three month project, agreed terminology for parts of the system, and started to assign tasks to project members for the first month.
Being only three months long, the project is beingÂ run in three one-month chunks. These are defined as follows:
- Month 1: Define and Investigate:Â This phase will allow us to agree what the Data Vault should do, and how it does it, Â Specifically it will look at:
- What are the use cases for the Data Vault
- How do we describe the system (create overview diagrams)
- How should the data be packed (metadata + data) for long term archival storage
- Develop example workflows for how the Data Vault could be used in the research process
- Examine the capabilities of archival storage systems to ensure they can support the proposed Data Vault
- Month 2: Requirements and Design: This phase will create the requirements specification and initial design of the system:
- Define the requirements specification
- Use the requirement specification to design the Data Vault system
- Month 3: Develop a Proof of Concept: This phase will seek to develop a minimal proof of concept that demonstrates the concept of the Data Vault:
- Deliver a working proof of concept that can describe and archive some data, and then retrieve it
At the end of month three, we will prepare for the second Jisc Data Spring sandpit workshop where we will seek to extend the project to take the prototype and develop it into a full system.
All of this is being documented in the project plan, which is a â€˜living documentâ€™ that is constantly evolving as the project progresses. Â The plan is online as a Google Document:
Look out for further blog posts during the month as we undertake the definitions and investigations!
Originally posted on the Jisc Data Vault blog, April 7, 2015