Editing PRONOM Signature Development Utility

Jump to: navigation, search

Warning: You are not logged in.

Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 18: Line 18:
 
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 =
 
+
== Using its Output ==
+
 
+
=== DROID ===
+
 
+
The signature development utility output can be directly uploaded to DROID via its 'Install Signature File' mechanism. Be sure to then select the new file from 'Preferences'.
+
 
+
=== Siegfried ===
+
 
+
[http://coptr.digipres.org/Siegfried Siegfried] is a useful tool for testing because it can combine a new signature file from this utility with all the other signatures in the PRONOM corpus, plus its many others.
+
 
+
==== Instructions for Linux ====
+
 
+
We use a utility called Roy to extend signature files. This is installed alongside Siegfried.
+
 
+
To extend a signature file to include a custom signature file, we need to make sure that there is a 'custom' folder, where Roy can find it. We will need our signature to be on a path that looks as follows:
+
 
+
<pre>/home/{username}/siegfried/custom/{custom-dev-sig}.xml</pre>
+
 
+
Extending the signature file can then be completed in two stages:
+
 
+
<pre>1) Roy harvest</pre>
+
 
+
This will download PRONOM signature file reports. This is the most accurate way to run Siegfried. An alternative is to let Siegfried parse the DROID signature file, but this has shown to lead to some inconsistencies where PRONOM and DROID do not reflect each other entirely.
+
 
+
<pre>2) Roy build -extend {custom-dev-sig}.xml</pre>
+
 
+
Try Siegfried on a single file of the format we have created the signature for:
+
 
+
<pre>3) sf {custom-dev-format}.{ext}</pre>
+
 
+
The result will be:
+
 
+
<pre>---
+
siegfried  : 1.7.6
+
scandate    : 2017-10-25T23:35:31+13:00
+
signature  : default.sig
+
created    : 2017-10-25T23:23:59+13:00
+
identifiers :
+
  - name    : 'pronom'
+
    details : 'DROID_SignatureFile_V91.xml; container-signature-20170330.xml; extensions: {custom-dev-sig}.xml'
+
---
+
filename : '{custom-dev-format}.{ext}'
+
filesize : 1492992
+
modified : 2017-10-22T16:02:13+13:00
+
errors  :
+
matches  :
+
  - ns      : 'pronom'
+
    id      : 'dev/1'
+
    format  : '{custom-dev-format}'
+
    version : '1.0'
+
    mime    : 'application/{custom-dev-format}'
+
    basis  : 'extension match img; byte match at 1024, 32'
+
    warning : </pre>
+
 
+
=== RDF ===
+
 
+
The tool's output suggests a potential RDF representation of a DROID signature. This looks as follows
+
 
+
<pre>
+
<?xml version="1.0" encoding="UTF-8"?>
+
<rdf:RDF xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:sigdev="http://nationalarchives.gov.uk/preservation/sigdev/signature/" xmlns:bytes="http://nationalarchives.gov.uk/preservation/sigdev/signature/byteSequence/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
+
  <sigdev:DevelopmentSignature rdf:about="http://nationalarchives.gov.uk/preservation/sigdev/signature/ddc3ab7d-db41-49c5-b3fa-262ad83dd703">
+
    <rdfs:label>Development Signature</rdfs:label>
+
    <sigdev:version>1.0</sigdev:version>
+
    <sigdev:extension>ext</sigdev:extension>
+
    <sigdev:internetMediaType>text/x-test-signature</sigdev:internetMediaType>
+
    <sigdev:puid>dev/1</sigdev:puid>
+
    <sigdev:byteSequence>
+
      <rdf:Description rdf:about="http://nationalarchives.gov.uk/preservation/sigdev/signature/byteSequence/228c0626-3e0d-40bc-98d3-d897a21b20e1/1">
+
        <bytes:string rdf:datatype="http://nationalarchives.gov.uk/preservation/sigdev/signature/droidRegularExpression">255044462D312E34</bytes:string>
+
        <bytes:anchor>BOFoffset</bytes:anchor>
+
        <bytes:offset rdf:datatype="http://www.w3.org/2001/XMLSchema#integer">0</bytes:offset>
+
        <bytes:maxOffset rdf:datatype="http://www.w3.org/2001/XMLSchema#integer">0</bytes:maxOffset>
+
      </rdf:Description>
+
    </sigdev:byteSequence>
+
  </sigdev:DevelopmentSignature>
+
</rdf:RDF>
+
</pre>
+
 
+
This can be used to generate a graph visualization of a signature, and provides another serialization of a DROID signature that could potentially be consumed by tools in the future.
+
 
+
== 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. -->
+
 
+
* [http://digital-archiving.blogspot.co.nz/2016/08/my-first-file-format-signature.html Jenny Mitcham creates her first signature using the Signature Development Utility]
+
* [http://openpreservation.org/blog/2016/09/08/making-the-switch-from-user-to-user-and-contributor-my-first-file-format-signature/ Andrea K. Byrne creates her first signature using the Signature Development Utility]
+
 
+
== Development Activity ==
+
 
<!-- 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. -->
 
All development activity is visible on GitHub: https://github.com/exponential-decay/signature-development-utility/commits
 
All development activity is visible on GitHub: https://github.com/exponential-decay/signature-development-utility/commits
 
   
 
   
==== Activity Feed ====
+
=== Activity Feed ===
 
Below the last 5 commits:
 
Below the last 5 commits:
 
<rss max=5>https://github.com/exponential-decay/signature-development-utility/commits/master.atom</rss>
 
<rss max=5>https://github.com/exponential-decay/signature-development-utility/commits/master.atom</rss>

Please note that all contributions to COPTR are considered to be released under the Attribution-ShareAlike 3.0 Unported (see COPTR:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel | Editing help (opens in new window)