COPTR - User contributions [en-gb]

Fixit tiff

2021-11-09T13:41:29Z

Andreas Romeyke: updated URLs because repository moved to git.fsfe.org

{{Infobox tool
|purpose=fixes some issues in (potentially) baseline tiffs, as an example, invalid datetime tags, wrong tiff tag order
|homepage=https://git.fsfe.org/art1pirat/fixit_tiff
|license=same as libtiff, see http://libtiff.maptools.org/ for details
|platforms=Linux (should work with each distribution, tested under Debian Buster), AIX, Windows
|function=Repair
|content=Image
}}
{{Infobox tool details
|releases_rss=https://git.fsfe.org/art1pirat/fixit_tiff/releases
|issues_rss=https://git.fsfe.org/art1pirat/fixit_tiff/issues
}}




== Description ==

Repairs broken TIFF files, it comes with routines to:
* remove all non-baseline-tags
* fix order of tags
* fix typical DATETIME tag problems

== User Experiences ==


See blog posts at https://kulturreste.blogspot.com/search?q=fixit_tiff

== Development Activity ==


https://git.fsfe.org/art1pirat/fixit_tiff/commits/branch/master

Checkit tiff

2021-11-09T13:38:55Z

Andreas Romeyke: updated URLs because repo was moved to git.fsfe.org

{{Infobox tool
|purpose=a tool to validate TIFF files against given configuration profile
|homepage=https://git.fsfe.org/art1pirat/checkit_tiff
|license=same as libtiff, see http://libtiff.maptools.org/misc.html
|platforms=Linux (each distribution should work, tested under Debian Buster), Windows
|formats_in=TIFF
|function=Quality Assurance, Validation
|content=Image
}}
{{Infobox tool details}}
== Description ==

The tool evaluates if a given TIFF matches against the rules defined in a configuration profile. The configuration profile is human readable and allows to validate TIFFs against rules like:
* no compression
* only 300dpi
* if tag X has Value Y then tag Z must exist

It is optimized for very high throughput, it is extremely robust and it is suitable for scripted use.

== User Experiences ==


See https://kulturreste.blogspot.com/search?q=checkit_tiff for blogposts about usage of checkit_tiff.

== Development Activity ==


https://git.fsfe.org/art1pirat/checkit_tiff/commits/branch/master

Checkit tiff

2021-05-27T09:01:17Z

Andreas Romeyke:

{{Infobox tool
|purpose=a tool to validate TIFF files against given configuration profile
|homepage=https://art1pirat.spdns.org/art1/checkit_tiff
|license=same as libtiff, see http://libtiff.maptools.org/misc.html
|platforms=Linux (each distribution should work, tested under Debian Buster), Windows
|function=Quality Assurance, Validation
|content=Image
}}
{{Infobox tool details}}
== Description ==

The tool evaluates if a given TIFF matches against the rules defined in a configuration profile. The configuration profile is human readable and allows to validate TIFFs against rules like:
* no compression
* only 300dpi
* if tag X has Value Y then tag Z must exist

It is optimized for very high throughput, it is extremely robust and it is suitable for scripted use.

== User Experiences ==


See https://kulturreste.blogspot.com/search?q=checkit_tiff for blogposts about usage of checkit_tiff.

== Development Activity ==


https://art1pirat.spdns.org/art1/checkit_tiff/commits/branch/master

File Format Identification Pronom

2021-05-27T08:48:52Z

Andreas Romeyke: tool to analyze pronom/droid signatures and/or convert them into regular expressions (regex)

{{Infobox tool
|purpose=Perl API to analyze and handle droid (PRONOM) signatures
|homepage=https://metacpan.org/release/File-FormatIdentification-Pronom
|license=Perl Artistic License
|function=File Format Identification
}}
{{Infobox tool details}}

The module allows to handle Droid signatures. [[Droid]] is a utility which uses the PRONOM database to identify file formats.

See https://www.nationalarchives.gov.uk/PRONOM/ for details.

With this module you could:

* convert Droid signatures to Perl regular expressions (Regex)
* analyze files and display which/where pattern of Droid signature matches via tag-files for wxHexEditor
* calc statistics about Droid signatures

The blog post https://kulturreste.blogspot.com/2018/10/heres-tool-make-it-work.html shows how to analyze the signatures.

Crazy-fast-image-scan

2021-05-27T08:40:50Z

Andreas Romeyke: file format identification tool for media images

{{Infobox tool
|purpose=crazy-fast-image-scan is a script to scan media very quickly to find out what kind of content it contains
|homepage=https://metacpan.org/pod/distribution/File-FormatIdentification-RandomSampling/bin/crazy_fast_image_scan.pl
|license=GNU General Public License 3.0
|function=File Format Identification
}}
{{Infobox tool details}}

== Usage ==
<code>
perl ./crazy_fast_image_scan.pl --image=/dev/sda
</code>

This scans the device /dev/sda.

<code>
perl ./crazy_fast_image_scan.pl --percent=0.00001 --image=cdrom.img
</code>

This scans the image using 0.00001 (0.001 %) bytes of the image.

== Description ==

This script scans devices or images very fast using random sampling and reports what kind of content could be found. This is useful to decide which image or media could have stuff of interest and allows to prioritize the order of further examinations.

The script uses random sampling and is based on ideas by Simson Garfinkel in a talk http://simson.net/ref/2014/2014-02-21_RPI_Forensics_Innovation.pdf

It calculates the sectors of a given image or device, select n sector samples, seek to the sector positions and read it.

DART (Digital Archivist's Resource Tool)

2020-08-17T08:37:49Z

Andreas Romeyke: /* Description */

{{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
}}


[[Category:Storage]]
[[Category:File Management]]
[[Category:Fixity]]
[[Category:Transfer]]

[[Category: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
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

ANTS (Archives Network Transfer System)

2020-08-17T08:37:18Z

Andreas Romeyke: /* Description */

{{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.
|image={{PAGENAMEE}}.png
|homepage=https://github.com/UAlbanyArchives/ants
|license=
|platforms=
}}



[[Category: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
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

Exactly

2020-08-17T08:36:30Z

Andreas Romeyke:

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



[[Category: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 ==


All development activity is visible on github: https://github.com/WeAreAVP/uk-exactly/

Exactly on Open Hub: https://www.openhub.net/p/exactly (no activity)

{{Infobox_tool_details
|mailing_lists=https://groups.google.com/forum/#!forum/exactly-users
|ohloh_id=exactly
}}

DataStage

2020-08-17T08:35:52Z

Andreas Romeyke: /* Standards compliance */

{{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.
|image=
|homepage=http://www.dataflow.ox.ac.uk/index.php/datastage
|license=
|platforms=
}}


[[Category:Active Data Storage]]
[[Category:Preservation System]]
[[Category:Managing Active Research Data]]
[[Category: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
}}

Archivematica

2020-08-17T08:34:44Z

Andreas Romeyke:

{{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
|image=
|homepage=https://www.archivematica.org
|license=[http://www.gnu.org/licenses/agpl.html AGPL version 3]
|platforms=
}}


[[Category:Preservation System]]
[[Category:File Format Migration]]
[[Category:METS]]

= 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

BagIt Transfer Utilities

2020-08-17T08:33:43Z

Andreas Romeyke: /* Description */

{{Infobox_tool
|purpose=BagIt transfer Utilities are a collection of tools developed for the purpose of validation and transfer of bags.
|image=
|homepage=http://sourceforge.net/projects/loc-xferutils/
|license=BSD License
|platforms=UNIX
}}


[[Category:Fixity]]
[[Category:File Copy]]

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

2020-08-17T08:33:10Z

Andreas Romeyke:

{{Infobox_tool
|purpose=BagIt Library is a Java software library that supports the creation, manipulation and validation of bags.
|image=
|homepage=http://sourceforge.net/projects/loc-xferutils/
|license=Public domain
|platforms=
}}


[[Category:Fixity]]
[[Category:File Copy]]

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

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=BagIt Library (BIL)
}}

Bagger

2020-08-17T08:26:07Z

Andreas Romeyke:

{{Infobox_tool
|purpose=GUI application to facilitate the creation and verification of [[BagIt]] bags.
|image=
|homepage=https://github.com/LibraryOfCongress/bagger
|license=Open License, but relies on several Apache based and GNU licensed components.
|platforms=
}}


[[Category:Fixity]]
[[Category: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 =

{{Infobox_tool_details
|ohloh_id=Bagger
}}

=== Activity Feed===
Link to any RSS feed that is updated when issue or code updates occur, if any, e.g:
<rss max=7>http://sourceforge.net/api/file/index/project-id/247203/mtime/desc/limit/20/rss</rss>

=== Release Feed ===

Bagger

2020-08-17T08:20:38Z

Andreas Romeyke:

{{Infobox_tool
|purpose=GUI application to facilitate the creation and verification of {{BagIt}} bags.
|image=
|homepage=https://github.com/LibraryOfCongress/bagger
|license=Open License, but relies on several Apache based and GNU licensed components.
|platforms=
}}


[[Category:Fixity]]
[[Category: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 =

{{Infobox_tool_details
|ohloh_id=Bagger
}}

=== Activity Feed===
Link to any RSS feed that is updated when issue or code updates occur, if any, e.g:
<rss max=7>http://sourceforge.net/api/file/index/project-id/247203/mtime/desc/limit/20/rss</rss>

=== Release Feed ===

Checkit tiff

2020-08-17T08:11:57Z

Andreas Romeyke:

{{Infobox_tool
|purpose=a tool to validate TIFF files against given configuration profile

|homepage=https://art1pirat.spdns.org/art1/checkit_tiff
|license=same as libtiff, see http://libtiff.maptools.org/misc.html
|platforms=Linux (each distribution should work, tested under Debian Buster), Windows
}}





[[Category:Image]] [[Category:Validation]] [[Category:Quality_Assurance]]

== Description ==

The tool evaluates if a given TIFF matches against the rules defined in a configuration profile. The configuration profile is human readable and allows to validate TIFFs against rules like:
* no compression
* only 300dpi
* if tag X has Value Y then tag Z must exist

== User Experiences ==


See https://kulturreste.blogspot.com/search?q=checkit_tiff for blogposts about usage of checkit_tiff.

== Development Activity ==


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

Checkit tiff

2020-08-17T08:11:08Z

Andreas Romeyke: refreshed repository information

{{Infobox_tool
|purpose=a tool to validate TIFF files against given configuration profile

|homepage=https://art1pirat.spdns.org/art1/checkit_tiff
|license=same as libtiff, see http://libtiff.maptools.org/misc.html
|platforms=Linux (Debian Jessie), Windows (untested)
}}





[[Category:Image]] [[Category:Validation]] [[Category:Quality_Assurance]]

== Description ==

The tool evaluates if a given TIFF matches against the rules defined in a configuration profile. The configuration profile is human readable and allows to validate TIFFs against rules like:
* no compression
* only 300dpi
* if tag X has Value Y then tag Z must exist

== User Experiences ==


See https://kulturreste.blogspot.com/search?q=checkit_tiff for blogposts about usage of checkit_tiff.

== Development Activity ==


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

Fixit tiff

2020-08-17T08:09:29Z

Andreas Romeyke: refreshed repository information

{{Infobox_tool
|purpose=fixes some issues in (potentially) baseline tiffs, as an example, invalid datetime tags, wrong tiff tag order

|homepage=https://art1pirat.spdns.org/art1/fixit_tiff
|license=same as libtiff, see http://libtiff.maptools.org/ for details
|platforms=Linux (should work with eatch distribution, tested under Debian Buster), AIX, Windows
}}




[[Category:Image]] [[Category:Repair]]



== Description ==

Repairs broken TIFF files, it comes with routines to:
* remove all non-baseline-tags
* fix order of tags
* fix typical DATETIME tag problems

== User Experiences ==


See blog posts at https://kulturreste.blogspot.com/search?q=fixit_tiff

== Development Activity ==


{{Infobox_tool_details
|releases_rss=https://art1pirat.spdns.org/art1/fixit_tiff/commits/branch/master
|issues_rss=https://art1pirat.spdns.org/art1/fixit_tiff/issues
|mailing_lists=
|ohloh_id=
}}

Archive::BagIt

2020-08-17T08:00:57Z

Andreas Romeyke: details added

{{Infobox_tool
|purpose=BagIt API for Perl
|image=
|homepage=https://metacpan.org/pod/Archive::BagIt
|license=Perl5 Attribution License
|platforms=UNIX, Windows, see http://matrix.cpantesters.org/?dist=Archive-BagIt+0.066
}}


[[Category:Fixity]]
[[Category:File Copy]]

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

Archive::BagIt

2020-08-17T07:56:40Z

Andreas Romeyke:

Archive::BagIt

2020-08-17T07:52:55Z

Andreas Romeyke: Created page with "{{Infobox_tool |purpose=BagIt API for Perl |image= |homepage=https://metacpan.org/pod/Archive::BagIt |license=Perl5 Attribution License |platforms=UNIX, Windows, see http://ma..."

{{Infobox_tool
|purpose=BagIt API for Perl
|image=
|homepage=https://metacpan.org/pod/Archive::BagIt
|license=Perl5 Attribution License
|platforms=UNIX, Windows, see http://matrix.cpantesters.org/?dist=Archive-BagIt+0.066
}}


[[Category:Fixity]]
[[Category:File Copy]]

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