{"id":1886,"date":"2024-11-11T19:28:08","date_gmt":"2024-11-11T19:28:08","guid":{"rendered":"https:\/\/exponentialdecay.co.uk\/blog\/?p=1886"},"modified":"2025-01-17T14:18:37","modified_gmt":"2025-01-17T14:18:37","slug":"simpledroid-completing-the-circle","status":"publish","type":"post","link":"https:\/\/exponentialdecay.co.uk\/blog\/simpledroid-completing-the-circle\/","title":{"rendered":"simpledroid: completing the loop"},"content":{"rendered":"

It’s nearing the end of 2024 and that must mean a PRONOM hackathon<\/a> as part of the World Digital Preservation Day (#WDPD2024).<\/p>\n

My contribution is a follow-up on my work earlier in the year to produce a valid DROID signature file from Wikidata in wddroidy<\/a>.<\/p>\n

<\/p>\n

simpledroid<\/a> is a Python package that is available on GitHub and creates a simple DROID signature file from PRONOM itself, creating a scripted pathway to create a signature file using official PRONOM data that doesn’t require the current PRONOM database and its legacy stored procedures.<\/p>\n

A reference signature file<\/a> is also available on GitHub; this can be used immediately with DROID. You may be able to see from the reference signature file that we do away with a lot of the excess data in the current DROID signature file which was previously an optimization for its Boyer Moore Horspool search algorithm, as described by Matthew Palmer<\/a>. This is no longer needed.<\/p>\n

The primary reason for simpledroid was to complete the loop on my previous efforts and to prove that it was possible to create a simplified signature file and for it to work with DROID. The result is about 80-90% there, with only a few skeleton files<\/a> that remain unidentified – it should only require a small amount of forensic research to determine the reason.<\/p>\n

\"Screenshot<\/a><\/p>\n

The output provides a way for simplifying the signature file generation process, offering new opportunities to create alternative versions, or filtering what’s already there, e.g. filtering out any signatures that aren’t explicitly for image identification, e.g. in a digitization workflow.<\/p>\n

It may provide another way into PRONOM data for those who might look at DROID first as well as opening up different ways to modify and test signatures.<\/p>\n

It is possible to see in the reference output<\/a>, that the signatures are much easier to understand via this simplified DROID file.<\/p>\n

\"A<\/a><\/p>\n

simpledroid outputs a file with a smaller footprint than the current file:<\/p>\n

1.2M DROID_SignatureFile_Simple_2024-11-11T12-29-22Z.xml<\/code>
\n3.4M DROID_SignatureFile_V118.xml<\/code><\/p>\n

It also contains all of the file classification data e.g. FormatType=\"Video\"<\/code> from PRONOM that will be added into DROID in a future release (and is already available in Siegfried).<\/p>\n

Unlike the wddroidy work, priorities have also been added to the signature file so the mechanics of the signature file are pretty close to the official version (DROID uses the signature sequence and offsets to identify a file, but it then uses a priority to determine what results to display to the user where there may otherwise be positive matches for formats that provide the foundation for another, e.g. how XML forms the basis of SVG or XHTML).<\/p>\n

It might be possible to remove some data around minimum and maximum offsets in the new file after discovering that simplified droid syntax requires curly bracket syntax at the beginning and end of sequences to mimic the same behavior, e.g.<\/p>\n

With a BOFoffset<\/code>, min_offset = 2<\/code>, and signature = BADF00D1<\/code>, the signature needs to become {2}BADF00D1<\/code> to work.<\/p>\n

The code is pretty straightforward and uses a few tricks to output XML sensibly without having to build the document’s tree (DOM) in a more verbose way. There are probably a few other shortcuts I’d fix with time if the code was ever useful, including improving variable naming and adding tests.<\/p>\n

I’m not sure this code will ever be used by anyone, but for a quick hack and a quick proof of concept, it felt good to put it out there. Maybe someone will look at this or the wddroidy work and see there may be a way to federate different sources of signature information together into something DROID can use. Or it might be a useful demonstration to the DROID team that allows them to simplify PRONOM’s database and output mechanisms in a way that remains compatible with existing tools.<\/p>\n

Previous research week work<\/h2>\n

My previous work for PRONOM research week includes a dashboard and API<\/a> for getting more information out of PRONOM, including listings of those records still requiring descriptions or signatures. You may find that work interesting and it is available at https:\/\/pronom.ffdev.info<\/a> and https:\/\/api.pronom.ffdev.info<\/a>.<\/p>\n

And if you want to get in on the signature development work, signature development utility 2.0 (https:\/\/ffdev.info<\/a>) was also a previous effort of mine for research week 2020<\/a> and will hopefully also benefit from outputting DROID’s simplified syntax.<\/p>\n

A week of file formats<\/h2>\n

Of course with World Digital Preservation Day, file formats were pretty popular.<\/p>\n

Andrew Jackson attempted to calculate how many distinct formats<\/a> might be out there using methods used to calculate ecological diversity.<\/p>\n

Amanda Tome described the scope of their work<\/a> and shared a number of useful resources including useful links to the PRONOM starter pack and to the PRONOM drop-in sessions.<\/p>\n

You might also find out a bit more about yourself<\/em> by playing this File Format Dating Game<\/a> from Lotte Wijsman and colleagues: Susanne van den Eijkel, Anton van Es, Elaine Murray, Francesca Mackenzie, Ellie O\u2019Leary, and Sharon McMeekin.<\/em> (I ended up on a date with FASTA<\/a> (FDD000622<\/a>) in my first play-through!)<\/p>\n

Not specifically for WDPD, but in the same week I also enjoyed this presentation from Ange Albertini looking at different ways of identifying file formats. One big take away for me was thinking about how to get more forensic information out of a file format identification. DROID doesn’t tell us a lot, but is there a world in which one day it could<\/a>?<\/p>\n