COPTR - User contributions [en-gb]

DROID (Digital Record Object Identification)

2026-04-18T14:24:01Z

Andrew N. Jackson: Update status

{{Infobox tool
|purpose=DROID (Digital Record Object Identification) is a software tool developed to perform automated batch identification of file formats.
|homepage=http://digital-preservation.github.io/droid/
|tool_status=Maintained
|sourcecode=https://github.com/digital-preservation/droid
|license=BSD License
|platforms=Java 6 Standard Edition
|formats_in=PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=CSV (Comma Separated Values)
|function=File Format Identification, Metadata Extraction
}}
= Description =
DROID (Digital Record Object Identification) is a software tool developed to perform automated batch identification of file formats. DROID is designed to meet the fundamental requirement of any digital repository to be able to identify the precise format of all stored digital objects, and to link that identification to a central registry of technical information about that format and its dependencies.

DROID uses the PRONOM [http://www.nationalarchives.gov.uk/aboutapps/pronom/droid-signature-files.htm signature files] to perform format identification. Like PRONOM, it was [http://www.nationalarchives.gov.uk/information-management/manage-information/policy-process/digital-continuity/file-profiling-tool-droid/ developed by the National Archives of the UK]. Written in Java, XML.

=== PRONOM ===
The format information held in PRONOM is what powers [[DROID (Digital Record Object Identification)]]. Both are maintained by the [http://www.nationalarchives.gov.uk/ UK's National Archives].

DROID downloads the latest [http://www.nationalarchives.gov.uk/aboutapps/pronom/droid-signature-files.htm signature files] from PRONOM, and those are used to drive the identification process. See the [http://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml PRONOM release notes].

A number of other tools and registries have been based around the PRONOM data. These include:

* [[Nanite]] and [[Fido]] identification tools
* [[Siegfried]] identification tool

Although the information and website are made freely available under the Open Government License, the underlying software engine that powers PRONOM is proprietary.

===== The PRONOM Web API =====
The website is oriented towards manual browsing, but note that each PRONOM registry entry as a permalink, like this:

https://www.nationalarchives.gov.uk/PRONOM/fmt/579

and furthermore, by appending '.xml' to the URL for any entry, the data can be recovered as XML:

https://www.nationalarchives.gov.uk/PRONOM/fmt/579.xml

= User Experiences =
* [https://www.dpconline.org/handbook/tool-demos/droid-demo Tool demo with videos] in the [https://www.dpconline.org/handbook DPC Handbook]
* [http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf Digital Asset Assessment Tool - Assessment of file format testing tools].
* Comparing how [[Apache Tika]] and DROID perform HTML identification: [http://britishlibrary.typepad.co.uk/webarchive/2014/07/how-much-of-the-uk-html-is-valid.html How much of the UK's HTML is valid?]
* [http://openplanetsfoundation.org/blogs/2014-06-03-analysis-engine-droid-csv-export An Analysis Engine for the DROID CSV Export]
* '''KOST-CECO:''' Used in [[KOST-Val]] for the file format identification. For performance and granularity reasons an own SignatureFile is used instead of the official PRONOM registry.
* '''FITS (File Information Tool Set):''' Used in [[FITS (File Information Tool Set)|FITS]]

= Development Activity =
All development activity is visible on GitHub: http://github.com/digital-preservation/droid/commits

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/digital-preservation/droid/releases.atom</rss>

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/digital-preservation/droid/commits/master.atom</rss>

=== About Formats ===
DROID do only read the format itself, not the spesification as such
{{Infobox tool details
|ohloh_id=droid
}}

DROID (Digital Record Object Identification)

2026-04-18T14:22:28Z

Andrew N. Jackson: Fix up broken PRONOM URLs

{{Infobox tool
|purpose=DROID (Digital Record Object Identification) is a software tool developed to perform automated batch identification of file formats.
|homepage=http://digital-preservation.github.io/droid/
|license=BSD License
|platforms=Java 6 Standard Edition
|formats_in=PREMIS (Preservation Metadata Implementation Strategies)
|function=File Format Identification, Metadata Extraction
}}
= Description =
DROID (Digital Record Object Identification) is a software tool developed to perform automated batch identification of file formats. DROID is designed to meet the fundamental requirement of any digital repository to be able to identify the precise format of all stored digital objects, and to link that identification to a central registry of technical information about that format and its dependencies.

DROID uses the PRONOM [http://www.nationalarchives.gov.uk/aboutapps/pronom/droid-signature-files.htm signature files] to perform format identification. Like PRONOM, it was [http://www.nationalarchives.gov.uk/information-management/manage-information/policy-process/digital-continuity/file-profiling-tool-droid/ developed by the National Archives of the UK]. Written in Java, XML.

=== PRONOM ===
The format information held in PRONOM is what powers [[DROID (Digital Record Object Identification)]]. Both are maintained by the [http://www.nationalarchives.gov.uk/ UK's National Archives].

DROID downloads the latest [http://www.nationalarchives.gov.uk/aboutapps/pronom/droid-signature-files.htm signature files] from PRONOM, and those are used to drive the identification process. See the [http://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml PRONOM release notes].

A number of other tools and registries have been based around the PRONOM data. These include:

* [[Nanite]] and [[Fido]] identification tools
* [[Siegfried]] identification tool

Although the information and website are made freely available under the Open Government License, the underlying software engine that powers PRONOM is proprietary.

===== The PRONOM Web API =====
The website is oriented towards manual browsing, but note that each PRONOM registry entry as a permalink, like this:

https://www.nationalarchives.gov.uk/PRONOM/fmt/579

and furthermore, by appending '.xml' to the URL for any entry, the data can be recovered as XML:

https://www.nationalarchives.gov.uk/PRONOM/fmt/579.xml

= User Experiences =
* [https://www.dpconline.org/handbook/tool-demos/droid-demo Tool demo with videos] in the [https://www.dpconline.org/handbook DPC Handbook]
* [http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf Digital Asset Assessment Tool - Assessment of file format testing tools].
* Comparing how [[Apache Tika]] and DROID perform HTML identification: [http://britishlibrary.typepad.co.uk/webarchive/2014/07/how-much-of-the-uk-html-is-valid.html How much of the UK's HTML is valid?]
* [http://openplanetsfoundation.org/blogs/2014-06-03-analysis-engine-droid-csv-export An Analysis Engine for the DROID CSV Export]
* '''KOST-CECO:''' Used in [[KOST-Val]] for the file format identification. For performance and granularity reasons an own SignatureFile is used instead of the official PRONOM registry.
* '''FITS (File Information Tool Set):''' Used in [[FITS (File Information Tool Set)|FITS]]

= Development Activity =
All development activity is visible on GitHub: http://github.com/digital-preservation/droid/commits

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/digital-preservation/droid/releases.atom</rss>

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/digital-preservation/droid/commits/master.atom</rss>

=== About Formats ===
DROID do only read the format itself, not the spesification as such
{{Infobox tool details
|ohloh_id=droid
}}

Pandoc

2026-03-20T09:03:38Z

Andrew N. Jackson: Some updated info and an example of use

{{Infobox tool
|purpose=If you need to convert files from one markup format into another, pandoc is your swiss-army knife.
|homepage=https://pandoc.org/
|tool_status=Maintained
|sourcecode=https://github.com/jgm/pandoc
|license=Free under the GPL
|platforms=Windows, MacOS, Linux, BSD
|language=Haskell
|function=File Format Migration
|content=Document
}}








== Description ==


== User Experiences ==

* [https://anjackson.net/2026/01/26/coptr-dpclinic/ Example of PPTX converted to Markdown to make a web version of a presentation]

== Development Activity ==

Releases are documented through the [http://pandoc.org/releases.html Pandoc release page]. Pandoc 2.3 was released in September 2018.

{{Infobox tool details}}

About COPTR

2026-03-19T19:17:32Z

Andrew N. Jackson: /* How can I get involved? */ Suggested prioritisation.

__NOTOC__
COPTR is a wiki based registry of digital preservation tools and workflows. It's main aim is to help practitioners discover preservation tools that might help them tackle particular preservation challenges. It can be browsed and searched directly by practitioners, or queried by other systems via an API.

Each tool in COPTR is categorised by the [[Lifecycle Stages|Lifecycle Stage]] it falls within, the (sub) [[Tool Functions|Function]] it performs and by the [[Content Types|Content Type]] that it operates on. It may also input and/or output specific [[File_Formats|file formats]]. For example, [[EpubCheck]] performs the Function [[Validation]], it operates on [[EBook]] Content and has [[EPUB]] as an input format. COPTR can help by enabling you to browse to tools that meet a particular need - perhaps relating to a specific [[Content Types|Content Type]] or [[Tool Functions|Function]].

COPTR also holds [[Workflow:Community_Owned_Workflows|digital preservation workflows]]. Sharing a workflow is a great way to exchange digital preservation practice and enable conversations around tools and how they are used.

[[Video guides to using COPTR|Watch these videos to find out more about how to use, and how to contribute to, COPTR]].

==How can I get involved?==
COPTR is a wiki, which means anyone can edit it and your contributions are very welcome. All changes are tracked, so if a mistake is made, it can easily be undone. So don't hold back - please dive in a help make the information in COPTR better.
Editing this wiki requires a user account, but due to problems with spam, you have to get in touch with us to request an account. Just email [mailto:coptr@openpreservation.org coptr@openpreservation.org] with your preferred username and we'll get you sorted. If you have any problems accessing your account, or want to report any spam, you can use the same contact email to request help.
Here are some suggestions:
*[[Add a tool to COPTR|Add a new tool to COPTR]]. Add a tool you're familiar with or check out this [[Wish list of tools to add to COPTR|wish list of tools to add to COPTR]].
** We know there are always more tools to find. If you can see lots of gaps, but are unsure of where to start, feel free to prioritise the tools that you know best, or the tools you think will be the most use to the most people.
*[[Contribute your workflow to COW|Add a new workflow to COW]]. It doesn't have to be a finished workflow - a draft or proposal is still useful!
*Correct or add more detail to existing entries - use the "Edit with form" option to do this. For example, you could:
** Check the [[:Category:Tool Status|Tool Status]], especially [[:Category:Unknown_Tool_Status|where the status is not known]].
** Flag1 or fix up outdated details, like broken URLs.
** Flag1 or remove text that does not meet the editorial guidelines (see ''Scope'' below).
** Add input or output formats. Ask for help (see below) if you need to create new [[File_Formats|File format]] entries.2

Beyond using, adding and updating the contents, you can also get involved by helping sustain and grow COPTR itself. Please take a look at the sustainability and governance sections below!

1Need to add some guidance on how to flag these cases.

2Can this be made easier?

==What is the scope of COPTR?==
COPTR captures basic, factual details about a tool, what it does, how to find more information (relevant URLs) and references to user experiences with the tool. The scope is a broad interpretation of the term "digital preservation". In other words, if a tool is useful in performing a digital preservation function such as those described in the OAIS model or the DCC lifecycle model, then it's within scope of this registry.

*In scope: Characterisation, visualisation, rendering, migration, storage, fixity, access, delivery, search, web archiving, open source software ->everything inbetween<- commercial software.
*Out of scope: Digitisation, file creation

Crucially, the goal of COPTR is to help you find tools to try out, not tell you what tools to use. The right tool often depends on your specific context and goals. By linking tools to user experiences, workflows, and other records of practice, we hope it will be easier to find out what others are doing, and that this will help you evaluate what you need.

Beyond tools, there are a number of other 'registries' that are related to COPTR and interlinked with it such as the [http://fileformats.archiveteam.org/ Just Solve The Problem File Formats Wiki] for detailed file format information, and the [https://www.nationalarchives.gov.uk/pronom/ PRONOM] format identification registry. You can find more resources and registries on the [https://github.com/digipres/awesome-digital-preservation?tab=readme-ov-file#readme Digital Preservation Awesome List].

==Why does COPTR exist?==
The digital preservation community had created a whole host of different tool registries that described preservation tools. Many people had also written blog posts about tools or organisations hosted web pages with lists of tools that tackled particular areas. There was lots of duplication between these lists and registries, but at the same time, each one often held tools that weren't described elsewhere. COPTR was built by bringing together and rationalising these other registries and lists. It was originally created in 2012 as a small activity within the Jisc funded [http://wiki.opf-labs.org/display/SPR SPRUCE Project] ([https://www.dpconline.org/digipres/collaborative-projects/completed-projects/spruce more info]), and has been significantly developed since - most notably with an upgrade to Semantic Mediawiki in 2021.

It was inspired by the original [http://digitalpowrr.niu.edu/ Preserving digital Objects With Restricted Resources project (POWRR)] Tools Grid and developed in partnership with the POWRR Project.

==Governance==
Currently COPTR does not have a community governance process in place.

It is supported by the Open Preservation Foundation (OPF) and the Digital Preservation Coalition (DPC), who cover the basic aspect of hosting the service, taking backups, removing entries that are clearly off-topic spam or abusive. Other issues, such as guidelines or processes around content quality, scope, review (see e.g. responding to [[Talk:Main_Page| Main page/discussion]]) or major service changes (e.g. shifting to other platforms, or dealing with the sustainability issues outlined below) are not covered.

The staff of the OPF and DPC are not the target users for COPTR, so we would like to encourage community members who care about COPTR to help us find a way to improve this situation. Please join us or get in touch via [[#Contact.2C_feedback_and_questions|the contact details below]]!

==Sustainability==

COPTR is stable, but has some sustainability issues. [https://github.com/orgs/digipres/discussions/66 Please see the full details in this statement on the service status and sustainability.]

==Technical stuff==
*[[Data structures in COPTR]] - information on the COPTR data model and its maintenance
*[[How COPTR Works]] - information on the technical setup of COPTR
*How to use the [[Using the COPTR data feed|COPTR data feed and API]]
*[[Development plans]]

==Organizational Contributions==

Organisations who would like to contribute the contents of their tool registry to COPTR should:

*Merge your own tool registry data with the new community registry (COPTR can help with this)
*Remove your own registry and agree not to set up any new project owned registries/lists
*Link to COPTR or expose the COPTR data by utilising the COPTR data feed
*Contribute any effort you have in adding new tools over time, to the community registry

COPTR is aiming to concentrate information about digital preservation tools in one place, keep the information in the registry maintainable and current by pooling the community's effort in one place, and avoid the emergence of new registries.

==Contact, feedback and questions==
Email [mailto:coptr@openpreservation.org coptr@openpreservation.org] if you have problems using the service, e.g. making sure you have a user account that works.

You can use [[Talk:Main_Page| Main page/discussion]] or [https://github.com/orgs/digipres/discussions the DigiPres.org GitHub discussion forums] to provide open feedback or raise questions or issues with the service.

If you'd like some support, or you're just curious about COPTR, please consider joining the [https://dpconline.org/digipres/pr-sig Preservation Registries Special Interest Group (PR-SIG)] and coming along to one our online ''Collaboration Café'' calls.

==COPTR Partners==
COPTR was created and launched with the support of the [http://www.educopia.org/events/ANADPII Aligning National Approaches to Digital Preservation] initiative and has been populated and maintained by members of the COPTR partner organisations:
<gallery heights=90>
File:DCClogo.png|[http://www.dcc.ac.uk The Digital Curation Centre (DCC)]
File:DCElogo.gif|[http://digitalcurationexchange.org/ The Digital Curation Exchange (DCE)]
File:DPCLogoSquare.png|[http://dpconline.org/ The Digital Preservation Coalition (DPC)]
File:nde-logo.png|[http://www.netwerkdigitaalerfgoed.nl Dutch Digital Heritage Network (DDHN)]
File:NDSAlogo.jpg|[https://ndsa.org National Digital Stewardship Alliance (NDSA)]
File:nestor-logo.jpg|[https://www.langzeitarchivierung.de/Webs/nestor/EN/nestor/nestor_node.html Network of expertise in long-term storage of digital resources in Germany (NESTOR)]
File:Opf-logo.png|[http://openpreservation.org// The Open Preservation Foundation (OPF)]
File:POWRRlogo.jpg|[http://digitalpowrr.niu.edu/ Preserving digital Objects With Restricted Resources project (POWRR)]
</gallery>

==Funding and development==
COPTR was made possible by support from the Jisc funded SPRUCE Project and the Institute of Museum and Library Services funded Digital POWRR Project.
<gallery heights=90>
File:2013 Jisc Logo RGB72.png|[http://www.jisc.ac.uk/ Jisc]
File:SPRUCElogo.png|[http://wiki.opf-labs.org/display/SPR SPRUCE Project]
File:POWRRlogo.jpg|[http://digitalpowrr.niu.edu/ Preserving digital Objects With Restricted Resources project (POWRR)]
File:DPCLogoSquare.png|[https://dpconline.org/ Digital Preservation Coalition (DPC)]
File:nde-logo.png|[http://www.netwerkdigitaalerfgoed.nl Dutch Digital Heritage Network (DDHN)]
</gallery>

Squad-convert

2026-03-19T16:38:52Z

Andrew N. Jackson: Initial entry for a new SIARD tool

{{Infobox tool
|purpose=Application to convert SIARD files to the (experimental) squad format
|homepage=https://github.com/sqdp-specs/squad-convert
|tool_status=Maintained
|sourcecode=https://github.com/sqdp-specs/squad-convert
|license=Apache 2.0
|language=Zig
|formats_in=SIARD
|formats_out=SQUAD
|function=File Format Migration
|content=Database
}}
== Description ==

Early stages, demo application to convert siard files to the (experimental) squad format

As seen at iPRES 2025

== User Experiences ==


== Development Activity ==


{{Infobox tool details
|releases_rss=https://github.com/sqdp-specs/squad-convert/releases.atom
}}

User:Andrew N. Jackson/Test Tool Page

2026-03-19T16:31:12Z

Andrew N. Jackson: Deliberately breaking this page so it does not show up as a tool!

{{Inf

obox tool test
|purpose=This is the home page for the open source implementation of the file(1) command that ships with every free operating system (OpenBSD, Linux, NetBSD, FreeBSD, etc.
|homepage=http://www.darwinsys.com/file/
|function=File Format Identification
|content=Binary Data
}}
= Description =
This is the home page for the open source implementation of the file(1) command that ships with every free operating system (OpenBSD, Linux, NetBSD, FreeBSD, etc.) and has been ported to most systems where people use free software (including OS/2, DOS, MS Windows, etc.).

= User Experiences =

*'''[2019-11-16]''' [https://shapeshed.com/unix-file/ Linux and Unix file command tutorial with examples]

= Development Activity =

All development activity is visible on GitHub: https://github.com/file/file/commits

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/file/file/releases.atom</rss>

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/file/file/commits/master.atom</rss>

Contribute your workflow to COW

2026-02-24T10:36:42Z

Andrew N. Jackson: Updating OSSArcFlow links.

Contributing to COW is easy, but if you'd like to [https://youtu.be/PQ4-Pb73VUY follow an example watch this video]. When you're ready to start, follow these tips:

# Check out one or two [[Browse COW workflows|existing workflows]] first
# Keep your workflow descriptions clean and concise. Text only is fine, but you are welcome to add a diagram. We recommend [https://www.yworks.com/products/yed Yed] as used by [https://bitcuratorconsortium.org/workflows Bitcurator], or [https://www.lucidchart.com/ Lucid Chart] as used by [https://educopia.org/research/ossarcflow OSSArcFlow] (also see the OOSArcFlow [https://app.lucidchart.com/invitations/accept/c1a9814d-ae2d-444a-8673-811bd68b0278 workflow template] which is pre-populated with useful workflow symbols. Also see this blog post from Bill LeFurgy on "[https://blogs.loc.gov/thesignal/2012/03/visualizing-digital-preservation-workflows/ Visualizing Digital Preservation Workflows]". And check out examples as part of the complimentary [https://educopia.org/research-project/ossarcflow/ OSSArcFlow Project] and their [https://educopia.org/wp-content/uploads/2024/09/OSSArcFlow_Guide_FINAL-1.pdf Guide to Documenting Born-Digital Archival Workflows].
# Save an early draft then do a longer edit to avoid loss of your workflow due to login timeouts
# Discuss or ask questions about the workflows of others using the respective "Discussion" pages
# Be friendly - please treat others with respect
# Give us your feedback - let us know how you got on - email andrew.jackson (at) dpconline (dot) org.

===Create a new workflow in COW===
*Create a new workflow by entering a title below and clicking the button.
*Keep your title short and meaningful. Include the general purpose of the workflow and the type of digital content it addresses. Eg. "Workflow for ingesting email"
*Save frequently! Don't worry, once you've saved it you can go back and edit it further.
{{#forminput:form=COW|query string=namespace=Workflow&={{PAGENAME}}|placeholder=Enter the title of your workflow here|button text=Create Workflow}}

Contribute your workflow to COW

2026-02-24T10:34:37Z

Andrew N. Jackson: Update link to yED and contact

Contributing to COW is easy, but if you'd like to [https://youtu.be/PQ4-Pb73VUY follow an example watch this video]. When you're ready to start, follow these tips:

# Check out one or two [[Browse COW workflows|existing workflows]] first
# Keep your workflow descriptions clean and concise. Text only is fine, but you are welcome to add a diagram. We recommend [https://www.yworks.com/products/yed Yed] as used by [https://bitcuratorconsortium.org/workflows Bitcurator], or [https://www.lucidchart.com/ Lucid Chart] as used by [https://educopia.org/research/ossarcflow OSSArcFlow] (also see the OOSArcFlow [https://app.lucidchart.com/invitations/accept/c1a9814d-ae2d-444a-8673-811bd68b0278 workflow template] which is pre-populated with useful workflow symbols. Also see this blog post from Bill LeFurgy on "[https://blogs.loc.gov/thesignal/2012/03/visualizing-digital-preservation-workflows/ Visualizing Digital Preservation Workflows]". And check out examples as part of the complimentary [https://educopia.org/research/ossarcflow OSSArcFlow Project] and their [https://educopia.org/ossarcflow-guide/ Guide to Documenting Born-Digital Archival Workflows].
# Save an early draft then do a longer edit to avoid loss of your workflow due to login timeouts
# Discuss or ask questions about the workflows of others using the respective "Discussion" pages
# Be friendly - please treat others with respect
# Give us your feedback - let us know how you got on - email andrew.jackson (at) dpconline (dot) org.

===Create a new workflow in COW===
*Create a new workflow by entering a title below and clicking the button.
*Keep your title short and meaningful. Include the general purpose of the workflow and the type of digital content it addresses. Eg. "Workflow for ingesting email"
*Save frequently! Don't worry, once you've saved it you can go back and edit it further.
{{#forminput:form=COW|query string=namespace=Workflow&={{PAGENAME}}|placeholder=Enter the title of your workflow here|button text=Create Workflow}}

Template:FormToolPreload

2026-02-13T14:59:20Z

Andrew N. Jackson: Clarifying the form fields below.

== Description ==


== User Experiences ==


== Development Activity ==

Fixity Pro

2026-02-13T14:55:56Z

Andrew N. Jackson: Cross-referencing to AVP Fixity

{{Infobox tool
|image=Fixity-Pro-Logo.png
|purpose=Fixity Pro is a desktop application for Windows and Mac that provides simple automated monitoring and reporting on the data integrity of your files that are stored on your computer, removable storage devices, and mounted network storage locations. Use Fixity Pro to schedule routine scans that will tell you if your files have been changed and if any files have been added, removed, or moved/renamed since the last scan that was performed.
|homepage=https://fixitypro.com/
|tool_status=Maintained
|platforms=Windows, Mac
|function=Fixity
}}
== Description ==

Fixity Pro is a desktop application for Windows and Mac that provides simple automated monitoring and reporting on the data integrity of your files that are stored on your computer, removable storage devices, and mounted network storage locations. Use Fixity Pro to schedule routine scans that will tell you if your files have been changed and if any files have been added, removed, or moved/renamed since the last scan that was performed.

Fixity Pro was the paid version of [[AVP Fixity|AVP's original Fixity program]], which was released in 2020, but [https://openpreservation.org/news/a-new-home-for-fixity-pro-the-opf-to-maintain-the-file-integrity-tool/ as of 2025 Fixity Pro has been transferred to the Open Preservation Foundation] and is now open source and free to use.

Fixity Pro offers a number of improvements and new features in addition to addressing bugs. These include: significantly faster processing times, a progress bar with reporting on time and files remaining, better support for managing external and network storage locations, support for managing partial and incomplete scans, and an improved user interface design.

== User Experiences ==


== Development Activity ==
{{Infobox tool details
|mailing_lists=https://lists.openpreservation.org/postorius/lists/fixitypro.lists.openpreservation.org/
}}

Form:Tool

2026-02-13T14:53:16Z

Andrew N. Jackson: Add editing help

<noinclude>
This is the "Tool" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.

{{#forminput:form=Tool}}

</noinclude><includeonly>
<div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>
{{{for template|Infobox tool}}}
{| class="formtable"
! Image: {{#info:In another tab, use the "Upload file" link to upload a logo image. Paste the name of the image here}}:
| {{{field|image}}}
|-
! Purpose* {{#info:A single sentence describing the function of the tool. Keep it factual and concise}}:
| {{{field|purpose|mandatory|input type=textarea}}}
|-
! Homepage {{#info:The URL of the homepage}}:
| {{{field|homepage}}}
|-
! Status {{#info:The current status of this tool}}:
| {{{field|tool_status}}}
|-
! Sourcecode {{#info:The URL for the source code}}:
| {{{field|sourcecode}}}
|-
! License:
| {{{field|license}}}
|-
! Cost:
| {{{field|cost}}}
|-
! Platforms:
| {{{field|platforms}}}
|-
! Language:
| {{{field|language}}}
|-
! Wikidata ID:
| {{{field|Wikidata ID}}}
|-
! Input formats {{#info:Start typing and select from the available list. Only add a new format if necessary}}:
| {{{field|formats_in|input type=tokens|values from category=Formats}}}
|-
! Output Formats: {{#info:Start typing and select from the available list. Only add a new format if necessary}}:
| {{{field|formats_out|input type=tokens|values from category=Formats}}}
|-
! Function*: {{#info:Start typing and select one or more functions from the available list. Only add a new function if absolutely necessary}}:
| {{{field|function|mandatory|input type=tokens|values from category=Functions}}}
|-
! Content: {{#info:Start typing and select one or more content types from the available list. Only add a new content type if absolutely necessary}}:
| {{{field|content|input type=tokens|values from category=Content Types}}}
|}
{{{end template}}}

'''Description:''' using ''wikitext'' markup. e.g. <nowiki>external links: [https://web.site title], internal links: [[Link To Another Page]], use * for bulleted lists</nowiki>. See [https://www.mediawiki.org/wiki/Cheatsheet this cheatsheet for the full syntax].

{{{standard input|free text|rows=30|editor=visualeditor|preload=Template:FormToolPreload}}}

{{{for template|Infobox tool details}}}
{| class="formtable"
! [https://www.openhub.net/ OpenHub] ID:
| {{{field|ohloh_id}}}
|-
! Mailing_lists:
| {{{field|mailing_lists}}}
|-
! Releases_rss:
| {{{field|releases_rss}}}
|-
! Issues_rss:
| {{{field|issues_rss}}}
|}
{{{end template}}}

</includeonly>

2026-02-05T20:55:42Z

Andrew N. Jackson:

<table class="infobox" border="0" style="float: right; border: 1px solid #aaa; max-width: 33%; overflow: hidden; background-color: #f9f9f9; padding: 0.25em; margin: 0 0.25em 1em;">
{{#if:{{{image|}}}|
<tr><td align="center" colspan="2">[[Image:{{{image}}}|100px|{{PAGENAME}}]]</td></tr>
}}
{{#if:{{{purpose|}}}|
<tr><td align="center" colspan="2">{{{purpose}}}</td></tr>
}}
{{#if:{{{homepage|}}}|
<tr><td>Homepage:</td><td>{{{homepage|Unknown}}}</td></tr>
}}
{{#if:{{{tool_status|}}}|{{#set:ToolStatus={{{tool_status}}}}}
<tr><td>Status:</td><td>{{{tool_status|Unknown}}}</td></tr>
}}
{{#if:{{{sourcecode|}}}|{{#set: Sourcecode={{{sourcecode}}} }}
<tr><td>Source Code:</td><td>{{{sourcecode|Unknown}}}</td></tr>
}}
{{#if:{{{license|}}}|{{#set: License={{{license}}} }}
<tr><td>License:</td><td>{{{license|Unknown}}}</td></tr>
}}
{{#if:{{{cost|}}}| {{#set: Cost={{{cost}}} }}
<tr><td>Cost:</td><td>{{{cost|Unknown}}}</td></tr>
}}
{{#if:{{{platforms|}}}| {{#set: Platforms = {{{platforms}}} }}
<tr><td>Platforms:</td><td>{{{platforms|Unknown}}}</td></tr>
}}
{{#if:{{{language|}}}|
<tr><td>Language:</td><td>{{{language|Unknown}}}</td></tr>
}}
{{#if:{{{Wikidata ID|}}}| {{#set: Wikidata ID = {{{Wikidata ID}}} }}
<tr><td>Wikidata ID:</td><td>[https://www.wikidata.org/wiki/{{{Wikidata ID}}} {{{Wikidata ID}}}]</td></tr>
}}
{{#if:{{{formats_in|}}}|
<tr><td>Input Formats:</td><td>{{#arraymap:{{{formats_in|}}}|,|xqqx|{{#formredlink:target=xqqx|form=Format}}{{#set:Input format=xqqx}} }}</ul></td></tr>
}}
{{#if:{{{formats_out|}}}|
<tr><td>Output Formats:</td><td>{{#arraymap:{{{formats_out|}}}|,|xqqx|{{#formredlink:target=xqqx|form=Format}}{{#set:Output format=xqqx}} }}</td></tr>
}}
{{#if:{{{function|}}}|
<tr><td>Function:</td><td>{{#arraymap: {{{function|}}}|,|xqqx|[[xqqx]]{{#set: Function=xqqx }}[[Category:xqqx]]|,}}</td></tr>|[[Category:Tools without Function]]
}}{{#if:{{{content|}}}|
<tr><td>Content type:</td><td>{{#arraymap: {{{content|}}}|,|xqqx|[[xqqx]]{{#set: Content=xqqx }} [[Category:xqqx]]|, }}</td></tr>|[[Category:Tools without Content Type]]
}}{{#if:{{#ask: [[Category:COW Workflows]] [[Tools::{{PAGENAME}}]]}}|
<tr><td>Appears in [[Workflow:Community_Owned_Workflows|COW]]:</td><td>{{#ask: [[Category:COW Workflows]] [[Tools::{{PAGENAME}}]]|limit=500|format=list}}</td></tr>
}}
</table>
[[Category:Tools]]
{{#if:{{{license|}}}|
|
[[Category:Unknown_license]]
}}
{{#if:{{{tool_status|}}}|
[[Category:{{{tool_status}}}]]
|
[[Category:Unknown_Tool_Status]]
}}
<noinclude>n.b. Created by Andrew N. Jackson to test why additional whitespace lines keep turning up everywhere.</noinclude>

Template:Infobox tool test

2026-02-05T20:54:34Z

Andrew N. Jackson:

<table class="infobox" border="0" style="float: right; border: 1px solid #aaa; max-width: 33%; overflow: hidden; background-color: #f9f9f9; padding: 0.25em; margin: 0 0.25em 1em;">
{{#if:{{{image|}}}|
<tr><td align="center" colspan="2">[[Image:{{{image}}}|100px|{{PAGENAME}}]]</td></tr>
}}
{{#if:{{{purpose|}}}|
<tr><td align="center" colspan="2">{{{purpose}}}{{#if: {{{purpose|}}}|{{#set: Purpose={{{purpose}}} }} }}</td></tr>
}}
{{#if:{{{homepage|}}}|
<tr><td>Homepage:</td><td>{{#if: {{{homepage|}}}|{{#set: Homepage={{{homepage}}} }} }}{{{homepage|Unknown}}}</td></tr>
}}
{{#if:{{{tool_status|}}}|{{#set:ToolStatus={{{tool_status}}}}}
<tr><td>Status:</td><td>{{{tool_status|Unknown}}}</td></tr>
}}
{{#if:{{{sourcecode|}}}|{{#set: Sourcecode={{{sourcecode}}} }}
<tr><td>Source Code:</td><td>{{{sourcecode|Unknown}}}</td></tr>
}}
{{#if:{{{license|}}}|{{#set: License={{{license}}} }}
<tr><td>License:</td><td>{{{license|Unknown}}}</td></tr>
}}
{{#if:{{{cost|}}}| {{#set: Cost={{{cost}}} }}
<tr><td>Cost:</td><td>{{{cost|Unknown}}}</td></tr>
}}
{{#if:{{{platforms|}}}| {{#set: Platforms = {{{platforms}}} }}
<tr><td>Platforms:</td><td>{{{platforms|Unknown}}}</td></tr>
}}
{{#if:{{{language|}}}|
<tr><td>Language:</td><td>{{{language|Unknown}}}</td></tr>
}}
{{#if:{{{Wikidata ID|}}}| {{#set: Wikidata ID = {{{Wikidata ID}}} }}
<tr><td>Wikidata ID:</td><td>[https://www.wikidata.org/wiki/{{{Wikidata ID}}} {{{Wikidata ID}}}]</td></tr>
}}
{{#if:{{{formats_in|}}}|
<tr><td>Input Formats:</td><td>{{#arraymap:{{{formats_in|}}}|,|xqqx|{{#formredlink:target=xqqx|form=Format}}{{#set:Input format=xqqx}} }}</ul></td></tr>
}}
{{#if:{{{formats_out|}}}|
<tr><td>Output Formats:</td><td>{{#arraymap:{{{formats_out|}}}|,|xqqx|{{#formredlink:target=xqqx|form=Format}}{{#set:Output format=xqqx}} }}</td></tr>
}}
{{#if:{{{function|}}}|
<tr><td>Function:</td><td>{{#arraymap: {{{function|}}}|,|xqqx|[[xqqx]]{{#set: Function=xqqx }}[[Category:xqqx]]|,}}</td></tr>|[[Category:Tools without Function]]
}}{{#if:{{{content|}}}|
<tr><td>Content type:</td><td>{{#arraymap: {{{content|}}}|,|xqqx|[[xqqx]]{{#set: Content=xqqx }} [[Category:xqqx]]|, }}</td></tr>|[[Category:Tools without Content Type]]
}}{{#if:{{#ask: [[Category:COW Workflows]] [[Tools::{{PAGENAME}}]]}}|
<tr><td>Appears in [[Workflow:Community_Owned_Workflows|COW]]:</td><td>{{#ask: [[Category:COW Workflows]] [[Tools::{{PAGENAME}}]]|limit=500|format=list}}</td></tr>
}}
</table>
[[Category:Tools]]
{{#if:{{{license|}}}|
|
[[Category:Unknown_license]]
}}
{{#if:{{{tool_status|}}}|
[[Category:{{{tool_status}}}]]
|
[[Category:Unknown_Tool_Status]]
}}
<noinclude>n.b. Created by Andrew N. Jackson to test why additional whitespace lines keep turning up everywhere.</noinclude>

Template:Infobox tool test

2026-02-05T20:53:39Z

Andrew N. Jackson:

<table class="infobox" border="0" style="float: right; border: 1px solid #aaa; max-width: 33%; overflow: hidden; background-color: #f9f9f9; padding: 0.25em; margin: 0 0.25em 1em;">
{{#if:{{{image|}}}|
<tr><td align="center" colspan="2">[[Image:{{{image}}}|100px|{{PAGENAME}}]]</td></tr>
}}
{{#if:{{{tool_status|}}}|{{#set:ToolStatus={{{tool_status}}}}}
<tr><td>Status:</td><td>{{{tool_status|Unknown}}}</td></tr>
}}
{{#if:{{{sourcecode|}}}|{{#set: Sourcecode={{{sourcecode}}} }}
<tr><td>Source Code:</td><td>{{{sourcecode|Unknown}}}</td></tr>
}}
{{#if:{{{license|}}}|{{#set: License={{{license}}} }}
<tr><td>License:</td><td>{{{license|Unknown}}}</td></tr>
}}
{{#if:{{{cost|}}}| {{#set: Cost={{{cost}}} }}
<tr><td>Cost:</td><td>{{{cost|Unknown}}}</td></tr>
}}
{{#if:{{{platforms|}}}| {{#set: Platforms = {{{platforms}}} }}
<tr><td>Platforms:</td><td>{{{platforms|Unknown}}}</td></tr>
}}
{{#if:{{{language|}}}|
<tr><td>Language:</td><td>{{{language|Unknown}}}</td></tr>
}}
{{#if:{{{Wikidata ID|}}}| {{#set: Wikidata ID = {{{Wikidata ID}}} }}
<tr><td>Wikidata ID:</td><td>[https://www.wikidata.org/wiki/{{{Wikidata ID}}} {{{Wikidata ID}}}]</td></tr>
}}
{{#if:{{{formats_in|}}}|
<tr><td>Input Formats:</td><td>{{#arraymap:{{{formats_in|}}}|,|xqqx|{{#formredlink:target=xqqx|form=Format}}{{#set:Input format=xqqx}} }}</ul></td></tr>
}}
{{#if:{{{formats_out|}}}|
<tr><td>Output Formats:</td><td>{{#arraymap:{{{formats_out|}}}|,|xqqx|{{#formredlink:target=xqqx|form=Format}}{{#set:Output format=xqqx}} }}</td></tr>
}}
{{#if:{{{function|}}}|
<tr><td>Function:</td><td>{{#arraymap: {{{function|}}}|,|xqqx|[[xqqx]]{{#set: Function=xqqx }}[[Category:xqqx]]|,}}</td></tr>|[[Category:Tools without Function]]
}}{{#if:{{{content|}}}|
<tr><td>Content type:</td><td>{{#arraymap: {{{content|}}}|,|xqqx|[[xqqx]]{{#set: Content=xqqx }} [[Category:xqqx]]|, }}</td></tr>|[[Category:Tools without Content Type]]
}}{{#if:{{#ask: [[Category:COW Workflows]] [[Tools::{{PAGENAME}}]]}}|
<tr><td>Appears in [[Workflow:Community_Owned_Workflows|COW]]:</td><td>{{#ask: [[Category:COW Workflows]] [[Tools::{{PAGENAME}}]]|limit=500|format=list}}</td></tr>
}}
</table>
[[Category:Tools]]
{{#if:{{{license|}}}|
|
[[Category:Unknown_license]]
}}
{{#if:{{{tool_status|}}}|
[[Category:{{{tool_status}}}]]
|
[[Category:Unknown_Tool_Status]]
}}
<noinclude>n.b. Created by Andrew N. Jackson to test why additional whitespace lines keep turning up everywhere.</noinclude>