Difference between revisions of "PRONOM Signature Development Utility"
Ross-spencer (talk | contribs) (Initial page linking back to GitHub repo) |
|||
| Line 17: | Line 17: | ||
<!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --> | <!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --> | ||
Utility to enable the creation of DROID compatible signature files using PRONOM regular expression syntax. The tool outputs in an XML format compatible with DROID 4 upwards (including DROID 5 and 6). Three sequences can be combined to create a single file format signature. Signature files can be concatenated manually if more complex collections are required for testing. | Utility to enable the creation of DROID compatible signature files using PRONOM regular expression syntax. The tool outputs in an XML format compatible with DROID 4 upwards (including DROID 5 and 6). Three sequences can be combined to create a single file format signature. Signature files can be concatenated manually if more complex collections are required for testing. | ||
| + | |||
| + | Signature File 88 contains of 1427 different PUIDs. | ||
= Development Activity = | = Development Activity = | ||
Revision as of 08:07, 4 April 2017
Description
Utility to enable the creation of DROID compatible signature files using PRONOM regular expression syntax. The tool outputs in an XML format compatible with DROID 4 upwards (including DROID 5 and 6). Three sequences can be combined to create a single file format signature. Signature files can be concatenated manually if more complex collections are required for testing.
Signature File 88 contains of 1427 different PUIDs.
Development Activity
All development activity is visible on GitHub: https://github.com/exponential-decay/signature-development-utility/commits
Activity Feed
Below the last 5 commits: Failed to load RSS feed from https://github.com/exponential-decay/signature-development-utility/commits/master.atom: There was a problem during the HTTP request: 404 Not Found