Editing Data Vault

{{Infobox_tool
|purpose=A storage broker and front end for archiving research data that is no longer active but that does not have a need for open publication
|image=datavault.jpg
|homepage=http://datavaultplatform.org/
|license=MIT
|platforms=Java, MySQL, Tomcat
}}
<!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. -->

<!-- Add one or more categories to describe the function of the tool, such as:
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) -->
[[Category:Preservation System]][[Category:Backup]][[Category:Storage]]

<!-- Add relevant categories to describe the content type that the tool addresses, such as:
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. -->
[[Category:Research Data]]

== Description ==
<!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. -->

A second phased of Jisc funding resulted in a [http://libraryblogs.is.ed.ac.uk/jiscdatavault/demo/ working prototype] at the end of December 2015.
From the project website:
"Research Data is being generated at an ever-increasing rate.  This brings challenges in how to store, analyse, and care for the data.  Part of this problem is the long term stewardship of data and associated files that need a safe and secure home for the medium to long term.

This project, funded by the Jisc #DataSpring programme seeks to define and develop a Data Vault software system that will allow data creators to describe and store their data safely in one of the growing number of options for archival storage.  This may include cloud solutions, shared storage systems, or local infrastructure."

== User Experiences ==
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. -->

== Development Activity ==
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. -->
<!-- Add the OpenHub.com ID for the tool, if known. -->
{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}