Difference between revisions of "Minimum Preservation Tool"
Jump to navigation
Jump to search
Ania Molenda (talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | + | {{Infobox tool | |
| − | + | |image=[[File: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 (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. | ||
| − | |||
|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 Verification, Preservation System |
}} | }} | ||
| − | + | {{Infobox tool details}} | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Description == | == 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. | 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. | ||
| Line 33: | Line 20: | ||
<!-- 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. --> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 15:53, 22 April 2021
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.
User Experiences
Introduction to the MPT https://www.dpconline.org/blog/minimum-preservation-tool-mpt
Development Activity
https://github.com/britishlibrary/mpt - Main site
https://github.com/anjackson/mpt/releases/tag/v1.1.6-UI - Experimental MPT user interface from @anjacks0n