COPTR - User contributions [en-gb]

DataFlow

2026-05-26T15:40:29Z

BertrandCaron: added BagIt as an output format

{{Infobox tool
|purpose=DataFlow is a two-stage data management infrastructure that is designed to allow researchers to work with, annotate, publish, and permanently store research data.
|homepage=http://www.dataflow.ox.ac.uk
|formats_out=BagIt
|function=Managing Active Research Data, Storage
|content=Research Data
}}
= Description =
[http://www.dataflow.ox.ac.uk DataFlow] is a two-stage data management infrastructure that is designed to allow researchers to work with, annotate, publish, and permanently store research data.
There are two components to DataFlow: [http://www.dataflow.ox.ac.uk/index.php/about/about-datastage DataStage] and [http://www.dataflow.ox.ac.uk/index.php/about/about-databank DataBank].
DataStage is a secure, personalized 'local' file management environment for use at the research group level. It appears as a mapped drive on the end-user's computer, with additional features such as repository submission and addition of metadata available via a web interface.
DataBank is a scalable, domain-agnostic data repository system designed specifically to manage and share research data in an institutional setting.
====Provider====
The University of Oxford, with JISC funding
====Licensing and cost====
Free – open source [http://www.opensource.org/licenses/MIT MIT license]
====Development activity====
DataFlow Version 0.2 was released in February 2012. Version 0.3 was released in May 2012, and Version 1.0 is scheduled for release on 31 May 2012.
While the DataFlow project will end in May 2012, the Oxford Bodleian Library has decided to trial the software for its own use and will support development until at least May 2013.
====Platform and interoperability====
DataBank is written in Python. Both DataBank and DataStage are designed to work with the Ubuntu Linux 11.10 Oneiric Ocelot operating system, and the Virtual Machines work with VMWare Fusion 4.x. The system may be deployed on the Eduserv cloud, on a commercial data storage cloud, or on a local institutional server.
Although specifically designed to work together, both DataBank and DataStage offer simple APIs that other services can use to integrate with the individual components.
====Functional notes====
DataBank’s digital object model is based around "collections," also known as "silos," that function as virtual administrative groups. Each silo has a set of users who can read and write files in the silo, and an administrator to manage it. A data package belongs to a silo and may contain one or many data files, metadata files, and license information for the contents of the data package. The administrator can set up an embargo period for the silo, or for an individual data package.
All data is stored as ZIP files, which are unzipped by the software in the access process. Metadata is added and modified directly through RDF files, although it is exposed in both human- and machine-readable forms. The software will also assign DOIs to data sets.
Unless the administrator adds a robots file saying they do not want to be crawled, by default all data held in a non-dark instance of DataBank are visible to Google and any other web crawlers.
DataStage gives three levels of password-controlled access: a "private" area only accessible to the file owner and the group leader, a "shared" area giving read-only access to the group, and a "collaborative" area giving read- and write-access. The administrator can invite outside collaborators into the group, pinpointing their level of access. Users can also access and annotate the files through a web interface.
DataStage can be deployed on a local server, or on an institutional or commercial cloud; users can also dynamically invoke additional cloud storage as required. Users can integrate the system into existing backup procedures. The repository interface also allows researchers to push selected files into a more permanent archive facility.
While users can add free-text metadata via the web interface, DataStage also automatically captures a number of general file attributes: date uploaded; file name; last modified; type; owner; location; and size.
====Documentation and user support====
There is a variety of documentation for the project, including an [http://www.dataflow.ox.ac.uk/index.php/datastage/users/test-users Information for Test Users] page, a [https://github.com/dataflow/DataStage/wiki DataStage documentation wiki], and a [https://github.com/dataflow/RDFDatabank/wiki DataBank documentation wiki]. Users can access an email list at [mailto:dataflow-devel@googlegroups.com dataflow-devel@googlegroups.com], and can report problems through an [http://dataflow-jira.bodleian.ox.ac.uk/jira/secure/IssueNavigator.jspa Issue Tracker].
The project is creating video walkthroughs for installation, configuration and use of DataStage and DataBank, to be available from the website by the end of May 2012.
====Usability====
End-users can interact with the DataBank system through a web interface, but metadata must be added by uploading an rdf file. DataStage appears either as a mapped drive on a user’s computer, implicitly integrating with their operating system’s current navigation structure, or through a web interface.
Installation and configuration use a command-line interface.
====Expertise required====
Installation and configuration require solid knowledge of command line interfaces, and benefit from system administration experience. Walkthrough videos should make it possible to get the system running without expertise, but novice users may not be able to get maximum functionality and customisability from the system.
====Standards compliance====
DataStage automatically gathers metadata in RDF format. The system uses the [http://www.dcc.ac.uk/node/9385 BagIt] specification when transferring files to a permanent archive, which must be SWORD-2 compliant.
DataBank uses Dublin Core as its default metadata standard. The system is able to assign DOIs using the [http://www.dcc.ac.uk/node/9397 DataCite] API.
====Influence and take-up====
DataFlow is used in a number of settings at the University of Oxford; it is not in “production” use outside the project yet but the project is developing an active base of test users and interested parties, including:

* UK Data Archive (testing DataStage + Eprints)
* University of Hertfordshire and the Centre for Digital Music, Queen Mary University London (testing DataStage + DSpace)
* RoaDMap project, University of Leeds (testing DataStage and DataBank)
* YHMAN Shared Virtual Data Centre (interest in rolling out DataStage and DataBank on a 'community cloud' of eight universities in Yorkshire & Humber and comprises a cluster resource pool in existing data centres linked by a stretched long-haul network)
* Microsoft Research (interest in DataBank as archive to hold and publicise large datasets)
* A pool of research group leaders in the University of Oxford, who implemented ADMIRAL (a precursor to DataStage) and will upgrade to DataStage 1.0.

= User Experiences =

= Development Activity =
{{Infobox tool details
|ohloh_id=DataFlow
}}

Archivematica

2026-05-26T15:39:44Z

BertrandCaron: added BagIt as an output format

{{Infobox tool
|purpose=Archivematica is a digital preservation system that automates the process of preparing digital objects for ingest into a repository and an access system
|homepage=https://www.archivematica.org
|license=[http://www.gnu.org/licenses/agpl.html AGPL version 3]
|formats_in=PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies), BagIt
|function=File Format Migration, Preservation System
}}
= Description =
Archivematica is a digital preservation system that automates the process of preparing digital objects for ingest into a repository and an access system, ingesting them into archival storage and providing access to the archived material as well as uploading access copies to an access system. The process is monitored and controlled through a Web-based dashboard that co-ordinates a suite of micro-services. It relies on normalisation with preservation as the original object and comprehensive PREMIS metadata in METS.xml as its primary preservation technique.

Any content that can be placed in a directory can be ingested, including images, text files, office documents, publications, audiovisual files, databases and research datasets. Archivematica performs digital preservation actions such as identifier assignment, checksum generation, virus scan, format identification and metadata extraction on all ingested objects. For certain types of files, specialized tools (such as ImageMagick for raster images, ffprobe and ffmpeg for AV files, Ghostscipt for PDF files, Inkscape for vector images, and bulk_extractor and sleuthkit for forensic disk images) are used for metadata extraction, format normalization and other preservation actions. New tools, rules and commands for preservation actions can be added to the workflow using the Format Policy Registry (FPR) via the Preservation Planning tab in the web-based dashboard.

Archivematica does not include a web crawler, although it can ingest warc (Web ARChive format) files. Archivematica can also ingest email archives and forensic disk images.

==Provider==

This project is managed by [https://www.artefactual.com/ Artefactual Systems].

Artefactual Systems was founded in January 2000 as a digital preservation consulting company, and expanded into open-source software development starting in 2006. It began in collaboration with the UNESCO Memory of the World's [http://goo.gl/tlRHbk Subcommittee on Technology] and the [https://vancouver.ca/your-government/city-of-vancouver-archives.aspx City of Vancouver Archives], but continues active development along with its partners at the [http://diginit.library.ubc.ca/ University of British Columbia Library], the [http://rockarch.org/ Rockefeller Archive Center], [http://www.sfu.ca/archives/ Simon Fraser University Archives and Records Management], [http://library.bentley.edu/ Bentley Historical Library] and a number of other collaborators. The company now offers software development, technical support and hosting services, data migrations (from legacy systems into AtoM), training and consulting. The company currently has more than 90 hosting/technical support clients and at any given time has around 12- to 15 software development, data migration and consulting clients. The company has 20+ personnel, a diverse group which includes archivists and librarians, software developers, systems administrators, project managers and technical services managers.

== Platform and interoperability ==

=== Installation ===

Archivematica may be installed directly on a Linux system. The following operating systems are supported:

* Ubuntu 14.04 64-bit Server Edition
* Ubuntu 16.04 64-bit Server Edition (beta)
* CentOS 7 64-bit

Other Linux distributions should work, but will require customization of these installation instructions.

Archivematica has a long list of software it depends on. They are installed when Archivematica is installed on a system.

Note that it is possible to install some of the components on separate machines in order to improve performance, such as:

* MySQL
* Gearman
* Elasticsearch (optional as of Archivematica 1.7)

=== Interoperability ===

Archivematica has out-of-the-box integrations with AtoM (AccessToMemory), Dspace, ArchivesSpace and CONTENTdm. Configuration and workflow instructions are available in the online user manual. Archivematica can also be used with Islandora, Dataverse and Samvera, but some customization may be required for setup.

=== Storage ===
Types of storage systems used with Archivematica include local file-based systems; cloud-based storage such as Amazon S3, Microsoft Azure and OpenStack Swift; and specialized storage tools and services such as LOCKSS, DuraCloud and Arkivum. Artefactual in partnership with DuraSpace offers [https://duraspace.org/archivesdirect/ ArchivesDirect] as an Archivematica and DuraCloud hosting option.

Users can ingest content manually via the transfer tab or can use automation tools to automatically ingest content from designated source locations such as a folder on a network drive or from systems such as DSpace, Islandora and Dataverse.

=== Access ===

Dissemination Information Packages to access systems such as AtoM or ArchivesSpace, where rich metadata enhancement can be undertaken for discoverability and access purposes.

=== Functional notes ===

Archivematica uses a micro-services approach, which means it acts as a wrapper for many task-specific applications such as the BagIt library, Clam Anti-Virus, DigiKam, FFmpeg, FITS (File Information Tool Set), ImageMagick, Inkscape, OpenOffice.org, and 7-Zip.
The typical workflow is for the curator to assemble a transfer package in the filesystem: a script is provided for setting up the right folder structure or the structure can be assembled manually for some workflows, then digital objects are added to one folder and contextual information (submission documentation in the form of e.g. transfer forms, donation agreements) to another. The package is moved to an input folder 'watched' by the main Archivematica Web tool. Through the Web interface, the curator can decide to accept or reject the transfer. If the transfer is accepted, the tool performs an initial analysis – calculating checksums, assigning UUIDs, scanning for viruses, identifying formats, extracting metadata – and then offers to create a Submission Information Package (SIP); it is also possible to create one or more SIPs manually. Metadata (simple Dublin Core and PREMIS 2.2 rights/restrictions) can then be added to the SIP before it is ingested. At ingest, the curator can choose various routes such as Preservation (where the digital objects are normalised to archival formats and transformed into an Archival Information Package, or AIP), Access (where the digital objects are normalised to dissemination formats and transformed into a Dissemination Information Package, or DIP), repackaging without normalisation, or many combinations of the aforementioned. Further functions are provided for moving AIPs into archival storage and uploading DIPs to AtoM or another access portal. Workflows and decision points are configurable via preconfiguration settings in the administration tab of the web-based dashboard.

= Documentation, community, and support =
The online [https://www.archivematica.org/en/ documentation] for Archivematica includes a User and an Administrative Manual.

The [https://wiki.archivematica.org/Main_Page project wiki] provides, screencasts, requirements specifications (including use cases, activity diagrams, recognised significant properties of various media and media preservation plans) and a description of the technical architecture.

Community support is available through the [http://groups.google.com/group/archivematica Archivematica Discussion Group]. Several [https://wiki.archivematica.org/Community/Regional_User_Groups region-based user groups] exist.

[https://wiki.archivematica.org/Community/Camps Archivematica Camps] are intended to provide a space for anyone interested in or currently using Archivematica, to come together, learn about the platform and share their experiences.

Sample data for testing Archivematica is [https://github.com/artefactual/archivematica-sampledata available online] and when Archivematica is installed.

Artefactual Systems, Inc., the primary developer of Archivematica, also offers [https://www.artefactual.com/services/ support options].

Digital POWRR offers [http://www.sustainableheritagenetwork.org/system/files/atoms/file/Tutorial_for_Archivematica_POWRR_WarmSprings.pdf a How-to Tech Tutorial] (PDF).

Archivist Ethan Gates offers a presentation entitled [https://ethan-gates.com/files/Archivematica_Workshop_2017.pdf A Place Where You Process: An Introduction to Archivematica Workflows] (slides,PDF).

==Usability==

The majority of operations are accomplished through a Web-based graphical user interface.

Reports on the ease of installation and the robustness of the system are mixed but improving. Example experiences of installing Archivematica (note that current version is 1.7):
* [http://libraryblogs.is.ed.ac.uk/bitsandpieces/2016/01/13/archivematica-youre-the-one-that-i-want/ Edinburgh University] with version 1.3
* [http://digital-archiving.blogspot.co.uk/2012/09/installing-archivematica-and-running.html Jenny Mitcham] with version 0.9
* [http://larchivista.blogspot.co.uk/2011/04/installing-archivematica.html Bonnie Weddle] with version 0.7
* [http://e-records.chrisprom.com/evaluating-open-source-digital-preservation-systems-a-case-study-2/ Angela Jordan] with version 0.7

==Expertise required==

The system is easy to use, though as it draws heavily on the [http://www.dcc.ac.uk/resources/briefing-papers/introduction-curation/using-oais-curation OAIS Reference Model] some familiarity with that model is needed to understand the workflows Archivematica supports. When installing directly on a Linux desktop or server, even if it is deployed in a virtual machine, a little technical expertise is required (e.g. for setting up ports correctly).

====Influence and take-up====
Archivematica is used by at least [https://www.archivematica.org/wiki/Community 30 organisations].

=Standards compliance=

The functionality of Archivematica is clearly based on that defined by the OAIS Reference Model. The Archival Information Packages generated by the system use the [[BagIt]] packaging format, in conjunction with a METS packaging manifest incorporating PREMIS metadata.

= Development Activity =

All development activity is visible on GitHub: http://github.com/artefactual/archivematica/commits

Documentation and information on the latest Archivematica release is available here: https://www.archivematica.org/en/docs/latest
{{Infobox tool details}}

DataStage

2026-05-26T15:38:31Z

BertrandCaron: added BagIt as an output format

{{Infobox tool
|purpose=DataStage is a flexible data storage system that provides controlled access, secure backup, and the ability to transfer selected files to a more permanent archiving facility.
|homepage=http://www.dataflow.ox.ac.uk/index.php/datastage
|formats_out=BagIt
|function=Active Data Storage, Managing Active Research Data
|content=Research Data
}}
= Description =
[http://www.dataflow.ox.ac.uk/index.php/datastage DataStage] is a flexible data storage system that provides controlled access, secure backup, and the ability to transfer selected files to a more permanent archiving facility. Designed for research groups, the system appears as a mapped drive on the end-user’s computer.
====Provider====
Oxford University Bodleian Libraries, as part of the wider DataFlow project
====Licensing and cost====
Free – [http://www.opensource.org/licenses/MIT open source MIT license]
====Development activity====
DataStage version 0.3 was released in May 2012.
While the DataFlow project will end in May 2012, the Bodlean Library has decided to trial the software for its own use and will support development until at least May 2013.
====Platform and interoperability====
DataStage is designed for the Ubuntu Linux 11.10 Oneiric Ocelot operating system, and the Virtual Machines work with VMWare Fusion 4.x. While it is intended to integrate with [http://www.dcc.ac.uk/resource/external/databank DataBank], the software offers an API so that it can package datasets for submission to any SWORD-2-compliant repository.
End-users can connect to DataStage through a web interface or as a mapped drive on Mac, Linux or Windows machines.
====Functional notes====
The software gives three levels of password-controlled access: a "private" area only accessible to the file owner and the group leader, a "shared" area giving read-only access to the group, and a "collaborative" area giving read- and write-access. The administrator can invite outside collaborators into the group, pinpointing their level of access. Users can also access and annotate the files through a web interface.
DataStage can be deployed on a local server, or on an institutional or commercial cloud; users can also dynamically invoke additional cloud storage as required. Users can integrate the system into existing backup procedures. The repository interface also allows researchers to push selected files into a more permanent archive facility.
While users can add free-text metadata via the web interface, DataStage also automatically captures a number of general file attributes: date uploaded; file name; last modified; type; owner; location; and size.
====Documentation and user support====
Documentation is available in the form of an [http://http://www.dataflow.ox.ac.uk/index.php/datastage/users/test-users Information for Test Users] page and the DataStage [https://github.com/dataflow/DataStage/wiki documentation wiki], which is very much a work in progress, but does offer information for installation and use. The project has an active mailing list at [http://dataflow-devel@googlegroups.com http://dataflow-devel@googlegroups.com] and links to a JIRA [http://dataflow-jira.bodleian.ox.ac.uk/jira/secure/IssueNavigator.jspa issue tracker]. Installation instructions are included in a README file, which comes zipped with the installation package.
The project is creating video walkthroughs for installation, configuration and use of DataStage, to be available from the website by the end of May 2012.
====Usability====
End-users interact with the system either as a mapped drive on their computer, implicitly integrating with their operating system’s current navigation structure, or through a web interface.
====Expertise required====
Installation and configuration would greatly benefit from knowledge of system administration, and use of the Linux command line. Walkthrough videos should make it possible to get DataStage running without expertise, but novice users may not be able to get maximum functionality and customisability from the system.
====Standards compliance====
Metadata automatically gathered by the system is in RDF format.
The system uses the [[BagIt]] specification when transferring files to a permanent archive, which must be SWORD-2 compliant.

====Influence and take-up====
DataStage is used at the Oxford Bodleian Libraries; information about wider use is unavailable.

= User Experiences =

= Development Activity =
{{Infobox tool details
|ohloh_id=DataStage
}}

DART (Digital Archivist's Resource Tool)

2026-05-26T15:37:29Z

BertrandCaron: added BagIt as an output format

{{Infobox tool
|purpose=Provides both a GUI and a command-line interface for packaging files and uploading them to remote repositories.
|homepage=https://aptrust.github.io/dart-docs/
|license=TBC
|platforms=Windows/Mac/Linux
|formats_out=BagIt
|function=File Management, Fixity, Storage, Transfer
|content=Binary Data
}}
== Description ==


<blockquote>
DART is the Digital Archivist's Resource Tool. Its primary purpose is to package digital materials and send them off to long-term preservation storage. DART's initial release focuses on packaging materials in [[BagIt]] format and uploading them to S3 buckets for ingest in APTrust. DART can be extended through plugins to produce other packaging formats and to communicated via additional network protocols.

DART runs in both graphical and command-line modes on Windows, Mac, and Linux.
</blockquote>

== User Experiences ==


== Development Activity ==


{{Infobox tool details}}

ANTS (Archives Network Transfer System)

2026-05-26T15:35:35Z

BertrandCaron: added BagIt as an output format

{{Infobox tool
|purpose=ANTS runs on a Windows desktop and is designed to package digital records with contextual metadata and transfer them to an institutional archives.
|homepage=https://github.com/UAlbanyArchives/ants
|formats_out=BagIt
|function=Transfer
}}
== Description ==

Developped by the University of Albany Archives, ANTS was designed for records creators to describe, package, and transfer unstructured files. It uses the [[BagIt]] specfication, and has been tested on Windows XP SP2, 7 and 10.

== User Experiences ==


== Development Activity ==


{{Infobox tool details}}

Exactly

2026-05-26T15:34:15Z

BertrandCaron: added BagIt as an output format

{{Infobox tool
|image=Exactly-50-small-300x279.png
|purpose=Packs data in BagIt bags and transfers them to/from remote location via FTP, SFTP
|homepage=https://www.weareavp.com/products/exactly/
|tool_status=Gone
|license=Apache License 2.0
|platforms=Mac and Windows
|formats_in=BagIt
|function=Transfer
}}




== Description ==

Exactly allows users to pack local data into [[BagIt]] bags and to transfer them to remote locations via FTP or SFTP protocol. While creating the bags, the users can choose to add user-info metadata, which is added to the bag-info file. The UI offers reserved fields, such as source-organization, organization-address, etc., per default, but also supports non-bagit fields to be added. Metadata profiles, (S)FTP parameters, email preferences, and other settings can be stored in preset settings files for usage in client installations.

During bag creation, the user has the option to choose whether the bag should be zipped or not.

The tool integrates with desktop-based file sharing workflows such as Dropbox or Google Transfer and is designed to assist data producers in easy data transfer to archiving institutions.

==== Provider ====
[https://www.weareavp.com/ AVP]

==== Licensing and cost ====
[https://www.apache.org/licenses/LICENSE-2.0 Apache License 2.0] – free.

== User Experiences ==

Exactly Users Google Group: https://groups.google.com/forum/#!forum/exactly-users

Exactly webinar: https://vimeo.com/200403270

== Development Activity ==


Exactly isn't being actively developed anymore: https://groups.google.com/g/exactly-users/c/vNfPuTN2lVg/m/fy7ZWI_-BAAJ

Exactly on Open Hub: https://www.openhub.net/p/exactly (no activity)
{{Infobox tool details
|ohloh_id=exactly
|mailing_lists=https://groups.google.com/forum/#!forum/exactly-users
|releases_rss=https://github.com/WeAreAVP/uk-exactly/releases.atom
}}

Bagger

2026-05-26T15:32:59Z

BertrandCaron: added BagIt as an input/output format

{{Infobox tool
|purpose=GUI application to facilitate the creation and verification of [[BagIt]] bags.
|homepage=https://github.com/LibraryOfCongress/bagger
|license=Open License, but relies on several Apache based and GNU licensed components.
|formats_in=BagIt
|formats_out=BagIt
|function=Fixity, Transfer
}}
= Description =
The [[BagIt]] specification is a hierarchical file packaging format for the creation of standardised digital containers called 'bags,' which are used for storing and transferring digital content. Derived from work by the Library of Congress and the California Digital Library, a bag consists of a ‘payload’ - the digital content - and ‘tags' - metadata files to document the storage and transfer of the bag. There are a number of [http://sourceforge.net/projects/loc-xferutils/ Bagit-specific tools] to ease bag creation, including the BagIt Library, a Java-based software library to support the creation, manipulation, and validation of bags. For those less comfortable with command-line interface, the Bagger application provides a graphical user interface to the BagIt Library.
====Provider====
The United States Library of Congress, and the National Digital Information Infrastructure and Preservation Program (NDIIPP)
====Licensing and cost====
[http://www.linfo.org/bsdlicense.html BSD License] - free.  The BagIt Library is public domain.
====Development activity====
Bagger 2.1.2 was released in February 2012. BagIt Library 4.1 was released in January 2012.
The Library of Congress website implies ongoing development of the Transfer Utilities. 
====Platform and interoperability====
Both the BagIt Library and Bagger require Java 6.
====Functional notes====
Bags contain at minimum three elements: a ‘payload’ and at least two ‘tags.’ The payload consists of the content being preserved. The first tag is a manifest itemising the files making up the content along with their checksums; the second is a bagit.txt file identifying the container as a bag and giving the version of the specification used and the character encoding of the tags.  The specification additionally allows for several optional tags.  
====Documentation and user support====
Documentation is extremely sparse, primarily consisting of README files detailing release notes. The [http://www.digitalpreservation.gov/documents/bagitspec.pdf BagIt specification itself ]can be found through the Library of Congress website.
It appears that the main user support consists of a mailing list hosted by Sourceforge; however, the list archive only shows 11 posts for 2011.
====Usability====
The BagIt Library uses a command-line interface, while Bagger provides a graphical user interface. No installation is required; the tools can simply be downloaded and run, although it may not be immediately clear to users how to do so.
====Expertise required====
BagIt is designed to create a common language for users exchanging digital materials, essentially negating the need for expertise about others’ protocols. However, for configuration, familiarity with one’s own repository’s technical protocols is essential.
====Standards compliance====
The BagIt specification is an Internet Engineering Task Force (IETF) internet draft.
====Influence and take-up====
The BagIt specification has become widely accepted in the preservation community, and is used by the Library of Congress, Chronopolis, and The Stanford Digital Repository, among others. The Transfer Utilities have been downloaded nearly 4000 times from Sourceforge.

= User Experiences =

= Development Activity =
=== Activity Feed===
Link to any RSS feed that is updated when issue or code updates occur, if any, e.g:
<rss max=7>https://github.com/LibraryOfCongress/bagger/commits/master.atom</rss>

=== Release Feed ===
<rss max=3>https://github.com/LibraryOfCongress/bagger/releases.atom</rss>
{{Infobox tool details
|ohloh_id=Bagger
}}

RODA-In

2026-05-26T15:31:06Z

BertrandCaron: added BagIt as an output format

{{Infobox tool
|purpose=The tool creates SIPs from files and folders available on the local file system.
|homepage=https://rodain.roda-community.org/
|sourcecode=https://github.com/keeps/roda-in
|license=LGPL-3.0 license
|platforms=Windows, macOS, Linux
|formats_out=BagIt
|function=Appraisal, Fixity, Transfer
}}
== Description ==
RODA-in is a tool specially designed for producers and archivists to create Submission Information Packages (SIP) ready to be submitted to an Open Archival Information System (OAIS).

The tool includes features such as:
* Create, load and edit classification schemas
* Automatic association of files/folders to SIP
* Automatic association of metadata to SIP
* Definition of metadata templates
* Support for various metadata formats (EAD, DC, etc.)
* Creation of SIP of unlimited size
* Creation of SIP in various formats: BagIt and E-ARK

RODA-in supports several Submission Information Package formats. At the moment we have included support for:
* BagIt, a hierarchical file packaging format for storage and transfer of arbitrary digital content. A “bag” has just enough structure to enclose descriptive “tags” and a “payload” but does not require knowledge of the payload’s internal semantics. This BagIt format should be suitable for disk-based or network-based storage and transfer. BagIt is widely used in the practice of digital preservation. The specification of BagIt can be found here.
* E-ARK SIP format, a Submission Information Package format developed by the EU funded E-ARK Project. The specification can be found here

== Development Activity ==
{{Infobox tool details
|releases_rss=https://github.com/keeps/roda-in/releases.atom
}}

BagIt Transfer Utilities

2026-05-26T15:30:00Z

BertrandCaron: added BagIt as input format

{{Infobox tool
|purpose=BagIt transfer Utilities are a collection of tools developed for the purpose of validation and transfer of bags.
|homepage=http://sourceforge.net/projects/loc-xferutils/
|license=BSD License
|platforms=UNIX
|formats_in=BagIt
|function=File Copy, Fixity
}}
= Description =
[[BagIt]] transfer Utilities are a collection of tools developed for the purpose of validation and transfer of bags. Developed by Library of Congress. Written in Python and UNIX shell.

= User Experiences =

= Development Activity =
{{Infobox tool details
|ohloh_id=BagIt Transfer Utilities
}}

BIL (BagIt Library)

2026-05-26T15:28:37Z

BertrandCaron: added BagIt as input/output format

{{Infobox tool
|purpose=BagIt Library is a Java software library that supports the creation, manipulation and validation of bags.
|homepage=http://sourceforge.net/projects/loc-xferutils/
|license=Public domain
|formats_in=BagIt
|formats_out=BagIt
|function=File Copy, Fixity
}}
= Description =
[[BagIt]] Library is a Java software library that supports the creation, manipulation and validation of bags. Developed by Library of Congress. Written in Java. The BagIt specification is standardised here https://www.rfc-editor.org/info/rfc8493

= User Experiences =

= Development Activity =
{{Infobox tool details
|ohloh_id=BagIt Library (BIL)
}}

Archive::BagIt

2026-05-26T15:27:49Z

BertrandCaron: also added BagIt as input format

{{Infobox tool
|purpose=BagIt API for Perl
|homepage=https://metacpan.org/pod/Archive::BagIt
|license=Perl5 Attribution License
|platforms=UNIX, Windows, see http://matrix.cpantesters.org/?dist=Archive-BagIt+0.066
|formats_in=BagIt
|formats_out=BagIt
|function=File Copy, Fixity
}}
= Description =
Archive::BagIt is a Perl5 API to create, manipulate and verify [[BagIt]] containers. It supports [[RFC8493]] (https://datatracker.ietf.org/doc/rfc8493/?include_text=1) and therefore Bags of version 1.0. It also allows to read and convert v0.97 based Bags.

There also command line utilities to create or verify Bags. See POD-documentation of Archive::BagIt::Base for details.

= User Experiences =

= Development Activity =
{{Infobox tool details
|releases_rss=https://metacpan.org/feed/distribution/Archive-BagIt
|issues_rss=https://rt.cpan.org/Public/Dist/Display.html?Name=Archive-BagIt
}}

EPADD

2026-05-26T15:26:44Z

BertrandCaron:

{{Infobox tool
|image=Epadd_logo_orig.png
|purpose=ePADD is a software package developed by Stanford University's Special Collections & University Archives that supports archival processes around the appraisal, ingest, processing, discovery, and delivery of email archives.
|homepage=https://library.stanford.edu/projects/epadd
|license=Apache 2.0
|platforms=Java
|Wikidata ID=Q59652265
|formats_in=MBOX
|formats_out=PREMIS (Preservation Metadata Implementation Strategies), BagIt
|function=Access, Appraisal, Content Profiling, Metadata Extraction, Metadata Processing
|content=Email
}}




== Description ==

From the [https://github.com/ePADD/epadd project Github page]:
"ePADD is a software package developed by Stanford University's Special Collections & University Archives that supports archival processes around the appraisal, ingest, processing, discovery, and delivery of email archives.

The software is comprised of four modules:

* '''Appraisal:''' Allows donors, dealers, and curators to easily gather and review email archives prior to transferring those files to an archival repository.

* '''Processing:''' Provides archivists with the means to arrange and describe email archives.

* '''Discovery:''' Provides the tools for repositories to remotely share a redacted view of their email archives with users through a web server discovery environment. (Note that this module is downloaded separately).

* '''Delivery:''' Enables archival repositories to provide moderated full-text access to unrestricted email archives within a reading room environment."

From the [https://library.stanford.edu/projects/epadd/ Project page]:

'''ePADD Technical Information'''

ePADD is written in Java and Javascript and powered by Apache Tomcat (v7.0) using Java EE Servlet API (v3.x) and Java Mail (v1.4.2). Text and metadata extraction, indexing and retrieval is performed by Apache Lucene (v4.7) and Apache Tika (v1.8). Charting and visualization is supported using the D3-based reusable chart library (v0.4.10). Oracle's Java Application Bundler and Launch4J are used for packaging on Mac and Windows platforms respectively. Other Java libraries from Apache (Lang, commons, CLI, IO, logging, etc.) are also used. JSON formatting is performed with the libraries org.json and Gson.

ePADD has implemented its own natural language processing (NLP) toolkit which is used for named entity extraction, disambiguation and other tasks. This toolkit supplants the Apache OpenNLP used in earlier beta versions of the ePADD software. We continue to use Muse as an internal library within ePADD. However, the Apache OpenNLP proved insufficient for our needs (at least for name recognition), and after various rounds of customization, we built our own named entity recognizer. This toolkit uses external datasets such as Wikipedia/DBpedia, Freebase, Geonames, OCLC FAST and LC Subject Headings/LC Name Authority File.

The project is developed with IDEs like IntelliJ Idea and Eclipse, built with Apache Maven, Ant, and custom shell scripts, and tracked using Git for source control and issue tracking. The ePADD software client is browser-based and compatible with Chrome and Firefox. It is optimized for Windows 7 SP1/10, OSX 10.12/10.13, and Ubuntu 16.04 machines, using Java 8.

== User Experiences ==

* On migrating from different email formats before ingest to ePADD https://groups.google.com/forum/#!topic/digital-curation/srt-oIVwAGU
* [https://twitter.com/e_padd?lang=en ePADD on Twitter]
* [http://library.stanford.edu/blogs/special-collections-unbound/2018/07/epadd-60-beta-released ePADD 6.0 beta released!]
* [https://docs.google.com/document/d/1CVIpWK5FNs5KWVHgvtWTa7u0tZjUrFrBHq6_6ZJVfEA ePADD User Guide]
* [https://docs.google.com/document/d/10U9Hxh9MS9C9bS8M7uYuXk5m7EBFpgd0yiwCcOSM6D ePADD Shared Discovery Module Website Collection Contributor Guide]
* [https://library.stanford.edu/projects/epadd/presentations-publications Full list of presentations and publications]

== Development Activity ==

All development activity is visible on GitHub: http://github.com/ePADD/epadd/commits

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

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/ePADD/epadd/commits/master.atom</rss>
{{Infobox tool details
|ohloh_id=epadd
}}

BagIt

2026-05-26T15:25:31Z

BertrandCaron: Created format

{{Infobox format
|Wikidata ID=Q4841355
|File formats wiki ID=BagIt
}}
BagIt is a set of packaging conventions used to support the exchange and transfer of Information Packages including files, metadata and checksums.

Archive::BagIt

2026-05-26T15:21:17Z

BertrandCaron: added BagIt as an output format

{{Infobox tool
|purpose=BagIt API for Perl
|homepage=https://metacpan.org/pod/Archive::BagIt
|license=Perl5 Attribution License
|platforms=UNIX, Windows, see http://matrix.cpantesters.org/?dist=Archive-BagIt+0.066
|formats_out=BagIt
|function=File Copy, Fixity
}}
= Description =
Archive::BagIt is a Perl5 API to create, manipulate and verify [[BagIt]] containers. It supports [[RFC8493]] (https://datatracker.ietf.org/doc/rfc8493/?include_text=1) and therefore Bags of version 1.0. It also allows to read and convert v0.97 based Bags.

There also command line utilities to create or verify Bags. See POD-documentation of Archive::BagIt::Base for details.

= User Experiences =

= Development Activity =
{{Infobox tool details
|releases_rss=https://metacpan.org/feed/distribution/Archive-BagIt
|issues_rss=https://rt.cpan.org/Public/Dist/Display.html?Name=Archive-BagIt
}}

7-Zip

2026-05-26T15:02:35Z

BertrandCaron: removed the function "Transfer"

{{Infobox tool
|purpose=7-Zip is a file archiver with a high compression ratio, and encryption and fixity check capabilities
|homepage=http://www.7-zip.org/
|license=7-Zip is open source software [http://www.7-zip.org/]. Most of the source code is under the GNU LPGL license [http://www.7-zip.org/]. You can use 7-Zip on any computer, including a computer in a commercial organization [http://www.7-zip.org/]. You don't need to register or pay for 7-zip [http://www.7-zip.org/].
|platforms=7-zip can be utilized on multiple platforms including Windows 7, Vista, XP, 2008, 2003, 2000, NT, ME, and 98 [http://www.sourceforge.net/projects/sevenzip/editorial/?source=psp].
|function=Fixity, Rendering
|content=Container, Disk Image
}}

[[Category:File Compression]]
[[Category:Encryption]]

= Description =
7-Zip is a file archiver with a high compression ratio [http://www.sourceforge.net/projects/sevenzip/editorial/?source=psp]. You can use 7-Zip on any computer, including a computer in a commercial organization [http://www.sourceforge.net/projects/sevenzip/editorial/?source=psp]. You don't need to register or pay for 7-zip [http://www.sourceforge.net/projects/sevenzip/editorial/?source=psp]. 7-Zip works for Windows 7, Vista, XP, 2008, 2003, 2000, NT, ME, and 98 [http://www.sourceforge.net/projects/sevenzip/editorial/?source=psp].

Most of the source code is under the GNU LGPL license [http://www.sourceforge.net/projects/sevenzip/editorial/?source=psp].

The unRar code is under a mixed license with GNU LGPL + unRAR restrictions [http://www.sourceforge.net/projects/sevenzip/editorial/?source=psp]. Check the license for details [http://www.sourceforge.net/projects/sevenzip/editorial/?source=psp].

=== Platform ===
7-zip can be utilized on multiple platforms including Windows 7, Vista, XP, 2008, 2003, 2000, NT, ME, and 98 [http://www.sourceforge.net/projects/sevenzip/editorial/?source=psp]

= User Experiences =
7-zip can be used to open an ISO Image File[http://en.wikipedia.org/wiki/ISO_image].

In order to secure a transfer along untrusted lines, 7-Zip can encrypt containers with AES-256.

For securing fixity: 7-Zip records checksums on compression and verifies them on decompression.

7-Zip can handle containers larger than 2 GigaByte (unlike tools for the genuine ZIP format).

And there is a port of the command line version to Linux/Unix [http://www.sourceforge.net/projects/sevenzip/editorial/?source=psp].

7-Zip has good handling of date-modified file system values which otherwise can be reset to date of extraction when using tools such as the native Windows extraction tool

= Development Activity =
{{Infobox tool details
|ohloh_id=sevenzip
}}

Wish list of tools to add to COPTR

2026-05-13T15:04:03Z

BertrandCaron: Added premis-generator

This is a scratch space for adding lists of tools that should be added to COPTR. Please add your wish list of tools below. If anyone subsequently adds tool entries for tools listed here, please indicate that by adding strike tags around them on this page!

==Tools to add==
*https://www.logipole.com/konvertor-en.htm
*http://www.chumba.ch/chumbalum-soft/ms3d/index.html
*https://www.embulk.org/
*ISO16363 PTAB http://www.iso16363.org/
*Guymager https://www.kali.org/tools/guymager/
*Bulk Extractor https://www.kali.org/tools/bulk-extractor/
*SoX http://sox.sourceforge.net/
*IFIscripts https://ifiscripts.readthedocs.io/en/latest/index.html
*Transformenator https://github.com/RetroFloppy/transformenator
*Document Liberation Project https://www.documentliberation.org/projects/
*https://github.com/kieranjol/IFIscripts
*https://formats.kaitai.io/
* [https://jacksum.net/en/index.html Jacksum]
* [https://github.com/rochester-rcl/premis-generator premis-generator]

Some great data manipulation tools in this thread: https://twitter.com/SarahRBarsness/status/1452684578905337866?s=20
*https://pandas.pydata.org/
*https://www.tableau.com/products/prep
*https://openrefine.org/

(note that the 4 tools below are referenced in this workflow. After they have been added, the links in the workflow should be updated so they point to the new tool entries) https://coptr.digipres.org/index.php/Workflow:Flashback_project_-_optical_media_imaging_workflow
*Toc2Cue
*BChunk
*GenISOImage
*Sophos AV Scan

(note that the 4 tools below are referenced in this workflow. After they have been added, the links in the workflow should be updated so they point to the new tool entries) https://coptr.digipres.org/index.php/Workflow:Workflow_for_ingesting_digitized_books_into_a_digital_archive
*DocuTeam Feeder
*cURL
*Saxon
*ClamAV

https://github.com/mkernik/geodct

https://github.com/VERT-sh/VERT

https://www.vanderplanki.com/

SER Rendition Server

Callas PDF/A Pilot

apryse (formerly PDFtron)

https://auto-archiver.readthedocs.io/en/latest/installation/faq.html

==Tools that are obsolete==
*Khtml2png
*ArchiveFacebook
*Pearl Crescent replaced with https://addons.mozilla.org/en-GB/firefox/addon/pagesaver-we/
*Spadix Software is actually Rafabot and looks old
*Storytracker ?
*WAS (Web Archiving Service) - obsolete
*WERA (Web ARchive Access)
*Curate.Us
*Find It! Keep It!
*Heritrix plug-in for rich media capture
*WAXToolbar

Talk:FTK (Forensic Toolkit)

2026-02-05T17:08:35Z

BertrandCaron:

I suggest that a separate page for FTK Imager is created as these are totally different tools. Happy to create one!

: I am in favour of that, yes! In addition, I think that there are differences in the platforms - FTK is only supported by Windows, while there is a Linux version for FTK Imager --[[User:BertrandCaron|BertrandCaron]] ([[User talk:BertrandCaron|talk]]) 15:52, 5 February 2026 (UTC)

MuPDF

2026-02-05T16:58:01Z

BertrandCaron:

{{Infobox tool
|image=960px-MuPDF.svg.png
|purpose=Free and open source rendering engine for PDFs, EPUBs and XPS documents.
|homepage=https://mupdf.com/
|tool_status=Maintained
|sourcecode=https://github.com/ArtifexSoftware/mupdf
|license=AGPL-3.0 license
|cost=n/a
|platforms=Windows, macOS, GNU/Linux
|language=English
|Wikidata ID=Q6930567
|formats_in=EPUB, PDF, XPS
|formats_out=PDF, HTML
|function=File Format Migration, Rendering, Repair
|content=Document
}}
{{Infobox tool details}}
== Description ==
MuPDF is a free and open source rendering engine for PDFs, EPUBs and XPS documents. It can perform other tasks, like cleaning the offsets of a cross-reference table in a PDF with the following command-line:

mutool clean myPdf

== User Experiences ==

* Caron, Bertrand. ‘“Validation OK” They Said: Fixing the Rendering of a So-Called Valid PDF’. Open Preservation Foundation, 21 May 2025. https://openpreservation.org/blogs/validation-ok-they-said-fixing-the-rendering-of-a-so-called-valid-pdf/.
* Knijff, Johan van der. ‘PDF Processing and Analysis with Open-Source Tools’. Bitsgalore, 6 September 2021. https://www.bitsgalore.org/2021/09/06/pdf-processing-and-analysis-with-open-source-tools.

MuPDF

2026-02-05T16:54:58Z

BertrandCaron: Creation of the page.

File:960px-MuPDF.svg.png

2026-02-05T16:37:40Z

BertrandCaron: The logo of the MuPDF tool

== Summary ==
The logo of the MuPDF tool

Pdfcpu

2026-02-05T16:32:13Z

BertrandCaron: /* User Experiences */

{{Infobox tool
|image=pdfcpuLogoSmall.png
|purpose=A Go library and command line tool for PDF processing incl. validation
|homepage=https://pdfcpu.io/
|license=Apache-2.0 License
|formats_in=PDF
|function=Metadata Extraction, Validation
|content=Document
}}
{{Infobox tool details}}
== Description ==

pdfcpu is a powerful Go library and command line tool that supports many PDF processing functions such as reading and writing the xref table, extracting images, fonts and embedded file attachments and encryption detection as well as decryption.
A full list of the command set is avaiable at:
https://pdfcpu.io/about/command_set

=== Validation ===
pdfcpu validates PDFs up to version 1.7. There are two different levels of validation, strict and relaxed, and the option to run validation in verbose mode which shows the output of the entire PDF syntax.

pdfcpu validate -mode strict this.pdf
validating(mode=strict) this.pdf ...
validation error (try -mode=relaxed): dict=type1FontDict required entry=FirstChar missing

pdfcpu validate -mode relaxed this.pdf
validating(mode=relaxed) this.pdf ...
validation ok

=== Metadata Extraction ===

Extraction of Metadata is possible in two ways. The argument ''info'' prints Information such as title, author, PDF producer, creation / modification data and some technical metadata such as encryption and permission information and whether the PDF is tagged, linearized or includes watermarks.
Sample output:

pdfcpu info this.pdf
PDF version: 1.6
Page count: 96
Page size: 21.00 x 29.70 cm
.........................................
Title: This is just a test
Author: Digiman
Subject:
PDF Producer: Adobe PDF Library 15.0
Content creator: Adobe InDesign CC 207 (Macintosh)
Creation date: D:20190912181416+02'00'
Modification date: D:20190918120753+02'00'
Keywords: key1
key2
..........................................
Tagged: Yes
Hybrid: No
Linearized: No
Using XRef streams: Yes
Using object streams: Yes
Watermarks: No
..........................................
Encrypted: No
Permissions: Full access

The second option is to extract any embedded metadata via the extract -mode meta flags. This creates txt files with the extracted metadata entries in a specified directory.
Sample output:

pdfcpu extract -mode meta this.pdf mdout
extracting metadata from this.pdf into mdout/ ...
writing mdout\this_Metadata_XObject_6499_6500.txt
writing mdout\this_Metadata_unknown_401_33.txt
writing mdout\this_Metadata_XObject_292_289.txt
writing mdout\this_Metadata_Catalog_6455_385.txt
writing mdout\this_Metadata_XObject_291_290.txt
writing mdout\this_Metadata_unknown_6491_6475.txt

== User Experiences ==

* Caron, Bertrand. ‘“Validation OK” They Said: Fixing the Rendering of a So-Called Valid PDF’. Open Preservation Foundation, 21 May 2025. https://openpreservation.org/blogs/validation-ok-they-said-fixing-the-rendering-of-a-so-called-valid-pdf/.
* Lindlar, Micky. ‘A Date with PDF-HUL-133 “Improperly Formed Date”’. Open Preservation Foundation, 13 May 2024. https://openpreservation.org/blogs/a-date-with-pdf-hul-133-improperly-formed-date/.
* Lindlar, Micky. ‘Destination Null: One of the Many Causes of PDF-Hul 122’. Open Preservation Foundation, 21 January 2024. https://openpreservation.org/blogs/destination-null-one-of-the-many-cases-of-pdf-hul-122/.
* Lindlar, Micky. ‘Tabs Keys in PDF Page Objects – What Are They and Should I Care?’ Open Preservation Foundation, 16 May 2023. https://openpreservation.org/blogs/tabs-keys-in-pdf-page-objects-what-are-they-and-should-i-care/.
* Lindlar, Micky. ‘Trouble-Shooting PDF Validation Errors - a Case of PDF-HUL-38’. Open Preservation Foundation, 27 November 2022. https://openpreservation.org/blogs/trouble-shooting-pdf-validation-errors-a-case-of-pdf-hul-38/.

== Development Activity ==

pdfcpu has an active user and developer community. All activity can be viewed via the github repo:
[https://github.com/pdfcpu/pdfcpu https://github.com/pdfcpu/pdfcpu]

Qpdf

2026-02-05T16:25:43Z

BertrandCaron: /* User Experiences */

{{Infobox tool
|purpose=QPDF is a command-line program that does structural, content-preserving transformations on PDF files
|homepage=http://qpdf.sourceforge.net/
|license=Artistic License 2.0
|platforms=Windows, Linux
|function=Metadata Extraction, Decryption
|content=Document
}}
{{Infobox tool details
|ohloh_id=qpdf
}}
== Description ==

Description from the project website:
<blockquote>
QPDF is a command-line program that does structural, content-preserving transformations on PDF files. (...) It also provides many useful capabilities to developers of PDF-producing software or for people who just want to look at the innards of a PDF file to learn more about how they work.
</blockquote>

== User Experiences ==

* Caron, Bertrand. ‘“Validation OK” They Said: Fixing the Rendering of a So-Called Valid PDF’. Open Preservation Foundation (blog), 21 May 2025. https://openpreservation.org/blogs/validation-ok-they-said-fixing-the-rendering-of-a-so-called-valid-pdf/.
* Knijff, Johan van der. ‘Why PDF/A Validation Matters, Even If You Don’t Have PDF/A’. Open Preservation Foundation, 7 July 2015. https://openpreservation.org/blogs/why-pdfa-validation-matters-even-if-you-dont-have-pdfa/.
* Lindlar, Micky. ‘Trouble-Shooting PDF Validation Errors - a Case of PDF-HUL-38’. Open Preservation Foundation, 27 November 2022. https://openpreservation.org/blogs/trouble-shooting-pdf-validation-errors-a-case-of-pdf-hul-38/.
* Lindlar, Micky. ‘Destination Null: One of the Many Causes of PDF-Hul 122’. Open Preservation Foundation, 21 January 2024. https://openpreservation.org/blogs/destination-null-one-of-the-many-cases-of-pdf-hul-122/.

== Development Activity ==

Qpdf

2026-02-05T16:21:16Z

BertrandCaron: /* User Experiences */

{{Infobox tool
|purpose=QPDF is a command-line program that does structural, content-preserving transformations on PDF files
|homepage=http://qpdf.sourceforge.net/
|license=Artistic License 2.0
|platforms=Windows, Linux
|function=Metadata Extraction, Decryption
|content=Document
}}
{{Infobox tool details
|ohloh_id=qpdf
}}
== Description ==

Description from the project website:
<blockquote>
QPDF is a command-line program that does structural, content-preserving transformations on PDF files. (...) It also provides many useful capabilities to developers of PDF-producing software or for people who just want to look at the innards of a PDF file to learn more about how they work.
</blockquote>

== User Experiences ==

* Caron, Bertrand. ‘“Validation OK” They Said: Fixing the Rendering of a So-Called Valid PDF’. Open Preservation Foundation (blog), 21 May 2025. https://openpreservation.org/blogs/validation-ok-they-said-fixing-the-rendering-of-a-so-called-valid-pdf/.
* Lindlar, Micky. ‘Trouble-Shooting PDF Validation Errors - a Case of PDF-HUL-38’. Open Preservation Foundation, 27 November 2022. https://openpreservation.org/blogs/trouble-shooting-pdf-validation-errors-a-case-of-pdf-hul-38/.
* Lindlar, Micky. ‘Destination Null: One of the Many Causes of PDF-Hul 122’. Open Preservation Foundation, 21 January 2024. https://openpreservation.org/blogs/destination-null-one-of-the-many-cases-of-pdf-hul-122/.

== Development Activity ==

Qpdf

2026-02-05T16:16:12Z

BertrandCaron: /* User Experiences */

{{Infobox tool
|purpose=QPDF is a command-line program that does structural, content-preserving transformations on PDF files
|homepage=http://qpdf.sourceforge.net/
|license=Artistic License 2.0
|platforms=Windows, Linux
|function=Metadata Extraction, Decryption
|content=Document
}}
{{Infobox tool details
|ohloh_id=qpdf
}}
== Description ==

Description from the project website:
<blockquote>
QPDF is a command-line program that does structural, content-preserving transformations on PDF files. (...) It also provides many useful capabilities to developers of PDF-producing software or for people who just want to look at the innards of a PDF file to learn more about how they work.
</blockquote>

== User Experiences ==

Caron, Bertrand. ‘“Validation OK” They Said: Fixing the Rendering of a So-Called Valid PDF’. Open Preservation Foundation (blog), 21 May 2025. https://openpreservation.org/blogs/validation-ok-they-said-fixing-the-rendering-of-a-so-called-valid-pdf/.

Lindlar, Micky. ‘Trouble-Shooting PDF Validation Errors - a Case of PDF-HUL-38’. Open Preservation Foundation, 27 November 2022. https://openpreservation.org/blogs/trouble-shooting-pdf-validation-errors-a-case-of-pdf-hul-38/.

== Development Activity ==

Wish list of tools to add to COPTR

2026-02-05T16:13:04Z

BertrandCaron: /* Tools to add */

This is a scratch space for adding lists of tools that should be added to COPTR. Please add your wish list of tools below. If anyone subsequently adds tool entries for tools listed here, please indicate that by adding strike tags around them on this page!

==Tools to add==
*https://www.logipole.com/konvertor-en.htm
*http://www.chumba.ch/chumbalum-soft/ms3d/index.html
*https://www.embulk.org/
*ISO16363 PTAB http://www.iso16363.org/
*Guymager https://www.kali.org/tools/guymager/
*Bulk Extractor https://www.kali.org/tools/bulk-extractor/
*SoX http://sox.sourceforge.net/
*IFIscripts https://ifiscripts.readthedocs.io/en/latest/index.html
*Transformenator https://github.com/RetroFloppy/transformenator
*Document Liberation Project https://www.documentliberation.org/projects/
*https://github.com/kieranjol/IFIscripts
*https://formats.kaitai.io/
* [https://jacksum.net/en/index.html Jacksum]

Some great data manipulation tools in this thread: https://twitter.com/SarahRBarsness/status/1452684578905337866?s=20
*https://pandas.pydata.org/
*https://www.tableau.com/products/prep
*https://openrefine.org/

(note that the 4 tools below are referenced in this workflow. After they have been added, the links in the workflow should be updated so they point to the new tool entries) https://coptr.digipres.org/index.php/Workflow:Flashback_project_-_optical_media_imaging_workflow
*Toc2Cue
*BChunk
*GenISOImage
*Sophos AV Scan

(note that the 4 tools below are referenced in this workflow. After they have been added, the links in the workflow should be updated so they point to the new tool entries) https://coptr.digipres.org/index.php/Workflow:Workflow_for_ingesting_digitized_books_into_a_digital_archive
*DocuTeam Feeder
*cURL
*Saxon
*ClamAV

==Tools that are obsolete==
*Khtml2png
*ArchiveFacebook
*Pearl Crescent replaced with https://addons.mozilla.org/en-GB/firefox/addon/pagesaver-we/
*Spadix Software is actually Rafabot and looks old
*Storytracker ?
*WAS (Web Archiving Service) - obsolete
*WERA (Web ARchive Access)
*Curate.Us
*Find It! Keep It!
*Heritrix plug-in for rich media capture
*WAXToolbar

Talk:FTK (Forensic Toolkit)

2026-02-05T15:53:18Z

BertrandCaron:

I suggest that a separate page for FTK Imager is created as these are totally different tools. Happy to create one!

: I am in favour of that, yes! --[[User:BertrandCaron|BertrandCaron]] ([[User talk:BertrandCaron|talk]]) 15:52, 5 February 2026 (UTC)

ODF Validator

2025-12-04T09:01:47Z

BertrandCaron: Updated URLs

{{Infobox tool
|purpose=ODF Validator is a tool that validates OpenDocument files and checks them for certain conformance criteria.
|homepage=https://odftoolkit.org/conformance/ODFValidator.html
|license=Apache License, Version 2.0
|function=Validation, Metadata Extraction
|content=Document
}}
{{Infobox tool details
|ohloh_id=odftoolkit
}}
== Description ==
ODF Validator is a tool that validates OpenDocument files and checks them for certain conformance criteria. It is available as Java library for command line or embedded use, as well as a [https://odfvalidator.org/ web application archive (WAR)]. ODF Validator is part of the [Apache ODF Toolkit].

== User Experiences ==

[http://www.openplanetsfoundation.org/comment/529#comment-529 Test by KEEP Solutions]:

<blockquote>Apache ODF Validator gives many false-negatives and false-positives (...) [b]ut (..) the schemas are publicly available and the method to validate is well defined by OASIS (...).</blockquote>

== Development Activity ==

Applesauce

2025-11-07T10:17:52Z

BertrandCaron: wording

{{Infobox tool
|purpose=Standalone disk image analysis/repair/conversion tool.
|homepage=https://applesaucefdc.com/software/
|license=unknown
|cost=Free
|platforms=MacOS
|language=English
|function=Disk Imaging
|content=Disk Image
}}
{{Infobox tool details}}
== Description ==
Disk Imaging tool which can read Applesauce A2R, SCP, Kryoflux RAW flux formats, visualize the floppy disk structure, and output common disk image formats.

== User Experiences ==

Applesauce was used by Internet Archive to [https://archive.org/details/2025_01_NOOKS_AND_CRANNIES image floppies].

Applesauce

2025-11-07T10:17:06Z

BertrandCaron: link to user xp at Internet Archive

{{Infobox tool
|purpose=Standalone disk image analysis/repair/conversion tool.
|homepage=https://applesaucefdc.com/software/
|license=unknown
|cost=Free
|platforms=MacOS
|language=English
|function=Disk Imaging
|content=Disk Image
}}
{{Infobox tool details}}
== Description ==
Disk Imaging tool which can read Applesauce A2R, SCP, Kryoflux RAW flux formats, visualize the floppy disk structure, and output common disk image formats.

== User Experiences ==

Applesauce was used to [https://archive.org/details/2025_01_NOOKS_AND_CRANNIES image floppies at Internet Archive].

Qpdf

2025-09-08T10:17:42Z

BertrandCaron: /* User Experiences */ added link to a blog post illustrating the use of the tool

SWF

2025-09-06T13:04:33Z

BertrandCaron: Created format SWF

{{Infobox format
|Wikidata ID=Q594447
|File formats wiki ID=SWF
|PRONOM PUID=fmt/104 fmt/105 fmt/106 fmt/107 fmt/108 fmt/109
}}
SWF (Small Web Format / Shockwave Format) is an obsolete Adobe format for Flash applications.

Ruffle

2025-09-06T13:00:56Z

BertrandCaron: Added SWF as input format

{{Infobox tool
|purpose=A flash player emulator written in Rust
|homepage=https://github.com/ruffle-rs/ruffle
|sourcecode=https://github.com/ruffle-rs/ruffle
|license=Apache License 2.0
|cost=Free and Open Source (FOSS)
|platforms=Windows, Linux, MacOS
|language=Rust
|formats_in=SWF
|function=Viewer
}}
{{Infobox tool details}}
== Description ==


Ruffle is a flash player emulator written in Rust. It is helpful to users with content such as SWF who would like to view the content and engage with it interactively.

As open source software the utility might also offer potential for developers to extract information about ''significant properties'' about Flash content by accessing the utility's underlying APIs.

= Development Activity =

All development activity is visible on GitHub: http://github.com/ruffle-rs/ruffle/commits

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

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

TweakPNG

2025-09-05T15:43:11Z

BertrandCaron: Added link to Ange Albertini's video.

{{Infobox tool
|image=Tweakpng.png
|purpose=TweakPNG examines different chunks in a PNG file and decode the information contained in each of these.
|homepage=https://entropymine.com/jason/tweakpng/
|sourcecode=https://github.com/jsummers/tweakpng
|license=GPL-3.0 license
|platforms=Windows XP and higher
|language=English
|formats_in=PNG
|function=Forensic, Metadata Extraction, Validation
|content=Image
}}
{{Infobox tool details}}
== Description ==

TweakPNG reveals the internal structure of PNGs by showing every chunk it contains, its length, type, CRC, and attribute. It decodes the content of metadata chunks. It can also check the validity of the file, edit and add new chunks and import an ICC profile.

== User Experience ==

Ange Albertini demonstrates the use of the tool in [https://www.youtube.com/live/Ck5_ADtePzE?t=1382 his video on PNG basics].

TweakPNG

2025-09-05T15:34:31Z

BertrandCaron:

File:Tweakpng.png

2025-09-05T15:34:09Z

BertrandCaron: A screenshot of the TweakPNG tool interface.

== Summary ==
A screenshot of the TweakPNG tool interface.

TweakPNG

2025-09-05T15:30:36Z

BertrandCaron: Creation of the page.

{{Infobox tool
|purpose=TweakPNG examines different chunks in a PNG file and decode the information contained in each of these.
|homepage=https://entropymine.com/jason/tweakpng/
|sourcecode=https://github.com/jsummers/tweakpng
|license=GPL-3.0 license
|platforms=Windows XP and higher
|language=English
|formats_in=PNG
|function=Forensic, Metadata Extraction, Validation
|content=Image
}}
{{Infobox tool details}}
== Description ==

TweakPNG reveals the internal structure of PNGs by showing every chunk it contains, its length, type, CRC, and attribute. It decodes the content of metadata chunks. It can also check the validity of the file, edit and add new chunks and import an ICC profile.

Mets-bag-checker

2024-09-04T10:50:18Z

BertrandCaron:

{{Infobox tool
|purpose=METS Bag checker is a simple python tool to check the validity of METS Information Packages (XML validity, completeness, Data Objects fixity, absence of unreferenced files).
|sourcecode=https://framagit.org/BCaron/mets-bag-checker
|license=GNU GPLv3
|language=python
|formats_in=METS (Metadata Encoding and Transmission Standard)
|function=Fixity, Validation
}}
{{Infobox tool details}}
== Description ==

METS Bag checker is a simple python tool to help METS implementers with little IT resources checking the validitiy of their Information Packages (below abbreviated as "IP(s)"). The term "bag" refers to the BagIt standard (RFC 8493), as this tool is based on some basic rules, similar to those defined by BagIt, in order to perform checks on IPs. Note that these conventions are not enforced by the METS standard itself but are of common usage in METS implementations:
* Manifest at the root Package (directory) level;
* Same manifest name in all Packages - or at least predictable, according to a given pattern -;
* Reference to all files contained in the Package by //mets:file elements;
* Reference to the Package files' via a relative path in the //mets:file/mets:FLocat/@xlink:href attribute;
* Use of //mets:file/@CHECKSUM and //mets:file/@CHECKSUMTYPE attributes to specify file checksum calculated with MD5, SHA-1, SHA-256, SHA-384 or SHA-512 algorithm.

Please note that this is a personal project by Bertrand Caron (Bibliothèque nationale de France).

Mets-bag-checker

2024-09-04T10:49:08Z

BertrandCaron:

{{Infobox tool
|purpose=METS Bag checker is a simple python tool to check the validity of METS Information Packages (XML validity, completeness, Data Objects fixity, absence of unreferenced files).
|sourcecode=https://framagit.org/BCaron/mets-bag-checker
|license=GNU GPLv3
|language=python
|formats_in=METS (Metadata Encoding and Transmission Standard)
|function=Fixity, Validation
}}
{{Infobox tool details}}
== Description ==

METS Bag checker is a simple python tool to help METS implementers with little IT resources checking the validitiy of their Information Packages (below abbreviated as "IP(s)"). The term "bag" refers to the BagIt standard (RFC 8493), as this tool is based on some basic rules, similar to those defined by BagIt, in order to perform checks on IPs. Note that these conventions are not enforced by the METS standard itself but are of common usage in METS implementations:
* Manifest at the root Package (directory) level;
* Same manifest name in all Packages - or at least predictable, according to a given pattern -;
* Reference to all files contained in the Package by //mets:file elements;
* Reference to the Package files' via a relative path in the //mets:file/@xlink:href attribute;
* Use of //mets:file/@CHECKSUM and //mets:file/@CHECKSUMTYPE attributes to specify file checksum calculated with MD5, SHA-1, SHA-256, SHA-384 or SHA-512 algorithm.

Please note that this is a personal project by Bertrand Caron (Bibliothèque nationale de France).

Mets-bag-checker

2024-09-04T10:43:43Z

BertrandCaron: Creation of the tool's page

{{Infobox tool
|purpose=METS Bag checker is a simple python tool to check the validity of METS Information Packages (XML validity, completeness, Data Objects fixity, absence of unreferenced files).
|sourcecode=https://framagit.org/BCaron/mets-bag-checker
|license=GNU GPLv3
|language=python
|formats_in=METS (Metadata Encoding and Transmission Standard)
|function=Validation, Fixity
}}
{{Infobox tool details}}
== Description ==

METS Bag checker is a simple python tool to help METS implementers with little IT resources checking the validitiy of their Information Packages (below abbreviated as "IP(s)"). The term "bag" refers to the BagIt standard (RFC 8493), as this tool is based on some basic rules, similar to those defined by BagIt, in order to perform checks on IPs. Note that these conventions are not enforced by the METS standard itself but are of common usage in METS implementations:
* Manifest at the root Package (directory) level;
* Same manifest name in all Packages - or at least predictable, according to a given pattern -;
* Reference to all files contained in the Package by //mets:file elements;
* Reference to the Package files' via a relative path in the //mets:file/@xlink:href attribute;
* Use of <file> CHECKSUM and CHEcKSUMTYPE to specify file checksum calculated with MD5, SHA-1, SHA-256, SHA-384 or SHA-512 algorithm.

Please note that this is a personal project by Bertrand Caron (Bibliothèque nationale de France).

Greens

2022-06-14T15:24:06Z

BertrandCaron: Corrected official website (Github repo).

{{Infobox tool
|image={{PAGENAMEE}}.png
|purpose=ARK identifiers minter and resolver
|homepage=https://github.com/uhlibraries-digital/greens
|license=MIT license
|function=Persistent Identification
}}
{{Infobox tool details}}




== Description ==
Greens is a rails application that is used as a ARK minter and resolver

== User Experiences ==


== Development Activity ==

Duke Data Accessioner

2022-06-04T15:36:15Z

BertrandCaron: Added PREMIS as output format.

{{Infobox tool
|purpose=Data Accessioner provides a graphical user interface to aid in migrating data from physical media to a dedicated file server, documenting the process and using MD5 checksums to identify any errors introduced in transfer.
|homepage=http://dataaccessioner.org/
|sourcecode=https://github.com/DataAccessioner/DataAccessioner
|license=Free
|cost=Free
|platforms=Java
|function=File Copy, File Format Identification, Metadata Extraction, Transfer, Validation
|formats_out=PREMIS (Preservation Metadata Implementation Strategies)
}}
{{Infobox tool details
|ohloh_id=Data Accessioner
}}
= Description =
The Data Accessioner provides a graphical user interface to aid in migrating data from physical media to a dedicated file server, documenting the process and using MD5 checksums to identify any errors introduced in transfer. The software also offers a way to integrate metadata tools into the migration workflow. The tool is primarily designed for use by technical services librarians in small institutions with little or no IT support.
====Provider====
Data Accessioner website and POWRR.
====Licensing and cost====
The software is free and licensed under the GNU Lesser General Public License (v 2.1).
====Platform and interoperability====
The software is written in Java, which renders it platform independent. (Requires Java 6.)

For versions 0.3.1 and earlier plugins are used via the Java Plugin Framework (JPF); a noted issue is that the JPF plugins do not work when running in a Mac OSX environment.
====Functional notes====
The Data Accessioner is comprised of three main components; a graphical interface, a migrator, and a metadata manager. The migrator recursively navigates a file tree, copying it to a given destination with the option of skipping specified files and directories. It also creates a MD5 checksum for both the original file and the new copy, comparing the two to detect and notify the user of any errors. As of version 1.0 the migrator also runs each file through FITS and sends the results to the metadata manager. The metadata manager, by default, transforms the FITS output to PREMIS (v 2.2) object metadata although this can be changed by updating an XSLT. Previous versions used Jhove, Droid, and custom metadata manager plugins.
While the software’s website does not give any information on volume or file format limitations, a [http://e-records.chrisprom.com/?p=1809 University of Illinois case study] encountered both. Overall, the user was extremely happy with the software; however, the project was unable to migrate information in CDA format and encountered a JVM error when attempting to migrate a large backup disk.
====Usability====
The Data Accessioner uses a simple and straightforward Graphical User Interface.
If the user wishes to exclusively run the migratory element of the software it must be done through command-line; however, this should not be necessary in the vast majority of uses.

The Sustainable Heritage Network has [https://vimeo.com/142888727 created a video tutorial] that provides an overview of how to use the tool.

====Expertise required====
The project’s goal was to create software for technical services librarians, able “to be easily adopted by smaller institutions with little or no IT staff.” Metadata customization, however, entails either editing the FITS to PREMIS XSLT or modifying the application's source-code, which requires solid knowledge of application design.
====Standards compliance====
The software includes a PREMIS metadata manager.
====Influence and take-up====
No statistics are available although it has been featured in various conference presentations and workshops.
====Other====
The old home page can be found here:http://library.duke.edu/rubenstein/uarchives/about/data-accessioner
= User Experiences =
[https://saaers.wordpress.com/2016/04/26/keeping-track-of-time-with-data-accessioner/ Keeping Track of Time With Data Accessioner]

[http://e-records.chrisprom.com/dataaccessioner/ Practical e-Records: Data Accessioner Review]

= Development Activity =
https://github.com/seth-shaw/DataAccessioner/

Matchbox Tool

2021-12-06T14:09:50Z

BertrandCaron: /* Description */ Encoding issues corrected

{{Infobox tool
|purpose=Matchbox: Duplicate detection tool for digital document collections.
|homepage=https://github.com/openplanets/scape/tree/master/pc-qa-matchbox
|license=Open source
|function=Quality Assurance, De-Duplication
|content=Image
}}
{{Infobox tool details
|ohloh_id=Matchbox Tool
}}
= Description =
The Matchbox tool is responsible for finding duplicatre pairs in a collection of digital documents based on SIFT features and SSIM methods. Consequently the tool takes a collection path with associated parameters as input. Currently three scenarios are implemented. These are:

* Duplicate search in one turn (parameter 'all')

* Professional duplicate search (experienced user can execute particular step in 'FindDuplicates' workflow)

* Quick check if two documents are duplicates (based on previous BoW dictionary).

Further parameters that influence and adjust duplicate analysis are currently investigated.

Image processing method:

The image processing algorithm can be described in 4 steps:

1. Document feature extraction

* Interest point detection (applying Scale Invariant Feature Transform (SIFT) keypoint extraction)
* Derivation of local feature descriptors (invariant to geometrical or radiometrical distortions)

2. Learning visual dictionary

* Clustering method applied to all SIFT descriptors of all images using k-means algorithm
* Run over collection and collect local descriptors in a visual dictionary using Bag-Of-Words (BoW) algorithm

3. Create visual histogram for each image document

4. Detect similar images based on visual histogram and local descriptors. Evaluate similarity score – pair-wise comparison of corresponding keyword frequency histograms for all documents. Conduct structural similarity analysis applying Sturctural SIMilarity (SSIM) approach (1 means identical and 0 means very different)

* Rotate
* Scale
* Mask
* Overlaying

Usage:

FindDuplicates script can be invoked from command line. For standard usage two parameters are required: path to the collection documents and 'all'.

scape/pc-qa-matchbox/Python# python2.7 FindDuplicates.py h

usage: FindDuplicates.py [-h] [\--threads THREADS] [\--sdk SDK] [\--precluster PRECLUSTER] [\--clahe CLAHE] [\--config CONFIG] [\--featdir FEATDIR] [\--bowsize BOWSIZE] [\--csv] [-v] dir all,extract,compare,train,bowhist,clean

= User Experiences =
currently installed at Austrian National Library

= Development Activity =

METSFlask

2020-07-03T10:57:15Z

BertrandCaron: Created page with " {{Infobox_tool |purpose=A web application for human-friendly exploration of Archivematica METS files |..."

{{Infobox_tool
|purpose=A web application for human-friendly exploration of Archivematica METS files
|image={{PAGENAMEE}}.png
|homepage=https://github.com/tw4l/METSFlask
|license=MIT License
|platforms=
}}


[[Category:View]]

[[Category:METS]]

== Description ==
METSFlask is the METS Viewer used by [https://coptr.digipres.org/Archivematica Archivematica].

A live demo is available on http://bitarchivist.pythonanywhere.com/.

== User Experiences ==


== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

NumaHOP

2020-07-03T10:50:11Z

BertrandCaron: Creating the entry.

{{Infobox_tool
|purpose=Platform for digitization projects management
|image={{PAGENAMEE}}.png
|homepage=https://www.numahop.fr/
|license=
|platforms=
}}


[[Category:Quality Assurance]]
[[Category:METS]]

== Description ==
NumaHOP is a tool for managing digitization projects. It provides the following features:
* importing descriptive records,
* producing a condition report,
* converting UNIMARC or EAD records to Dublin Core,
* controlling deliverables,
* producing derivative products (dissemination images, OCR files, etc.),
* creating Submission Information Packages, with METS metadata.

== User Experiences ==


== Development Activity ==
NumaHOP has been developed by [http://www.bsg.univ-paris3.fr/iguana/www.main.cls Bibliothèque Sainte-Geneviève], [https://www.bulac.fr/ Bibliothèque universitaire des langues et civilisations (BULAC)] and the [https://www.sciencespo.fr/bibliotheque/ Sciences Po university library]. Its source code is freely reusable and will be upload soon on Github.



{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

DFG Viewer

2020-07-03T09:21:06Z

BertrandCaron:

{{Infobox_tool
|purpose=Browser-based viewer for digital objects
|image=
|homepage=https://dfg-viewer.de/
|license=GPL 2.0
|platforms=
}}


[[Category:View]]

[[Category:METS]]

== Description ==
The DFG Viewer is a browser web service for displaying digital representations from decentralised library repositories. It has an XML interface for exchanging meta- and structural data in the METS/MODS and METS/TEI format. Displaying of a digital representation is enriched and supplemented with additional functions, if applicable, with the help of these data.

As a result, users are provided with a uniform interface for viewing digitised media. They can browse documents, view and download the individual digital representations in various resolutions and switch to the respective web presentation of the library involved upon a request to that end in order to use further possibilities there.

The DFG Viewer is based on the free CMSTYPO3 as well as the open source digitization software [https://coptr.digipres.org/Goobi Goobi] and can be used free of charge by anyone interested. This can either be done centrally via the web service operated here or by means of a local implementation. In this context, connection is optionally provided via a native XML interface or via the standardised OAI protocol. You can find comprehensive documentations, examples and useful tips regarding both application scenarios there.

== User Experiences ==

== Development Activity ==

The last version of DFG Viewer is 5.0. Its source code is available on Github at https://github.com/slub/dfg-viewer.

{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

DFG Viewer

2020-07-03T09:17:34Z

BertrandCaron: Created page with " {{Infobox_tool |purpose=Browser-based viewer for digital objects |image= |homepage=https://dfg-viewer...."

{{Infobox_tool
|purpose=Browser-based viewer for digital objects
|image=
|homepage=https://dfg-viewer.de/
|license=GPL 2.0
|platforms=
}}


[[Category:View]]

[[Category:METS]]

== Description ==
The DFG Viewer is a browser web service for displaying digital representations from decentralised library repositories. It has an XML interface for exchanging meta- and structural data in the METS/MODS and METS/TEI format. Displaying of a digital representation is enriched and supplemented with additional functions, if applicable, with the help of these data.

As a result, users are provided with a uniform interface for viewing digitised media. They can browse documents, view and download the individual digital representations in various resolutions and switch to the respective web presentation of the library involved upon a request to that end in order to use further possibilities there.

The DFG Viewer is based on the free CMSTYPO3 as well as the open source digitization software [https://coptr.digipres.org/Goobi Goobi] and can be used free of charge by anyone interested. This can either be done centrally via the web service operated here or by means of a local implementation. In this context, connection is optionally provided via a native XML interface or via the standardised OAI protocol. You can find comprehensive documentations, examples and useful tips regarding both application scenarios there.

== User Experiences ==

== Development Activity ==
{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

Greens

2020-07-03T08:32:26Z

BertrandCaron:

{{Infobox_tool
|purpose=ARK identifiers minter and resolver
|image={{PAGENAMEE}}.png
|homepage=https://github.com/ndlib/noids
|license=MIT license
|platforms=
}}


[[Category:Persistent Identification]]

== Description ==
Greens is a rails application that is used as a ARK minter and resolver

== User Experiences ==


== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

DArcMail

2019-09-04T15:50:34Z

BertrandCaron: Created page with " {{Infobox_tool |purpose= Processing and access to email accounts |homepage=https://siarchives.si.edu/wh..."

{{Infobox_tool
|purpose= Processing and access to email accounts
|homepage=https://siarchives.si.edu/what-we-do/digital-curation/email-preservation-darcmail
|license=MIT License (https://opensource.org/licenses/MIT)
|platforms=Windows, Mac OS, Linux
}}

[[Category:Data capture and Deposit]]
[[Category:Access]]
[[Category:Email]]
== Description ==
The DArcMail application builds upon the functional core of the Collaborative Electronic Records Preservation (CERP) Parser. DArcMail delivers a broader range of features and functions and does so on the popular Python platform. In addition to preservation functionality, DArcMail supports appraisal, processing, and providing access to email accounts or large groups of related email messages. DArcMail’s design shrinks processing time and enables it to handle large email accounts on the three most popular operating systems:Windows, Mac OS, and Linux systems.
It is developed by the Smithsonian Institution Archives (SIA) and maintained by the Archives plus a user community.
DArcMail is python-based and works on a MySQL or SQLite database.
== User Experiences ==
Reports on DArcMail have been produced by the Task Force on Technical Approaches for Email Archives in March 2018, at http://www.emailarchivestaskforce.org/documents/email-tools/ and by Harvard Library in 2016 at http://nrs.harvard.edu/urn-3:HUL.InstRepos:28682572.

== Development Activity ==
DArcMail's last version is 1.2, released in March 2018.

Omeka Identity plugin

2019-05-11T14:17:17Z

BertrandCaron: Created page with " {{Infobox_tool |purpose=Plugin for Omeka to assign ARK identifiers |image={{PAGENAMEE}}.png |homepage=..."

{{Infobox_tool
|purpose=Plugin for Omeka to assign ARK identifiers
|image={{PAGENAMEE}}.png
|homepage=https://github.com/uklibraries/IdentityPlugin
|license=MIT License
|platforms=
}}


[[Category:Persistent Identification]]

== Description ==
The Omeka Identity plugin makes sure that each item in the digital library has an ARK identifier.

It is developped by the Kentucky Digital Library.

== User Experiences ==


== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

UKWA Access API

2019-05-11T14:13:18Z

BertrandCaron: Created page with " {{Infobox_tool |purpose=Web archives access API |image={{PAGENAMEE}}.png |homepage=https://github.com/..."

{{Infobox_tool
|purpose=Web archives access API
|image={{PAGENAMEE}}.png
|homepage=https://github.com/ukwa/ukwa-access-api
|license=Apache License 2.0
|platforms=
}}


[[Category:Persistent Identification]]

== Description ==
UKWA Access API is an application to wrap up APIs for accessing UKWA content including an ARK resolver.

== User Experiences ==


== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}