Difference between revisions of "Minimum Preservation Tool"
m |
|||
(6 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
− | + | {{Infobox tool | |
− | + | |image=MPT_horizontal_no_logo.png | |
− | {{ | + | |purpose=The Minimum Preservation Tool (MPT) can be used to create an interim preservation storage environment for files awaiting preservation in a longer term repository solution. It supports checksum generation, fixity checking, and replication across two or more storage nodes. |
− | |purpose=The Minimum Preservation Tool can be used to create an interim preservation storage environment for files awaiting preservation in a longer term repository solution. It supports checksum generation, fixity checking, and replication across two or more storage nodes. | ||
− | |||
|homepage=https://github.com/britishlibrary/mpt | |homepage=https://github.com/britishlibrary/mpt | ||
|license=http://www.apache.org/licenses/LICENSE-2.0 | |license=http://www.apache.org/licenses/LICENSE-2.0 | ||
− | | | + | |function=Fixity, Preservation System |
}} | }} | ||
− | + | {{Infobox tool details}} | |
+ | == Description == | ||
+ | The MPT was designed to make use of existing network storage and compute resources available at most institutions. It is intended to provide greater protection to digital content than a standard network storage offering. The key differences between an MPT solution and standard network storage are replication of content across two or more storage “nodes” and regular fixity checking (checksum validation) of all files on all nodes to help ensure content remains authentic and unchanged. | ||
+ | Papers & Posters: | ||
+ | Back to Basics: The Minimum Preservation Tool (iPRES2021) - short paper. Pennock, Maureen; Beaman, John; May, Peter; Davies, Kevin | ||
+ | https://zenodo.org/record/5788586#.YyN4Q3bMJhE | ||
− | + | Upscaling the MPT (iPRES2022)- poster. May, Peter; Davies, Kevin (forthcoming) | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== User Experiences == | == User Experiences == | ||
Line 27: | Line 20: | ||
== Development Activity == | == Development Activity == | ||
− | https://github.com/britishlibrary/mpt | + | https://github.com/britishlibrary/mpt - Main site |
+ | |||
+ | https://github.com/anjackson/mpt/releases/tag/v1.1.6-UI - Experimental MPT user interface from @anjacks0n | ||
+ | |||
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --> | <!-- 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. --> | <!-- Add the OpenHub.com ID for the tool, if known. --> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Latest revision as of 19:13, 15 September 2022
Description[edit]
The MPT was designed to make use of existing network storage and compute resources available at most institutions. It is intended to provide greater protection to digital content than a standard network storage offering. The key differences between an MPT solution and standard network storage are replication of content across two or more storage “nodes” and regular fixity checking (checksum validation) of all files on all nodes to help ensure content remains authentic and unchanged.
Papers & Posters: Back to Basics: The Minimum Preservation Tool (iPRES2021) - short paper. Pennock, Maureen; Beaman, John; May, Peter; Davies, Kevin https://zenodo.org/record/5788586#.YyN4Q3bMJhE
Upscaling the MPT (iPRES2022)- poster. May, Peter; Davies, Kevin (forthcoming)
User Experiences[edit]
Introduction to the MPT https://www.dpconline.org/blog/minimum-preservation-tool-mpt
Development Activity[edit]
https://github.com/britishlibrary/mpt - Main site
https://github.com/anjackson/mpt/releases/tag/v1.1.6-UI - Experimental MPT user interface from @anjacks0n