PRONOM Signature Development Utility - Revision history

Ross-spencer: Add homepage for the utility itself

2022-01-31T14:35:24Z

Add homepage for the utility itself

Ross-spencer: Fixed development activity RSS

2021-06-14T16:48:07Z

Fixed development activity RSS

Ross-spencer at 13:17, 18 May 2021

2021-05-18T13:17:00Z

Ania Molenda at 15:18, 26 April 2021

2021-04-26T15:18:14Z

Ross-spencer: /* Using its Output */

2020-03-06T04:30:41Z

Using its Output

Ross-spencer: Corrected harvest command.

2017-11-06T05:19:17Z

Corrected harvest command.

Ross-spencer: Added Siegfried and User Experiences

2017-11-02T23:21:47Z

Added Siegfried and User Experiences

Chlara: Use the structure provided in this template, do not change it! -> "User Experiences" added

2017-04-20T06:25:25Z

Use the structure provided in this template, do not change it! -> "User Experiences" added

Yfriese at 08:07, 4 April 2017

2017-04-04T08:07:44Z

Ross-spencer: Initial page linking back to GitHub repo

2016-09-07T05:34:25Z

Initial page linking back to GitHub repo

New page

{{Infobox_tool
|purpose=Output DROID compatible file format signature files using PRONOM syntax
|image=
|homepage=https://github.com/exponential-decay/signature-development-utility
|license=Open source (see URL above)
|platforms=PHP + JQuery + Javascript + text/html
}}


[[Category:File Format Identification]]



== 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.

= 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:
<rss max=5>https://github.com/exponential-decay/signature-development-utility/commits/master.atom</rss>


{{Infobox_tool_details
|ohloh_id=
}}

@@ Line 1: / Line 1: @@
 {{Infobox tool
 |purpose=Output DROID compatible file format signature files using PRONOM syntax
-|homepage=https://github.com/exponential-decay/signature-development-utility
+|homepage=https://github.com/exponential-decay/signature-development-utility, http://ffdev.info
 |license=Open source (see URL above)
 |platforms=Golang + PHP + JQuery + Javascript + text/html

@@ Line 3: / Line 3: @@
 |homepage=https://github.com/exponential-decay/signature-development-utility
 |license=Open source (see URL above)
-|platforms=PHP + JQuery + Javascript + text/html
+|platforms=Golang + PHP + JQuery + Javascript + text/html
 |function=File Format Identification
 }}
@@ Line 9: / Line 9: @@
 == Description ==
 <!-- 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.
-Signature File 88 contains of 1427 different PUIDs.
+=== Version 2: FFDev.info ===
 == Using its Output ==
@@ Line 17: / Line 37: @@
 === 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'.
+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'. Container signatures need to be added via the users /home/<username>/.droid6 directory. On Windows the user's home folder can be found under Users in 'C:'.
 === Siegfried ===
@@ Line 69: / Line 89: @@
 === RDF ===
-The tool's output suggests a potential RDF representation of a DROID signature. This looks as follows
+The tool's output suggests a potential RDF representation of a DROID signature ('''NB.''' this is a version 1 option only).
 <pre>
@@ Line 94: / Line 116: @@
 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 ==
+== 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. -->
@@ Line 100: / Line 122: @@
 * [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 ==
+== Additional reading ==
 <!-- 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
-==== Activity Feed ====
+==== Activity feed ====
 Below the last 5 commits:
 <rss max=5>https://github.com/exponential-decay/signature-development-utility/commits/master.atom</rss>
 <!-- Add the Ohloh.com ID for the tool, if known. -->

@@ Line 73: / Line 73: @@
      basis   : 'extension match img; byte match at 1024, 32'
      warning : </pre>
 == User Experiences ==

@@ Line 40: / Line 40: @@
 Extending the signature file can then be completed in two stages:
-<pre>1) Roy -harvest</pre>
+<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.

@@ Line 19: / Line 19: @@
 Signature File 88 contains of 1427 different PUIDs.
 == 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 ==