COPTR - User contributions [en-gb]

BnL Mets Exporter

2020-07-08T06:42:48Z

Jukervin:

{{Infobox_tool
|purpose=Command Line Interface (CLI) to export METS/ALTO documents to other formats.
|homepage=https://github.com/natliblux/BnLMetsExporter
|license=GPL v3
|platforms=Java
}}



[[Category:Metadata Processing]]


[[Category:METS]]
[[Category:ALTO format]]

== Description ==

Command line tool used by the National Library of Luxembourg (Bibliothèque nationale de Luxembourg - BnL) to parse METS/ALTO documents and export them into another format.

Note that this project is highly tailored to the BnL's METS/ALTO requirements and current workflows.

== User Experiences ==


== Development Activity ==


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

Namalysator

2020-07-08T06:41:55Z

Jukervin:

{{Infobox_tool
|purpose=Tool for METS/ALTO validation and quality control.
|homepage=https://github.com/natliblux/Namalysator
|license=GPL v3
|platforms=Windows
}}



[[Category:Metadata Processing]]
[[Category:Quality Assurance]]
[[Category:Validation]]


[[Category:METS]]

== Description ==

This project is the initial QA tool that has been developed at the BnL in 2014 and is still in use for current digitization compaigns. However, the software is not actively developed. Only severe bug fixes are being made. The last major update was in 2018.

The software is written in C++ and consist of 3 programs:

*loadinventory: Load an external inventory file.
*metsverifier: Verifies a batch containing METS/ALTO packages.
*namalysator: GUI for quality control.

Features

*BNL Inventory loading
*METS/ALTO validation against BnL Schema
*Various logical checks (Page numbers, inventory cross-validation)
*GUI with calendar view, document listing, error listing and document viewer.
*Error reporting and exporting

== User Experiences ==


== Development Activity ==



Commits in GitHub : https://github.com/natliblux/Namalysator/commits/master

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

Namalysator

2020-07-08T06:38:42Z

Jukervin:

{{Infobox_tool
|purpose=Quality Control Tool for BnL digitization campaigns.
|homepage=https://github.com/natliblux/Namalysator
|license=GPL v3
|platforms=Windows
}}



[[Category:Metadata Processing]]
[[Category:Quality Assurance]]
[[Category:Validation]]


[[Category:METS]]

== Description ==

This project is the initial QA tool that has been developed at the BnL in 2014 and is still in use for current digitization compaigns. However, the software is not actively developed. Only severe bug fixes are being made. The last major update was in 2018.

The software is written in C++ and consist of 3 programs:

*loadinventory: Load an external inventory file.
*metsverifier: Verifies a batch containing METS/ALTO packages.
*namalysator: GUI for quality control.

Features

*BNL Inventory loading
*METS/ALTO validation against BnL Schema
*Various logical checks (Page numbers, inventory cross-validation)
*GUI with calendar view, document listing, error listing and document viewer.
*Error reporting and exporting

== User Experiences ==


== Development Activity ==



Commits in GitHub : https://github.com/natliblux/Namalysator/commits/master

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

BnL Mets Exporter

2020-07-08T06:37:45Z

Jukervin: Created tool page for BnL Mets Exporter

{{Infobox_tool
|purpose=CLI tool to export BnL METS/ALTO documents into another format
|homepage=https://github.com/natliblux/BnLMetsExporter
|license=GPL v3
|platforms=Java
}}



[[Category:Metadata Processing]]


[[Category:METS]]
[[Category:ALTO format]]

== Description ==

Command line tool used by the National Library of Luxembourg (Bibliothèque nationale de Luxembourg - BnL) to parse METS/ALTO documents and export them into another format.

Note that this project is highly tailored to the BnL's METS/ALTO requirements and current workflows.

== User Experiences ==


== Development Activity ==


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

Namalysator

2020-07-08T06:31:23Z

Jukervin: Created tool page for Namalysator

{{Infobox_tool
|purpose=Quality Control Tool for BnL digitization campaigns.
|homepage=https://github.com/natliblux/Namalysator
|license=GPL v3
|platforms=Windows
}}



[[Category:Metadata Processing]]
[[Category:Quality Assurance]]


[[Category:METS]]

== Description ==

This project is the initial QA tool that has been developed at the BnL in 2014 and is still in use for current digitization compaigns. However, the software is not actively developed. Only severe bug fixes are being made. The last major update was in 2018.

The software is written in C++ and consist of 3 programs:

*loadinventory: Load an external inventory file.
*metsverifier: Verifies a batch containing METS/ALTO packages.
*namalysator: GUI for quality control.

Features

*BNL Inventory loading
*METS/ALTO validation against BnL Schema
*Various logical checks (Page numbers, inventory cross-validation)
*GUI with calendar view, document listing, error listing and document viewer.
*Error reporting and exporting

== User Experiences ==


== Development Activity ==



Commits in GitHub : https://github.com/natliblux/Namalysator/commits/master

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

Bnlviewer

2020-07-08T06:21:58Z

Jukervin: Created tool page for Bnlviewer

{{Infobox_tool
|purpose=METS / ALTO viewer written in Java and Javascript
|homepage=https://sourceforge.net/projects/bnlviewer/
|license=
|platforms=
}}





[[Category:METS]]
[[Category:ALTO format]]

== Description ==

The National library of Luxembourg's viewer for METS files with OCR files in the ALTO format. The viewer needs a tomcat application server to run in. It can be deployed so that it reads the METS files from a local folder. Its main use is for digitized newspapers and postcards but can be adapted to other METS profiles as well.

== User Experiences ==


== Development Activity ==



Development stopped. Last update on 2014-09-22.

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

Limb Processing

2020-07-08T06:07:01Z

Jukervin: Created tool page

{{Infobox_tool
|purpose=Software for processing, enhancing and converting cultural heritage into digital cultural heritage
|homepage=https://www.limbsuite.com/limb-processing
|license=Commercial
|platforms=
}}



[[Category:Metadata Processing]]
[[Category:OCR]]


[[Category:METS]]
[[Category:ALTO format]]

== Description ==


LIMB Processing is a software solution to offer all the tools needed for digitization projects: project management, image processing, document processing (OCR, structuring, etc.), quality control, metadata management, as well as multiple conversion formats for long-term archiving, digital libraries or on-demand printing.

== User Experiences ==


== Development Activity ==


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

SobekCM METS Editor

2020-07-08T05:45:54Z

Jukervin: Created tool page

{{Infobox_tool
|purpose=Creation of METS documents from a folder of items with bibliographic metadata.
|homepage=http://sobekrepository.org/software/mets
|license=
|platforms=Windows
}}



[[Category:Metadata Processing]]


[[Category:METS]]

== Description ==

Windows form app creates METS-compliant metadata files for digital library resources. It allows the user to enter all of the bibliographic information,
and assign page names and divisions to the structure map. Supports MarcXML, MODS and Dublin Core for bibliographic metadata.

== User Experiences ==

* https://sourceforge.net/projects/metseditor/reviews/

== Development Activity ==



Development stopped. Latest release version 1.1.0 on 2013-07-07.

Relase history : http://sobekrepository.org/metseditor/history

SourceForge page : https://sourceforge.net/projects/metseditor/

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

EchoDep Hub and Spoke Framework Tool Suite

2020-07-07T13:43:18Z

Jukervin: Created tool page

{{Infobox_tool
|purpose=Tool suite to manage digital content in multiple repository systems.
|homepage=https://sourceforge.net/projects/echodep/
|license=University of Illinois/NCSA Open Source License
|platforms=
}}



[[Category:Metadata Processing]]


[[Category:METS]]

== Description ==

The Hub and Spoke (HandS) tool suite was built to help curators of digital objects manage content in multiple repository systems while preserving valuable preservation metadata. Implementing METS and PREMIS, HandS provides a standards-based method for packaging content that allows digital objects to be moved between repositories more easily while supporting the collection of technical and provenance information crucial for long-term preservation.

The Hub and Spoke Framework Tool Suite (HandS) was developed as part of the ECHO DEPository. ECHO DEPository a five-year (2004-2009) digital preservation research and development project at the University of Illinois at Urbana-Champaign, funded by the Library of Congress under their National Digital Information Infrastructure and Preservation Program (NDIIPP). Among the core activities in ECHO DEPository Phase I was repository evaluation, in which several open-source repository software applications were installed, configured, tested, and evaluated for insight into the real-world problems of archiving digital content. A key outcome of HandS in Phase I was a set of software scripts and programs, known as the Hub and Spoke Framework Tool Suite, for facilitating interoperability between repositories.

The Hub and Spoke Framework Tool Suite was designed not only to provide basic interoperability between repositories, but we are looking forward to using the architecture as a unifying platform for preservation. The architecture currently consists of several parts. Probably the most important being the METS profile which remains mostly neutral regarding content files and structure but defines a minimum level of descriptive (MODS) and administrative (PREMIS) metadata with a strong emphasis on preservation, particularly technical data and provenance.

A second key part of the architecture are the spokes. These are a RESTful Web Service which we call the Lightweight Repository CRUD Service (LRCRUDS). CRUD being Create, Retrieve, Update, and Delete from the relational database lexicon. This service would map URIs to local identifiers and use the HTTP methods PUT, GET, POST, and DELETE to handle packages being submitted or disseminated from a particular repository. Packages would be shipped over the network as ZIP archives containing a standard header, METS file, and content files in a format suitable for import into the repository. An instance of this service would be created for each repository participating in the HandS.

The third critical part of the architecture is the Hub. The Hub performs the transformations required to convert from and to the METS profile, and it manages the generation and validation of technical and provenance metadata. Initially the Hub is simply a staging area as packages are moved about. However, the ultimate goal is to develop the Hub into a trusted preservation archive capable of handling submissions from various other repositories and also disseminating packages to those repositories, as well as handling all the other required functions of a trusted digital repository.

== User Experiences ==


== Development Activity ==


Development stopped. Last commit in 2010-01-22.

Commits in SourceForge : https://sourceforge.net/p/echodep/code/commit_browser

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

METS Navigator

2020-07-07T13:26:00Z

Jukervin: Created tool page for METS Navigator

{{Infobox_tool
|purpose=METS-based system for displaying and navigating sets of page images or other multi-part digital objects.
|homepage=http://metsnavigator.sourceforge.net/
|license=
|platforms=
}}





[[Category:METS]]

== Description ==

METS Navigator is a METS-based system developed by the Indiana University Digital Library Program for displaying and navigating sets of page images or other multi-part digital objects. METS, the Metadata Encoding and Transmission Standard, is an XML standard, maintained by the Library of Congress, for managing and describing digital library objects. Using the information in the METS <structMap> elements, METS Navigator builds a hierarchical menu that allows users to navigate to specific sections of a document, such as title page, specific chapters, illustrations, etc. METS Navigator also allows simple navigation to the next, previous, first, and last page image or component part of a digital object.

METS Navigator is built using Java and open source Web technologies, including the Apache Struts Web Application Framework, the Castor Java & XML Data Binding libraries, and Ant, and runs under a Web application server such as Apache Tomcat.

== User Experiences ==


== Development Activity ==


Development stopped. Last commit was in 2012-05-09.

Commits in SourceForge : https://sourceforge.net/p/metsnavigator/code/commit_browser

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

Veridian

2020-07-07T13:08:09Z

Jukervin: Created tool page for Veridian

{{Infobox_tool
|purpose=Online search, discovery, and display of digitized newspaper collections
|homepage=https://veridiansoftware.com/services/#veridiansoftware
|license=Commercial
|platforms=Linux
}}



[[Category:Discovery]]


[[Category:METS]]
[[Category:ALTO format]]

== Description ==

Veridian Software is an online platform to make digitized collections more accessible to users.

It features full-text searching, search result summary, search facets and filters, and various browsing structures.

Veridian is built specifically to support digital objects in the METS/ALTO standard, which is well established as the industry standard for newspaper digitization projects.
Veridian supports METS/ALTO both with and without article segmentation and can even support both types of data within the same collection

== User Experiences ==


== Development Activity ==


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

7train

2020-07-07T12:37:01Z

Jukervin: Created tool page for 7train

{{Infobox_tool
|purpose=XSLT 2.0 tool for generating METS files from XML input
|homepage=http://seventrain.sourceforge.net/
|license=BSD License
|platforms=
}}



[[Category:Metadata Processing]]


[[Category:METS]]

== Description ==

An XSLT 2.0 tool for generating METS files from XML input. It builds the basic METS structure so that the user can worry about what is specific to the user's project. It includes (and was first built for) a complete transformation from ContentDM XML export.

== User Experiences ==


== Development Activity ==


Development stopped. Last commit was done in 2012-12-12.

Commits in SourceForge : https://sourceforge.net/p/seventrain/code/commit_browser

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

METS API

2020-07-07T12:29:05Z

Jukervin: Created tool page for METS API

{{Infobox_tool
|purpose=The METS API is a Java API designed to aid developers in the processing and assembly of METS Documents.
|homepage=https://sourceforge.net/projects/mets-api/
|license=Apache License V2.0
|platforms=Java
}}



[[Category:Metadata Processing]]


[[Category:METS]]

== Description ==

A Java API to aid developers in the building and processing of METS documents. The API wraps the SAX and w3c DOM libraries provided with Sun's Java JDK, making it simpler to focus on developing METS-oriented code as opposed to low-level XML document navigation.

== User Experiences ==


== Development Activity ==



Development stopped. Last code commit was done 2010-10-17.

Commits in SourceForge : https://sourceforge.net/p/mets-api/code/commit_browser

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

NumaHOP

2020-07-07T12:13:48Z

Jukervin: Added License

{{Infobox_tool
|purpose=Platform for digitization projects management
|image={{PAGENAMEE}}.png
|homepage=https://www.numahop.fr/
|license=GNU Affero General Public License v3.0
|platforms=
}}


[[Category:Quality Assurance]]
[[Category:OCR]]
[[Category:METS]]
[[Category:ALTO format]]

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

GitHub Commits : https://github.com/progilone/numahop/commits/master



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

NumaHOP

2020-07-07T12:10:25Z

Jukervin: Added OCR and ALTO Format category, Added link to GitHub commits.

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


[[Category:Quality Assurance]]
[[Category:OCR]]
[[Category:METS]]
[[Category:ALTO format]]

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

GitHub Commits : https://github.com/progilone/numahop/commits/master



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

Category:ALTO format

2020-07-03T10:40:51Z

Jukervin:

{{Infobox_content
|definition=Tools that support the creation, processing or displaying of data in ALTO XML format. It is mainly used for OCR data.
}}

ALTO (Analyzed Layout and Text Object) is a XML Schema that details technical metadata for describing the layout and content of physical text resources, such as pages of a book or a newspaper. It most commonly serves as an extension schema [https://www.loc.gov/standards/alto/techcenter/use-with-mets.html used with METS]. However, ALTO instances can also exist as a standalone document used independently of METS.

Each ALTO file contains a style section where different styles (for paragraphs and fonts) are listed. The layout section contains what’s on the page. A page is divided into several regions (Print space, left margin, right margin, top margin and bottom margin). For each region all objects are listed which have been detected inside.

More information at [https://www.loc.gov/standards/alto/ the official ALTO website] and [https://github.com/altoxml the official ALTO Github website].

Category:METS

2020-07-03T10:37:15Z

Jukervin:

{{Infobox_content
|definition=Tools that support the creation, processing and preservation of METS metadata.
}}

METS (Metadata Encoding and Transmission Standard) is a standard for encoding descriptive, administrative and structural metadata, and it is widely used e.g. in digital preservation. Please see [http://www.loc.gov/standards/mets/ the official METS website] and [https://github.com/mets the official METS Github website] for more information.

Greenstone

2020-07-03T09:20:35Z

Jukervin: Page Created

{{Infobox_tool
|purpose=A suite of software for building and distributing digital library collections
|homepage=http://www.greenstone.org/
|license=GPL 2
|platforms=Windows, Unix/Linux, and Mac OS-X
}}



[[Category:Access]]


[[Category:METS]]

== Description ==

Greenstone is a suite of software for building and distributing digital library collections. It is not a digital library but a tool for building digital libraries. The software provides a way of organizing information and publishing it on the Web in the form of a fully-searchable, metadata-driven digital resource. It can also be run in a non-networked environment (standalone), operating from removable media such as a USB Flash Drive and DVD. Greenstone has been developed and distributed in cooperation with UNESCO and the Human Info NGO in Belgium. It is open-source, multilingual software, issued under the terms of the GNU General Public License.

== User Experiences ==


== Development Activity ==



Commits : http://trac.greenstone.org/timeline

Issues : http://trac.greenstone.org/report/1?asc=0&sort=modified&USER=anonymous

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

Kraken

2020-07-03T08:19:43Z

Jukervin: /* Description */

{{Infobox_tool
|purpose=Open Source turn-key OCR system forked from ocropus
|homepage=http://kraken.re/
|license=Apache 2.0 License
|platforms=Linux
}}



[[Category:OCR]]


[[Category:ALTO format]]

== Description ==

kraken is a turn-key OCR system forked from [https://github.com/tmbarchive/ocropy ocropus]. It is intended to rectify a number of issues while preserving (mostly) functional equivalence.

'''main features:'''
*Script detection and multi-script recognition support
*Right-to-Left, BiDi, and Top-to-Bottom script support
*ALTO, abbyXML, and hOCR output
*Word bounding boxes and character cuts
*Public repository of model files
*Lightweight model files
*Variable recognition network architectures

All functionality not pertaining to OCR and prerequisite steps has been removed, i.e. no more error rate measuring, etc.

== User Experiences ==


== Development Activity ==



Commits : https://github.com/mittagessen/kraken/commits

Issues : https://github.com/mittagessen/kraken/issues

Kraken

2020-07-03T08:18:43Z

Jukervin:

{{Infobox_tool
|purpose=Open Source turn-key OCR system forked from ocropus
|homepage=http://kraken.re/
|license=Apache 2.0 License
|platforms=Linux
}}



[[Category:OCR]]


[[Category:ALTO format]]

== Description ==

kraken is a turn-key OCR system forked from ocropus. It is intended to rectify a number of issues while preserving (mostly) functional equivalence.

'''main features:'''
*Script detection and multi-script recognition support
*Right-to-Left, BiDi, and Top-to-Bottom script support
*ALTO, abbyXML, and hOCR output
*Word bounding boxes and character cuts
*Public repository of model files
*Lightweight model files
*Variable recognition network architectures

All functionality not pertaining to OCR and prerequisite steps has been removed, i.e. no more error rate measuring, etc.

== User Experiences ==


== Development Activity ==



Commits : https://github.com/mittagessen/kraken/commits

Issues : https://github.com/mittagessen/kraken/issues

Kraken

2020-07-03T08:17:29Z

Jukervin: Page Created

{{Infobox_tool
|purpose=Open Source OCR system forked from ocropus
|homepage=http://kraken.re/
|license=Apache 2.0 License
|platforms=Linux
}}



[[Category:OCR]]


[[Category:ALTO format]]

== Description ==

kraken is a turn-key OCR system forked from ocropus. It is intended to rectify a number of issues while preserving (mostly) functional equivalence.

'''main features:'''
*Script detection and multi-script recognition support
*Right-to-Left, BiDi, and Top-to-Bottom script support
*ALTO, abbyXML, and hOCR output
*Word bounding boxes and character cuts
*Public repository of model files
*Lightweight model files
*Variable recognition network architectures

All functionality not pertaining to OCR and prerequisite steps has been removed, i.e. no more error rate measuring, etc.

== User Experiences ==


== Development Activity ==



Commits : https://github.com/mittagessen/kraken/commits

Issues : https://github.com/mittagessen/kraken/issues

Create Validator (by CCS)

2020-07-03T07:54:28Z

Jukervin: Jukervin moved page Create Validator (by CCS) to Validator (by CCS): Mistake in name

#REDIRECT [[Validator (by CCS)]]

Talk:Main Page

2020-07-03T07:12:00Z

Jukervin: /* GitHub ATOM RSS feeds don't work */

==Use of Level 1 section headings ==
I just had a first stab at some editing an existing entry, and creating a new one. One small thing I noticed: all of the pages I've seen use Level 1 headings for the main sections, but this is discouraged by the MediaWiki documentation (esp. since Level 1 is already used for the main heading of each entry). See e.g. here:

http://www.mediawiki.org/wiki/Help_talk:Formatting#Level_1

And also:

http://www.mediawiki.org/wiki/Help:Formatting

So maybe it would be better to change those to level 2 (also in all cases I've seen the child sections use level 3 headings)? Not a big deal of course but it's a bit ugly and it's probably easier to fix this now than postponing it to a later stage (also existing entries will most likely be used as a template for creating new ones, so the problem will get progressively worse if left as it is). I suppose this is also something that might mess up attempts at automated text extraction. [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 14:58, 20 November 2013 (UTC)

: Good point - I didn't know about this recommendation. It should be possible to automated this transformation using the [https://www.mediawiki.org/wiki/Manual:Pywikibot Pywikibot] framework and the [https://pypi.python.org/pypi/mwparserfromhell mwparserfromhell]. We could change the [[Template:Tool/Preload|tool template]] now and use a bot to modify the rest? [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 15:15, 20 November 2013 (UTC)

::Great! It would also help to mention the template on the main page (I don't have edit rights there), as I didn't even know there was any! Anyway, I just updated the template myself.[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 16:07, 20 November 2013 (UTC)

::: I updated the main page to include an explicit link to the template that should be used when creating new Tool entries. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]])

==Purpose field in infobox==
Another thing I noticed is that for most entries the ''purpose'' field in the infobox more or less repeats what's already in the ''Description'' section. So maybe it's better to leave it out altogether (on the other hand it might be useful for automated discovery/analysis)? [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 14:58, 20 November 2013 (UTC)
: The intention was the other way around - that the 'purpose' field was a brief description that might be published and re-used in other forms (due to being in the infobox), and the Description section should be more detailed. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 15:15, 20 November 2013 (UTC)
:: Yes, that's what I thought as well. For some existing entries both are identical though, so it wasn't immediately clear. [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 15:56, 20 November 2013 (UTC)
::: I would say the goal is to improve the body Description section for those items. Is the Description in these cases exactly identical to the purpose? If so, I might be able to check for that automatically. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 21:18, 20 November 2013 (UTC)

==Perhaps rename Imaging category to Disk Imaging?==
Another thing: people might end up mixing up the ''Image'' and ''Imaging'' categories. Maybe rename the latter to ''Disk Imaging'' to avoid this?
[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 16:15, 20 November 2013 (UTC)
: Good idea. Unfortunately, I think that due to the way MediaWiki works, this means editing all the items tagged with that category (unless there's a trick I'm unaware of). However, perhaps I should tweak [[User:COPTR Bot|COPTR Bot]] to do this too. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 21:22, 20 November 2013 (UTC)
:: Fixed manually --[[User:Prwheatley|Prwheatley]] ([[User talk:Prwheatley|talk]]) 17:51, 26 November 2013 (UTC)

==Problems with login procedure (VeriSign)==
Having created an OpenID with Verisign, signing in to COPTR is a bit hit and miss. It always takes multiple attempts before I can successfully log in, and I first have to work myself through multiple authorization errors. Not clear to me whether the error is caused by COPTR or VeriSign, and results seem to be a bit random. Also after some time of inactivity I seem to get logged out automatically. Confusingly, the COPTR login status at the top right then shows I'm still logged in (depending on which page I'm on, it seems), and I have to go through the whole login procedure (including failures) again.
[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 11:16, 21 November 2013 (UTC)

: [http://meta.stackoverflow.com/a/1789 This StackOverflow answer] outlines some of the possible causes of problems with OpenID logins. I guess we could perhaps enable non-OpenID logins, although I wanted to avoid that for fear of making it even easier for the robots/spammers. Using Google as an OpenID provider is working fine for me. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 11:40, 21 November 2013 (UTC)

:: Hmm ... the StackOverflow page links to an OpenID checker, but I'm a bit scared of it because it exposes all the info you enter there to a publicly viewable log ... Not keen on using Google either, because they're, well ... Google. The main point of course is that the success of COPTR will depend completely on community involvement, and if the login procedure is already such a stumbling block that's not going to help there. Also the procedure to get the OpenID isn't terribly straightforward, and this will scare off potential contributors as well. So I would consider adding a non-OpenID login procedure, perhaps augmented with a CAPTCHA to keep the robots at bay (e.g. like the Archiveteam Formats Wiki). [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 12:28, 21 November 2013 (UTC)

::: Okay, I've enabled plain logins and registration. To make sure you retain the same user account, you should ensure it knows the right email address so you can use password recovery to login. Alternatively, I think you should be able to reset your PW from your Preferences page. The current setup is that you should see CAPTCHAs blocking all edits etc. unless you have confirmed your email address. We'll see how it goes, and if we have to tighten up things to avoid spam, so be it. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 12:45, 21 November 2013 (UTC)

::::Great, thanks for the quick response! Apparently there's no way to set a pw from the Preferences page once you have an existing OpenID assigned to your user profile, and when I try to delete my OpenID I get an error that this isn't possible because no password is set, classic Catch 22 there! Anyway, I'll stick with the OpenID madness for a bit and if I get really fed up with it I may well just create a new COPTR account, probably the easiest solution all around. [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 13:14, 21 November 2013 (UTC)

::::: I'm pretty sure that, if you completely log out first, and if there is an email associated with your account, you can use the 'Password reset' option to get access. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 15:28, 21 November 2013 (UTC)

== changing Open Planets Foundation to Open Preservation Foundation ==

Hi. The Main Page need some update (changing Open Planets Foundation to Open Preservation Foundation). I have of course not the permission to do that :-) . Thanks. [[User:Chlara|Chlara ]] ([[User talk:Chlara|talk]]) 10:18, 27 November 2014 (UTC)
* Good call, this is now fixed. Thanks!

== DSPS (Digital Preservation Software Platform) is the same as Digital Preservation Software Platform ==

Hi. I have updated the Digital Preservation Software Platform. After that I saw that there is a nearly same Page DSPS (Digital Preservation Software Platform). Due to the fact, that "DSPS (Digital Preservation Software Platform)" is the better title I have copied the content from Digital Preservation Software Platform into DSPS (Digital Preservation Software Platform). In the Page Digital Preservation Software Platform I replaced the content with a link to DSPS (Digital Preservation Software Platform).

Can you please delete the page Digital Preservation Software Platform.

Thanks. [[User:Chlara|Chlara ]] ([[User talk:Chlara|talk]]) 11:30, 8 January 2015 (UTC)

== Merging duplicate entries ==

I noticed that there are two entries for the CONTENTdm digital asset management system:

* http://coptr.digipres.org/ContentDM
* http://coptr.digipres.org/CONTENTdm

I removed the limited content from the ContentDM page and made it redirect to the CONTENTdm page, using the MediaWiki #redirect option (see [http://www.mediawiki.org/wiki/Help:Redirects http://www.mediawiki.org/wiki/Help:Redirects]. Should this be the recommended practice or would you rather simply delete one of the pages? If the latter, how to we request removal of a page?

[[User:Danielle Plumer|Danielle Plumer]] ([[User talk:Danielle Plumer|talk]]) 03:00, 5 February 2015 (UTC)

== Check this entries ==
==== Workflow ====
Hi. I Think the entrie http://coptr.digipres.org/Workflow:Workflow_for_ingesting_digitized_books_into_a_digital_archive need to be changed or deleted. What do you think about it? Thanks. [[User:Chlara|Chlara ]] ([[User talk:Chlara|talk]]) 06:19, 20 April 2017 (UTC)

== Change to https ==
Hi. COPTR should change to https. Thanks. --[[User:Chlara|Chlara ]] ([[User talk:Chlara|talk]]) 09:48, 14 September 2017 (UTC)

== GitHub ATOM RSS feeds don't work ==

Pages with RSS feed embeds show error messages like:

Below the last 5 commits: Failed to load RSS feed from https://github.com/intranda/goobi/commits/master.atom: Error fetching URL: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

Is this a server configuration problem on COPTR's end? Can it be corrected or should the GitHub feeds be removed from pages?
--[[User:Jukervin|Jukervin]] ([[User talk:Jukervin|talk]]) 07:12, 3 July 2020 (UTC)

Talk:Main Page

2020-07-03T07:10:55Z

Jukervin: /* GitHub ATOM RSS feeds don't work */ new section

Goobi

2020-07-03T07:05:15Z

Jukervin: Added category ALTO format

{{Infobox_tool
|purpose=Workflow Management Tool
|image={{PAGENAMEE}}.png
|homepage=http://www.intranda.com/goobi
|license=GPLv2
|platforms=Linux
}}

[[Category:Workflow]]
[[Category:OCR]]
[[Category:Planning]]
[[Category:Quality Assurance]]
[[Category:METS]]
[[Category:ALTO format]]

== Description ==
Goobi is a web based workflow management tool. It can be used to create manual, partly automatic or fully automatically workflows to validate, transform or enrich content.

== User Experiences ==
* http://www.intranda.com/en/uber-uns/referenzen/

== Development Activity ==

All development activity is visible on GitHub: http://github.com/intranda/goobi/commits

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

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

{{Infobox_tool_details
|ohloh_id=
}}

Tesseract-ocr

2020-07-03T07:00:32Z

Jukervin: Added links to GitHub source commits and issues.

{{Infobox_tool
|purpose=Open source OCR engine, accepting uncompressed TIFF files as input
|image=Tesseract.png
|homepage=https://github.com/tesseract-ocr/tesseract
|license=Apache 2.0 License EXCEPT the tesseractTrainer.py, which is licensed with GPL
|platforms=Linux, Windows, MacOSX
}}


[[Category:OCR]]
[[Category:ALTO format]]

= Description =
Tesseract is probably the most accurate open source OCR engine available. Combined with the [http://leptonica.com/ Leptonica Image Processing Library] it can read a wide variety of image formats and convert them to text in over 60 languages. It was one of the top 3 engines in the 1995 UNLV Accuracy test. Between 1995 and 2006 it had little work done on it, but since then it has been improved extensively by Google.

== Provider ==
Development of Tesseract is sponsored by Google. Its chief developer is [http://research.google.com/pubs/author4479.html Ray Smith].

==Licensing and cost==
Tesseract is an Open Source OCR engine, available under the [http://www.apache.org/licenses/LICENSE-2.0 Apache 2.0 license]. It can be used directly, or (for programmers) using an [https://github.com/tesseract-ocr/tesseract/blob/master/include/tesseract/baseapi.h API].

==History==
It was initially developed at HP during a 10 year period from 1984 to 1994. After a decade of minimal development it was released in 2005 for open source. Google acquired Tesseract in 2006 and currently maintains its development.

==Platform and interoperability==
*The latest downloads for Linux and Windows are found on [https://drive.google.com/folderview?id=0B7l10Bj_LprhQnpSRkpGMGV2eE0&usp=sharing GoogleDrive]. Older versions of Tesseract and its language packs are found on the discontinued [https://code.google.com/p/tesseract-ocr/downloads/list Google Code download page].
*The easiest way to install Tesseract on Mac OSX is with [https://www.macports.org/ MacPorts]. Once it is installed, you can install Tesseract by running the command ''sudo port install tesseract'', and any language with ''sudo port install tesseract-<langcode>''. A list of available langcodes can be found on the [https://www.macports.org/ports.php?by=name&substr=tesseract- MacPorts Tesseract page].
*Dependencies for running Tesseract include Autotools and [http://www.leptonica.org/ Leptonica] . The Windows version requires installation of [http://msdn.microsoft.com/en-us/vstudio/aa718325.aspx Visual Studio]. More information about required Ubantu libraries and links to specific requirements are on the [https://code.google.com/p/tesseract-ocr/wiki/Compiling Tesseract Wiki].
*Other programs such as Scan Tailor, unpaper, ImageJ, Gimp or ImageMagick may be needed to properly prepare images for use in Tesseract.

==Functional notes==
===Input supported===
Any image readable by Leptonica is supported in Tesseract including BMP, PNM, PNG, JFIF, JPEG, and TIFF.
GIF is not supported [http://www.leptonica.com/library-overview.html http://www.leptonica.com/library-overview.html].
===Output generated===
plain text, hOCR (HTML), PDF, invisible-text-only PDF, TSV and ALTO (XML)

==Documentation and support==
*Smith, Ray (2007). An Overview of the Tesseract OCR Engine [http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/33418.pdf http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/33418.pdf ]
*Installation information is found on the [https://code.google.com/p/tesseract-ocr/wiki/ReadMe ReadMe] page of the project site.
*Support is offered and issues are addressed on the [https://code.google.com/p/tesseract-ocr/issues/list Issues] page of the project site.

==Included in==
*Integration with the free [http://www.dcc.ac.uk/resources/external/xena-software-0 Xena-Digital Preservation Software][http://sourceforge.net/projects/xena/?source=navbar http://sourceforge.net/projects/xena/?source=navbar]
*Integration with Free Online OCR [http://www.free-ocr.com/faq.html http://www.free-ocr.com/faq.html]

==Usability==
*Tesseract was primarily developed for English OCR capability, but 47 language packs have been developed for use with other languages [https://tesseract-ocr.googlecode.com/svn/trunk/doc/tesseract.1.html https://tesseract-ocr.googlecode.com/svn/trunk/doc/tesseract.1.html]. Tesseract 2.0x and 3.0x are [https://code.google.com/p/tesseract-ocr/wiki/TrainingTesseract3 trainable] for other languages.
*There is no built-in GUI, but there are several available from the [https://code.google.com/p/tesseract-ocr/wiki/3rdParty 3rdParty] page.

= User Experiences =
*Lazorchak, Butch. (2014). Making Scanned Content Accessible Using Full-text Search and OCR [http://blogs.loc.gov/digitalpreservation/2014/08/making-scanned-content-accessible-using-full-text-search-and-ocr/ http://blogs.loc.gov/digitalpreservation/2014/08/making-scanned-content-accessible-using-full-text-search-and-ocr/]
*Texas A&M University. (2012-). Early Modern OCR Project Workflow [http://emop.tamu.edu/about http://emop.tamu.edu/about http://emop.tamu.edu/about http://emop.tamu.edu/about]
*Adams, Chris. (2014). Content Search on a Budget-using Tesseract on large TIFF files [http://chris.improbable.org/2014/3/17/content-search-on-a-budget/ http://chris.improbable.org/2014/3/17/content-search-on-a-budget/]
*PSNC Digital Libraries Team. (2011). Tesseract 3.0 installation on Ubuntu 10.10 server [http://dl.psnc.pl/2011/01/24/tesseract-3-0-installation-on-ubuntu-10-10-server/ http://dl.psnc.pl/2011/01/24/tesseract-3-0-installation-on-ubuntu-10-10-server/]
*Lacy, David. (2014). Digital Library upgrade provides enhanced discovery [http://blog.library.villanova.edu/digitallibrary/2014/02/18/digital-library-upgrade-provides-enhanced-discovery/#sthash.OwCtLlEc.dpuf http://blog.library.villanova.edu/digitallibrary/2014/02/18/digital-library-upgrade-provides-enhanced-discovery/#sthash.OwCtLlEc.dpuf]
*Applied in an AQuA Mashup that resulted in the Solution page: [http://wiki.opf-labs.org/display/AQuA/Compare+OCR+results+of+the+same+source+material+in+different+formats+%28TIFF%2C+JP2%29 Compare OCR results of the same source material in different formats (TIFF, JP2)]

= Development Activity =
Source Commits : [https://github.com/tesseract-ocr/tesseract/commits https://github.com/tesseract-ocr/tesseract/commits]

Issues : https://github.com/tesseract-ocr/tesseract/issues

{{Infobox_tool_details
|ohloh_id=tesseract-ocr
}}

Tesseract-ocr

2020-07-03T06:45:49Z

Jukervin: Updated Output formats. Removed dead development RSS feeds. Replacement GitHub atom feeds don't seem to work https://github.com/tesseract-ocr/tesseract/commits/master.atom

Tesseract-ocr

2020-07-03T06:40:34Z

Jukervin: Updated homepage link to Github. Added category ALTO format

{{Infobox_tool
|purpose=Open source OCR engine, accepting uncompressed TIFF files as input
|image=Tesseract.png
|homepage=https://github.com/tesseract-ocr/tesseract
|license=Apache 2.0 License EXCEPT the tesseractTrainer.py, which is licensed with GPL
|platforms=Linux, Windows, MacOSX
}}


[[Category:OCR]]
[[Category:ALTO format]]

= Description =
Tesseract is probably the most accurate open source OCR engine available. Combined with the [http://leptonica.com/ Leptonica Image Processing Library] it can read a wide variety of image formats and convert them to text in over 60 languages. It was one of the top 3 engines in the 1995 UNLV Accuracy test. Between 1995 and 2006 it had little work done on it, but since then it has been improved extensively by Google.

== Provider ==
Development of Tesseract is sponsored by Google. Its chief developer is [http://research.google.com/pubs/author4479.html Ray Smith].

==Licensing and cost==
Tesseract is an Open Source OCR engine, available under the [http://www.apache.org/licenses/LICENSE-2.0 Apache 2.0 license]. It can be used directly, or (for programmers) using an [https://github.com/tesseract-ocr/tesseract/blob/master/include/tesseract/baseapi.h API].

==History==
It was initially developed at HP during a 10 year period from 1984 to 1994. After a decade of minimal development it was released in 2005 for open source. Google acquired Tesseract in 2006 and currently maintains its development.

==Platform and interoperability==
*The latest downloads for Linux and Windows are found on [https://drive.google.com/folderview?id=0B7l10Bj_LprhQnpSRkpGMGV2eE0&usp=sharing GoogleDrive]. Older versions of Tesseract and its language packs are found on the discontinued [https://code.google.com/p/tesseract-ocr/downloads/list Google Code download page].
*The easiest way to install Tesseract on Mac OSX is with [https://www.macports.org/ MacPorts]. Once it is installed, you can install Tesseract by running the command ''sudo port install tesseract'', and any language with ''sudo port install tesseract-<langcode>''. A list of available langcodes can be found on the [https://www.macports.org/ports.php?by=name&substr=tesseract- MacPorts Tesseract page].
*Dependencies for running Tesseract include Autotools and [http://www.leptonica.org/ Leptonica] . The Windows version requires installation of [http://msdn.microsoft.com/en-us/vstudio/aa718325.aspx Visual Studio]. More information about required Ubantu libraries and links to specific requirements are on the [https://code.google.com/p/tesseract-ocr/wiki/Compiling Tesseract Wiki].
*Other programs such as Scan Tailor, unpaper, ImageJ, Gimp or ImageMagick may be needed to properly prepare images for use in Tesseract.

==Functional notes==
===Input supported===
Any image readable by Leptonica is supported in Tesseract including BMP, PNM, PNG, JFIF, JPEG, and TIFF.
GIF is not supported [http://www.leptonica.com/library-overview.html http://www.leptonica.com/library-overview.html].
===Output generated===
Tesseract outputs to TXT. PDF output was added in version 3.03.

==Documentation and support==
*Smith, Ray (2007). An Overview of the Tesseract OCR Engine [http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/33418.pdf http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/33418.pdf ]
*Installation information is found on the [https://code.google.com/p/tesseract-ocr/wiki/ReadMe ReadMe] page of the project site.
*Support is offered and issues are addressed on the [https://code.google.com/p/tesseract-ocr/issues/list Issues] page of the project site.

==Included in==
*Integration with the free [http://www.dcc.ac.uk/resources/external/xena-software-0 Xena-Digital Preservation Software][http://sourceforge.net/projects/xena/?source=navbar http://sourceforge.net/projects/xena/?source=navbar]
*Integration with Free Online OCR [http://www.free-ocr.com/faq.html http://www.free-ocr.com/faq.html]

==Usability==
*Tesseract was primarily developed for English OCR capability, but 47 language packs have been developed for use with other languages [https://tesseract-ocr.googlecode.com/svn/trunk/doc/tesseract.1.html https://tesseract-ocr.googlecode.com/svn/trunk/doc/tesseract.1.html]. Tesseract 2.0x and 3.0x are [https://code.google.com/p/tesseract-ocr/wiki/TrainingTesseract3 trainable] for other languages.
*There is no built-in GUI, but there are several available from the [https://code.google.com/p/tesseract-ocr/wiki/3rdParty 3rdParty] page.

= User Experiences =
*Lazorchak, Butch. (2014). Making Scanned Content Accessible Using Full-text Search and OCR [http://blogs.loc.gov/digitalpreservation/2014/08/making-scanned-content-accessible-using-full-text-search-and-ocr/ http://blogs.loc.gov/digitalpreservation/2014/08/making-scanned-content-accessible-using-full-text-search-and-ocr/]
*Texas A&M University. (2012-). Early Modern OCR Project Workflow [http://emop.tamu.edu/about http://emop.tamu.edu/about http://emop.tamu.edu/about http://emop.tamu.edu/about]
*Adams, Chris. (2014). Content Search on a Budget-using Tesseract on large TIFF files [http://chris.improbable.org/2014/3/17/content-search-on-a-budget/ http://chris.improbable.org/2014/3/17/content-search-on-a-budget/]
*PSNC Digital Libraries Team. (2011). Tesseract 3.0 installation on Ubuntu 10.10 server [http://dl.psnc.pl/2011/01/24/tesseract-3-0-installation-on-ubuntu-10-10-server/ http://dl.psnc.pl/2011/01/24/tesseract-3-0-installation-on-ubuntu-10-10-server/]
*Lacy, David. (2014). Digital Library upgrade provides enhanced discovery [http://blog.library.villanova.edu/digitallibrary/2014/02/18/digital-library-upgrade-provides-enhanced-discovery/#sthash.OwCtLlEc.dpuf http://blog.library.villanova.edu/digitallibrary/2014/02/18/digital-library-upgrade-provides-enhanced-discovery/#sthash.OwCtLlEc.dpuf]
*Applied in an AQuA Mashup that resulted in the Solution page: [http://wiki.opf-labs.org/display/AQuA/Compare+OCR+results+of+the+same+source+material+in+different+formats+%28TIFF%2C+JP2%29 Compare OCR results of the same source material in different formats (TIFF, JP2)]

= Development Activity =

==Google Code Source Feed==
Below the last 5 source updates:
<rss max=5>https://code.google.com/feeds/p/tesseract-ocr/gitchanges/basic</rss>
==Google Code Wiki Feed==
Below are the last 3 wiki updates:
<rss max=3>https://code.google.com/feeds/p/tesseract-ocr/gitchanges/basic?repo=wiki</rss>
==Google Code Issue Feed==
Below are the last 3 issue updates:
<rss max=3>https://code.google.com/feeds/p/tesseract-ocr/issueupdates/basic</rss>

{{Infobox_tool_details
|ohloh_id=tesseract-ocr
}}

CONTENTdm

2020-07-03T06:23:18Z

Jukervin: Updated external links. Added category ALTO format

{{Infobox_tool
|purpose=CONTENTdm is a digital collection management system
|image=
|homepage=https://www.oclc.org/en/contentdm.html
|license=
|platforms=
}}


[[Category:Preservation System]]
[[Category:METS]]
[[Category:ALTO format]]

= Description =
[https://www.oclc.org/en/contentdm.html CONTENTdm] is a software solution that handles the storage, management, and delivery of library digital collection to the web by providing access to web-based digital collection tool where data and digital items are prepared in large batches, a server where data and images are stored and can be edited, a Web-based discovery interface optimized for customization, self-service tool to upload the metadata of your digital content to WorldCat using the Digital Collection Gateway, and integration with OCLC products for building collections with cataloging workflows, as well as the option of harvesting from the Web sites and adding long-term preservation. Developed by OCLC. A hosted version is available.
====Provider====
OCLC
====Licensing and cost====
CONTENTdm uses fee-based licenses for both the software and the hosting service; a range of optional services and tools is available as well. Pricing is unclear on the OCLC website.  
====Development activity====
CONTENTdm version 6.9 was released in November 2014.
OCLC is a self-funded not-for-profit organisation; CONTENTdm is one of their core services, receiving ongoing development and support.

====Platform and interoperability====
CONTENTdm Server runs on IIS with Windows 2008 or Apache with Linux (requires PHP 5.3). The CONTENTdm website has similar requirements. The software was designed to integrate with other OCLC products, including Connexion and Web Harvester. The CONTENTdm Project Client requires the Microsoft .NET Framework 3.5 or higher running on Windows P SP2 or later.
CONTENTdm offers an API to allow users to customise their workflows and extend website functionality.
====Functional notes====
Some licenses include an OCR Extension to generate full-text transcripts, and an Image Rights tool to designate ownership of items in the collection. The customisable web access platform integrates with OCLC’s WorldCat to promote greater discoverability. Collections can be stored on distributed drives, enabling collaboration between organisations.
====Documentation and user support====
Email- and telephone-based user support is included in the licensing fee. Users are also granted access to a [https://help.oclc.org/Metadata_Services/CONTENTdm User Support Center] with installation guides, Help files, tutorials and a Support FAQ. The Center also supports forums and blogs for the CONTENTdm community.
====Usability====
CONTENTdm provides a web-based administration interface, and includes number of options for managing and adding content to collections. For its latest iteration, extensive usability testing was conducted as part of a user-centered design approach.
====Expertise required====
If an organisation wishes to host its own server, installation and configuration will require system administration knowledge.
====Standards compliance====
CONTENTdm heavily advertises its standards compliance in a number of arenas: supporting Unicode for character display; offering Dublin Core, VRA Core, and METS/ALTO for metadata assignment; serving as an OAI repository for those who wish to make their metadata available for harvesting; and supporting Z39.50 for search and retrieval.
====Influence and take-up====
The CONTENTdm website advertises use by over 2,000 organizations, including public libraries, academic libraries, historical societies, and museums.

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=CONTENTdm
}}

Docworks

2020-07-03T06:13:55Z

Jukervin:

{{Infobox_tool
|purpose=Document digitization workflow software
|homepage=https://content-conversion.com/#docworks-2
|license=Commercial
|platforms=Windows
}}



[[Category:OCR]]
[[Category:Workflow]]
[[Category:Quality Assurance]]


[[Category:Image]]
[[Category:METS]]
[[Category:ALTO format]]

== Description ==

docWorks helps archives and content owners to convert their print holdings into professional digital libraries. This process consists of two steps: the digitization, i.e. the scanning of the printed page, and the conversion, i.e. the recognition of all contained text, image, layout and structural information.

docWorks is a conversion software that covers all conversion steps in a single workflow. It provides layout analysis and offers multiple OCR engines to handle any type of publication, language or writing system.

Import formats are TIF, JPG, JP2, GIF and PDF and you can export METS and ALTO XML, image files, PDF, PDF/A-1, full-text XML, RTF and EPUB.
Metadata schemes are MIX, MARC, MODS, DC, METS physical structural maps and METS logical structural maps.

== User Experiences ==


== Development Activity ==

Category:ALTO format

2020-07-03T06:12:23Z

Jukervin: Category ALTO format created.

[[Category:Content Type]]
{{Infobox_content
|definition=Tools that support the creation, processing or displaying of data in ALTO XML format. It is mainly used for OCR data.
}}

ALTO (Analyzed Layout and Text Object) is a XML Schema that details technical metadata for describing the layout and content of physical text resources, such as pages of a book or a newspaper. It most commonly serves as an extension schema [https://www.loc.gov/standards/alto/techcenter/use-with-mets.html used with METS]. However, ALTO instances can also exist as a standalone document used independently of METS.

Each ALTO file contains a style section where different styles (for paragraphs and fonts) are listed. The layout section contains what’s on the page. A page is divided into several regions (Print space, left margin, right margin, top margin and bottom margin). For each region all objects are listed which have been detected inside.

More information at [https://www.loc.gov/standards/alto/ the official ALTO website] and [https://github.com/altoxml the official ALTO Github website].

Docworks

2020-07-02T18:45:03Z

Jukervin:

{{Infobox_tool
|purpose=Document digitization workflow software
|homepage=https://content-conversion.com/#docworks-2
|license=Commercial
|platforms=Windows
}}



[[Category:OCR]]
[[Category:Workflow]]
[[Category:Quality Assurance]]


[[Category:Image]]
[[Category:METS]]

== Description ==

docWorks helps archives and content owners to convert their print holdings into professional digital libraries. This process consists of two steps: the digitization, i.e. the scanning of the printed page, and the conversion, i.e. the recognition of all contained text, image, layout and structural information.

docWorks is a conversion software that covers all conversion steps in a single workflow. It provides layout analysis and offers multiple OCR engines to handle any type of publication, language or writing system.

Import formats are TIF, JPG, JP2, GIF and PDF and you can export METS and ALTO XML, image files, PDF, PDF/A-1, full-text XML, RTF and EPUB.
Metadata schemes are MIX, MARC, MODS, DC, METS physical structural maps and METS logical structural maps.

== User Experiences ==


== Development Activity ==

Docworks

2020-07-02T18:44:33Z

Jukervin:

{{Infobox_tool
|purpose=Document digitization workflow software
|homepage=https://content-conversion.com/#docworks-2
|license=Commercial
|platforms=Windows
}}



[[Category:OCR]]
[[Category:Workflow]]
[[Category:Quality Assurance]]


[[Category:Image]]
[[Category:METS]]

== Description ==

docWorks helps archives and content owners to convert their print holdings into professional digital libraries. This process consists of two steps: the digitization, i.e. the scanning of the printed page, and the conversion, i.e. the recognition of all contained text, image, layout and structural information.

docWorks is a conversion software that covers all conversion steps in a single workflow. It provides layout analysis and offers multiple OCR engines to handle any type of publication, language or writing system.

Import formats are TIF, JPG, JP2, GIF and PDF and you can export METS and ALTO XML, image files, PDF, PDF/A-1, full-text XML, RTF and EPUB.
Metadata schemes are MIX, MARC, MODS, DC, METS physical structural maps and METS logical structural maps.

== User Experiences ==


== Development Activity ==
<-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. -->

Docworks

2020-07-02T18:43:59Z

Jukervin: docWorks page created

{{Infobox_tool
|purpose=Document digitization workflow software
|homepage=https://content-conversion.com/#docworks-2
|license=Commercial
|platforms=Windows
}}



[[Category:OCR]]
[[Category:Workflow]]
[[Category:Quality Assurance]]


[[Category:Image]]
[[Category:METS]]

== Description ==

docWorks helps archives and content owners to convert their print holdings into professional digital libraries. This process consists of two steps: the digitization, i.e. the scanning of the printed page, and the conversion, i.e. the recognition of all contained text, image, layout and structural information.

docWorks is a conversion software that covers all conversion steps in a single workflow. It provides layout analysis and offers multiple OCR engines to handle any type of publication, language or writing system.

Import formats are TIF, JPG, JP2, GIF and PDF and you can export METS and ALTO XML, image files, PDF, PDF/A-1, full-text XML, RTF and EPUB.
Metadata schemes are MIX, MARC, MODS, DC, METS physical structural maps and METS logical structural maps.

== User Experiences ==


== Development Activity ==
Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. -->

JHOVE2

2020-07-02T18:26:37Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=JHOVE2 allows data curators to characterise the digital objects in their repositories.
|image=
|homepage=http://jhove2.org/
|license=JHOVE2 is made freely available under the termsof the BSD open source license for all project-developed code; some third-party libraries may be covered by other open source licences.
|platforms=
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:File Format Identification]]
[[Category:Encryption Detection]]
[[Category:METS]]

= Description =
[https://bitbucket.org/jhove2/main/wiki/Home JHOVE2] is a follow-on to the Harvard/JSTOR [[JHOVE (Harvard Object Validation Environment)| JHOVE]] project, with the similar purpose of allowing data curators to characterise the digital objects in their repositories.  Characterisation is comprised of four elements: first, identifying the object’s format; second, validating that the object conforms to its format’s technical norms; third, extracting technical metadata from the object; and fourth, assessing whether the object should be accepted into a repository, based on policies set by the curator.  
The software was designed to be able to integrate with other applications to enable easy incorporation into a repository’s Ingest workflow.
====Provider====
California Digital Library, Portico, and Stanford University, with funding from the National Digital Information Infrastructure and Preservation Program (NDIIPP). Version 2.1 also credits the Bibliothèque nationale de France and Netarkivet.
====Licensing and cost====
Open Source [http://www.linfo.org/bsdlicense.html BSD license] – free.
====Development activity====
JHOVE2 version 2.1 was released in March 2013.
Funding for the JHOVE2 project ended in 2011. The project partners committed to providing self-funded maintenance (but not further development effort) for three years. Their goal was to create an open-source community to guide and foster JHOVE2 technical development, and the involvement of Bibliothèque nationale de France and Netarkivet from version 2.1 signifies some success in this regard.
====Platform and interoperability====
JHOVE2 is written in Java Standard Edition 6, and requires a Java 6 runtime environment.  If the user is hoping to use the SGML validation module, an OpenSP SGML parser is required.
Developers wishing to rebuild JHOVE2 from the provided source will need a full Java SE 6 development kit and the Apache Maven project tool.
====Functional notes====
The JHOVE2 project came about as a response to perceived shortcomings in the [[JHOVE (Harvard Object Validation Environment)| JHOVE]] software. JHOVE2 separates identification from validation, allowing the software to identify objects even if they are not valid.  This also provides the opportunity to use the [http://www.dcc.ac.uk/resources/external/pronom PRONOM] registry in signature-based identification via integration with [[DROID_(Digital_Record_Object_Identification)|DROID]], creating the ability to identify many more format-types than those for which it has validation modules. Other improvements include the ability to characterize hierarchical digital objects such as directories, zip files and bit streams nested within files, and a design that allows easier integration with other applications.
JHOVE2 has validation modules for the following format types: ICC color profile; SGML; Shapefile; TIFF (including TIFF/EP, TIFF-FX, TIFF/IT, Exif, GeoTIFF, DNG and RFC 1314); UTF-8 encoded text; WAVE (including Broadcast Wave); XML; ZIP; GZIP; ARC; WARC; and arbitrary bytestreams, filesets and directories. Modules for JPEG 2000 (JP2 and JPX profiles) and PDF (including PDF/X and PDF/A) were planned but have not been implemented yet.  
For comparison, ICC, SGML, Shapefile, ZIP, GZIP, ARC and WARC are newly supported in JHOVE2; however, JHOVE supports AIFF, GIF, JPEG, JPEG2000 and PDF while JHOVE2 does not.  HTML is also not supported in JHOVE2, as it is in JHOVE, but since HTML can be expressed in terms of SGML or XML the functionality remains the same. 
====Documentation and user support====
JHOVE2’s website includes an informative FAQ introduction, as well as standard documentation such as a [https://bytebucket.org/jhove2/main/wiki/documents/JHOVE2-Users-Guide_20110222.pdf user guide] and [https://bytebucket.org/jhove2/main/wiki/documents/JHOVE2Programmer2-0-0.pdf programmer guide].  
Primary user support is through the jhove2-techtalk-l listserv, which remains active as of June 2013.  In addition, the website includes an issue tracker displaying reported bugs and feature enhancement requests. 
====Usability====
JHOVE2 does not include a GUI, which will be challenging for many users.
The default output (e. g. in xml, txt or json) is very talkative and can contain up to 3500 lines for one TIFF file.
====Expertise required====
Installation requires solid knowledge of command line interfaces and experience with manually editing configuration files. Creation of the assessment policies requires detailed knowledge of digital preservation standards and technologies.  
====Standards compliance====
JHOVE2 uses the PRONOM registry for file identification.  The software includes a stylesheet that can transform JHOVE2 outputs into the METS metadata standard.
====Influence and take-up====
As of July 2013, the website reports approximately 1000 downloads of version 2 and 200 of version 2.1.

= User Experiences =
Please note that JHOVE2 cannot cope with any empty spaces in the command line. Therefor, JHOVE2 has to be stored in a folder which can be typed in without any empty space.

As the output is extremely wordy and contains so much information that it is difficult to tell if a certain TIFF file is valid or not, it might be helpfull to configure the output options. This is possible in the sgml-file. It might proove to be difficult for the average non-SGML-expert to handle the file.

= 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>http://bitbucket.org/jhove2/main/rss</rss>

{{Infobox_tool_details
|ohloh_id=JHOVE2
}}

Archivists' Toolkit

2020-07-02T18:01:34Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=The Archivists? Toolkit?, or the AT, is the first open source archival data management system to provide broad, integrated support for the management of archives.
|image=
|homepage=http://archiviststoolkit.org/download/release/2_0.html
|license=Educational Community License version 1.0
|platforms=
}}


[[Category:Metadata Processing]]
[[Category:METS]]

= Description =
The Archivists? Toolkit?, or the AT, is the first open source archival data management system to provide broad, integrated support for the management of archives. Currently, the application supports accessioning and describing archival materials; establishing names and subjects associated with archival materials, including the names of donors; managing locations for the materials; and exporting EAD finding aids, MARCXML records, and METS, MODS and Dublin Core records. Developed by UCSD Libraries. The project began in early 2004 and its second phase concluded at the end of September 2009.

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=Archivists' Toolkit
}}

ArchivesSpace

2020-07-02T17:30:21Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=ArchivesSpace is the next-generation web-based archives information management system, designed by archivists and supported by diverse archival repositories.
|image=
|homepage=http://www.archivesspace.org/
|license=Educational Community License, version 2.0.
|platforms=
}}



[[Category:Access]]
[[Category:Metadata Processing]]


[[Category:METS]]

== Description ==

ArchivesSpace is an open source, web application for managing archives information. The application is designed to support core functions in archives administration such as accessioning; description and arrangement of processed materials including analog, hybrid, and born-digital content; management of authorities (agents and subjects) and rights; and reference service. The application supports collection management through collection management records, tracking of events, and a growing number of administrative reports. The application also functions as a metadata authoring tool, enabling the generation of EAD, MARCXML, MODS, Dublin Core, and METS formatted data.

ArchivesSpace dates from June 2009 when representatives of New York University, the University of Illinois Urbana-Champaign, the University of California San Diego, and the Andrew W. Mellon Foundation agreed to integrate the Archivists' Toolkit and Archon into a single application in order to increase overall functionality within a single application and to optimize sustainability of the application. The Andrew W. Mellon Foundation provided generous funding for the first two phases of the ArchivesSpace program. A planning phase ran from January 2010 to June 2011, during which functional specifications were drafted, a business plan was formulated, and an organizational home was secured. A development phase ran from July 2011 to September 2013, culminating in the release of ArchivesSpace 1.0 on September 30, 2013. There have been nine releases of ArchivesSpace since the 1.0 release, all of which have served to both advance the integration of the Archivists' Toolkit and Archon and to introduce new functionality not present in either of those precursor applications. Source: http://archivesspace.org/overview

== User Experiences ==


== Development Activity ==

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

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

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


{{Infobox_tool_details
|ohloh_id=
}}

SobekCM

2020-07-02T17:17:23Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=SobekCM is a digital repository and digital scholarship/publishing system which enables easy deposit, preservation, and access for all types of digital content, tailored to the needs of galleries, libraries, archives, museums, scholars, and researchers.
|homepage=http://sobekrepository.org
|license=GNU GPL license
|platforms=
}}

[[Category:Access]]
[[Category:Discovery]]
[[Category:Metadata Processing]]
[[Category:Preservation System]]
[[Category:Quality Assurance]]
[[Category:METS]]

= Description =
The SobekCM Open Source Software is a software engine with related tools that power many institutional repositories and digital collections, small through large collaborative digital libraries including international collaborative programs like the [http://dloc.com Digital Library of the Caribbean (dLOC)], and digital scholarship projects, including Digital Humanities, Data Curation, and more. SobekCM has an active development and user community contributing to further develop tools and resources, as well as a number of current and planned grant projects which add more functionality.

= User Experiences =
* Reviews of SobekCM are available on [http://sourceforge.net/projects/sobekcm/ SobekCM on SourceForge], from the State University Libraries of Florida use SobekCM and the SobekCM METS Editor for archival package preparation to the [http://daitss.fcla.edu/content/new-version-sobekcm-mets-editor-released-version-104 DAITSS system], and see the [http://www.dloc.com/AA00016535/00001/pdf select bibliography] on the [http://dloc.com Digital Library of the Caribbean (dLOC)] which includes reviews of the software and analysis of the system for functional and non-functional requirements.

= Development Activity =

SobekCM is on [https://github.com/MarkVSullivan/SobekCM-Web-Application GitHub]. The University of Florida, a major contributor to SobekCM by a team in the UF Libraries, tracks and reports on recent enhancements and related activities (trainings, webinars, publications and presentations featuring SobekCM, etc.) on the [http://ufdc.ufl.edu/sobekcm/development/highlightsSobekCM list of recent enhancements].

====Release Feed====
Below the last 3 release feeds:
<rss max=3>https://github.com/MarkVSullivan/SobekCM-Web-Application/releases.atom</rss>

====Activity Feed====
Below the last 5 activity feeds:
<rss max=5>https://github.com/MarkVSullivan/SobekCM-Web-Application/commits/master.atom</rss>

{{Infobox_tool_details
|ohloh_id=sobekcm-web-application
}}

Rosetta

2020-07-02T17:16:21Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=Ex Libris Rosetta enables institutions to preserve and provide access to the collections in their care.
|image=
|homepage=http://www.exlibrisgroup.com/category/RosettaOverview
|license=Commercially licensed product.
|platforms=
}}


[[Category:Preservation System]]
[[Category:Access]]
[[Category:Metadata Processing]]
[[Category:File Format Migration]]
[[Category:METS]]

== Description ==
Designed in collaboration with the National Library of New Zealand and reviewed by an international peer group of recognized leaders and innovators, Ex Libris Rosetta enables institutions to preserve and provide access to the collections in their care, now and in the future.

Rosetta is a complete preservation solution. Its focus is to archive and preserve the digitized and born digital materials stored at academic and memory institutions like libraries and archives, research organizations and government institutions.
It aims to ensure data integrity and access over time for the archived digital data.

Rosetta supports the acquisition, validation, ingest, storage, preservation and dissemination of digitale objects that are in various formats and originate from many sources.

Rosetta uses standards like Premis and Mets. The METS profile of Ex Libris is published and open. Tehe data model of Rosetta is as following:

* intellectual entity (coherent set of content, the whole unit like e. g. a digitized book)
* representation (the set of files, including all the metadata)
* file
* bit-stream

Tools integrated in Rosetta
* BIRT (open source, eclipse-based Business Intelligence and Reporting Tools reporting system)
* thanks to a SDK, Rosetta users can easily build their own tools, submission applications and plug-ins
* Pronom connection

Rosetta is an OAIS-compliant solution.

== User Experiences ==


== Development Activity ==

Rescarta

2020-07-02T17:15:07Z

Jukervin: Fix METS Category location

{{Infobox_tool
|purpose=The ResCarta Tools software empowers users to create non-proprietary digital objects with LOC standard METS, MODS, MIX and AudioMD metadata from existing TIFF, JPEG, PDF and WAV data through user-friendly interfaces. Digital collections can be created, indexed, displayed and validated using the software. Exports DC, OAI_DC formats for use in OAI/PMH servers.
|image=
|homepage=http://www.ResCarta.org
|license=Apache License v2.0
|platforms=Linux, Windows, and OSX operating systems
}}


[[Category:Preservation System]]
[[Category:Access]]
[[Category:Personal Archiving]]


[[Category:Audio]]
[[Category:Document]]
[[Category:Research Data]]
[[Category:METS]]

== Description ==

ResCarta Toolkit allows users to create digital archives from scans, digital photographs or recordings of analog objects. Metadata is added using simple forms and is written into each digital object to Library of Congress Standards of METS, MODS, MIX, and AudioMD. Audio files containing spoken words can be automatically transcribed. Textural content of documents and audio can be edited to create highly accurate transcriptions using graphical tools. Standard directory and file naming is produced during use. A complete Lucene tm index of metadata and textural content can be created for use in a fully functional web application for discovery and display of digital objects. A checksum validation tool is included to assure long term stability of the archive.

====Platform====
The ResCarta Toolkit runs on Windows, Mac and Linux operating systems in single user or coordinated multiuser mode.

== User Experiences ==

* https://sourceforge.net/projects/rescarta/reviews?source=navbar

== Development Activity ==

Years of archived releases can be found at...
http://sourceforge.net/projects/rescarta/files/ResCarta%20Tools/


{{Infobox_tool_details
|ohloh_id=rescarta
}}

Roda

2020-07-02T17:13:56Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=RODA - Repository of Authentic Digital Objects
|image=RODA-logo-basic.png
|homepage=http://www.roda-community.org
|license=LGPL v3
|platforms=Server runs on Linux. Client runs on any web browser.
}}



[[Category:Preservation System]]


[[Category:Preservation System]]
[[Category:METS]]

== Description ==

RODA is a digital repository created in conjunction with the Portuguese National Archives. Its primary objective is to allow long-term preservation and authenticity of digital objects of national importance. Based as much as possible on standards, following international specifications to become a trustworthy repository, as the OAIS/TRAC, and having high standards of security and scalability. The user interface was also an important consideration, as it was designed for archivists, producers, and consumers.

=== Features ===

RODA is a complete digital repository that delivers functionality for all the main units of the OAIS reference model. RODA is capable of ingesting, managing and providing access to the various types of digital content produced by large corporations or public bodies. RODA is based on open-source technologies and is supported by existing standards such as the OAIS, METS, EAD and PREMIS.

* '''Conforms to open standards''' - RODA follows open standards using EAD for description metadata, PREMIS for preservation metadata, METS for structural metadata, and several standards for technical metadata (e.g. NISO Z39.87 for digital still images).
* '''Vendor independent''' - RODA is 100% built on top of open-source technologies. The entire infrastructure required to support RODA is vendor independent. This means that you may use the hardware and Linux distributions that best fit your institutional needs.
* '''Scalable''' - The service-oriented nature of RODA's architecture allows the system to be highly scalable, enabling the distribution of the processing load between several servers. Furthermore, new developments are in the works to enable RODA's preservation actions to be run over Hadoop clusters for even greater performance.
* '''Embedded preservation actions''' - Preservation actions and management within RODA is handled by a task scheduler. The task scheduler allows the administrator to define the set of rules that trigger specific actions, and when these should take place. Preservation actions include format conversions, checksum verifications, reporting (e.g. to automatically send SIP acceptance/rejection emails), notification events, etc.
* '''Authenticity''' - RODA uses preservation metadata (PREMIS) to create a trust chain between all format migrations and content verifications. The preservation metadata, together with the establishment of trust of its surrounding environment (ISO 16363) ensures reliability of the service and authenticity of the enclosed digital records.
* '''Support for multiple formats''' - RODA is capable of ingesting and normalizing (according to the preservation plan in place) text documents, raster images, relational databases, video, and audio. A plug-in mechanism enables RODA to easily support additional formats.
* '''Copes with the rapid changing nature of technology''' - The plug-in and task scheduling mechanism allows an easy way to add more functionality to the system (e.g. new preservation events, alerts, tools, etc.). Also, the service oriented architecture allows RODA base components to be incrementally updated, allowing a heterogeneous use of technologies at all levels: hardware, OS and applications.
* '''Advanced access control''' - Users must be authenticated before accessing the repository. All user actions are logged for future accountability. Permissions are granular and can be defined at repository level, all the way down to individual data objects.
* '''Integration with 3rd party systems''' - RODA exposes all its functionality via Web Services. Convenient Java libraries are available to allow developers to interact with RODA via its Core APIs. Several tools exist to create and manipulate the SIPs and submit them to RODA's ingest workflow.
* '''Advanced ingest workflow''' - RODA supports the ingest of new digital material as well as associated metadata in 4 distinct ways: 1) online submission (self-archiving), 2) off-line submission using an client application called “RODA-in” (off-line self-archiving), 3) batch import by depositing SIPs via FTP or SMB/CIFS; and 4) integration with third-party document management software via invocation of SOAP Services or client API.

== User Experiences ==


== Development Activity ==


Code is being actively developed at [https://github.com/keeps/roda RODA GitHub repository].
All development activity is visible on GitHub: http://github.com/keeps/roda/commits

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

The following new features were added in RODA version 1.2.0:
* Using Droid for file format identification
* Added support for presentations: Microsoft Powerpoint (ppt, pptx), OpenOffice Presentation / LibreOffice Impress (odp)
* Added support for spreadsheets: Microsoft Excel (xls, xlsx), OpenOffice Spreadsheet / LibreOffice Calc (ods)
* Added support for email (.eml) but conversion is not yet supported
* Added web service to download AIP
* Added web service to download DIP

For more information checkout the complete [https://github.com/keeps/roda/blob/master/CHANGELOG.txt change log].

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

{{Infobox_tool_details
|ohloh_id=Roda
}}

Rescarta

2020-07-02T17:11:37Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=The ResCarta Tools software empowers users to create non-proprietary digital objects with LOC standard METS, MODS, MIX and AudioMD metadata from existing TIFF, JPEG, PDF and WAV data through user-friendly interfaces. Digital collections can be created, indexed, displayed and validated using the software. Exports DC, OAI_DC formats for use in OAI/PMH servers.
|image=
|homepage=http://www.ResCarta.org
|license=Apache License v2.0
|platforms=Linux, Windows, and OSX operating systems
}}


[[Category:Preservation System]]
[[Category:Access]]
[[Category:Personal Archiving]]
[[Category:METS]]


[[Category:Audio]]
[[Category:Document]]
[[Category:Research Data]]

== Description ==

ResCarta Toolkit allows users to create digital archives from scans, digital photographs or recordings of analog objects. Metadata is added using simple forms and is written into each digital object to Library of Congress Standards of METS, MODS, MIX, and AudioMD. Audio files containing spoken words can be automatically transcribed. Textural content of documents and audio can be edited to create highly accurate transcriptions using graphical tools. Standard directory and file naming is produced during use. A complete Lucene tm index of metadata and textural content can be created for use in a fully functional web application for discovery and display of digital objects. A checksum validation tool is included to assure long term stability of the archive.

====Platform====
The ResCarta Toolkit runs on Windows, Mac and Linux operating systems in single user or coordinated multiuser mode.

== User Experiences ==

* https://sourceforge.net/projects/rescarta/reviews?source=navbar

== Development Activity ==

Years of archived releases can be found at...
http://sourceforge.net/projects/rescarta/files/ResCarta%20Tools/


{{Infobox_tool_details
|ohloh_id=rescarta
}}

OpenWMS (Workflow Management System for Digital Objects)

2020-07-02T17:05:44Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=The OpenWMS is a platform-independent, open source, web-accessible system that can be used as a standalone application or integrated with other repository architectures by a wide range of organizations.
|image=
|homepage=http://rucore.libraries.rutgers.edu/open/projects/openwms/
|license=
|platforms=
}}


[[Category:Metadata Processing]]
[[Category:Preservation System]]
[[Category:METS]]

= Description =
The OpenWMS is a platform-independent, open source, web-accessible system that can be used as a standalone application or integrated with other repository architectures by a wide range of organizations. It provides a complete metadata creation system for analog and digital materials, with services to ingest objects and metadata into a Fedora repository and to export these objects and metadata, individually and in bulk in METS/XML Wrapper.

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=OpenWMS: Workflow Management System for Digital Objects
}}

Libsafe

2020-07-02T17:02:13Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=libsafe allows the organizations to create a full OAIS compliant Archive, including active and passive digital preservation workflows and is particularly suited for master image files of digitizing processes.
|homepage=http://www.preservaciondigital.es
}}



[[Category:Preservation System]]
[[Category:Audio]]
[[Category:Document]]
[[Category:Image]]
[[Category:Video]]
[[Category:Web Archive]]
[[Category:METS]]

== Description ==

LIBSAFE Advanced allows the organizations to create a full OAIS aligned Archive, including active and passive digital preservation workflows and is particularly suited for master image files of digitizing processes. It's used by large institutions like the British Library, the National Library of Spain or the United States Holocaust Memorial Museum but also by smaller organizations like universities or hospitals.

It allows to manage high volume data archives with ease, having deployments of 6PB in size.

More information: https://www.libnova.com

Key features and benefits:
* Easy to use web interface
* Integrated catalog
* Full preservation lifecycle management
* Object versioning
* Powerful metadata engine (versioning of the metadata, unique metadata and mandatory metatadata) over any schema. Full METS and PREMIS aligment. Allows creating new schemas and migrating one to another. Allows sync to other tools. Fully configurable metadata schemas.
* REST API for ingestion, catalog search and object retrieve.
* Works with any SMB, NFS or Object based storage.
* Microservices: It's possible to expand various functions easily with plug-ins.
* Linear scalability: It is possible to scale the platform to achieve any needed performance.

=== Detailed description ===
The OAIS submission agreement concept maps over a "Preservation area" on libsafe, that defines all the preservation policy to apply:

* Sanitizing policy (deleting temp files, etc)
* Preprocessing: new formats generation for files (doc > pdf, ARC > WARC, etc) or metadata pre-processing.
* Checking: fixity checking (antivirus, files and folders names, jhove validation, file size, etc). Each check can be enabled, disabled or let the system choose using a regex expression.
* Exploring: How metadata should be extracted.
* Dissemination: how many copies and in wich "storage pools" should the information be stored. libsafe does not destroy the folder/file structure or filenames.
* Auditing policy: How often the object should be audited by the system in background.

The whole system is "job" based. Every process is a job (ingestion job, auditing job, migration job, etc).

It implements full OAIS framework including:

==== Ingestion ====
* DirectSIP - Create a SIP with the browser from a set of folders (one folder > one object) or ingest SIP.

* Preprocessing: launches selected plugings over the content. A preprocessor is a plugin (essentialy a .exe file) that makes any changes on a object. Most common preprocessors can be preloaded souch as ImageMagik, FFMPEG, GhostScript, inkscape and others, but it's easy to extend the functionality.

* Checking: A check verifies something about the object, it's files or it's metadata. A check is a plugin (essentialy a .exe file) that is launched against any elemment (object, any file, etc) if it matches a regex or extension (for ex: *.TIF) and verifies something about it, returning a "OK" or "ERROR". libsafe has about 40 checks (jhove validation, file size, file numbers, etc) bu adding more is very easy. If a check fails the ingestion job stops and the system returns the control to the user to correct the problems and re-launch the job.

* Exploring: Extracts (from XML, CSV, text file or quering other system) and generates metadata (using DROID for instance) and loads it to the catalog. libsafe can load METS files, but reading metadata from custom XML file is easy using XSLT file. It's possible to use conversion or generation plug-ins here also (for instance, quering a OAI-PMH server using the folder name of the object).

* Dissemination: Storage Groups contain Storage Volumnes (mountpoints). Based on the Preservation Area storage policy, libsafe selects the Storage Volumes to store the object. and starts coping them. libsafe stores the path and the hash to each file. In this part of the object, security XML files are also created, containing all the metadata, events, other locations of each file, etc.

* Auditing: Inmediatly after finishing the object copy, libsafe scans again all the object files hasing them again and comparing the hash between the database stored hash, the ingestion job temp files hash, security XML hash and the real files hash on every copy. If the audit job is finished with a OK result, all objects are considered preserved.

==== Data Management ====
* Bulk transforms: Allows massive metadata schema changes (DC > Marc21 for instance), but it's possible to evolve to any schema defining a crosswalk.

* API for metadata versionig: It's possible to edit the objects metadata using an API. Previous versions of the metadata sets are always preserved. It's not really editing, it's versioning.

==== Access ====
* Catalog: It's possible to search for any metadata of the object, locate it and visualize it's details, including:
** Object creation details (when, who, etc)
** Metadata details
** Object previuos versions
** Object files and folders hierarchy, being able to download the files or the full object in a AIP.
** Active preservation
*** Risks
*** File formats used and risks (using PRONOM among others)
*** Metadata formats
** Passive preservation
** Auditing results
** Storage details (where it's this object stored)
** Object events (creation, access, transformation, etc)

It's also posible to query the system using the API and to retrieve files or complete objects using a RESTful API call.

==== Administration ====
Reports: various reports including collection wide.
Users: create, set roles, etc.
Settings: Change system settings, submission agreements, etc.

==== Active preservation ====
Including options to evolve not only file formats but also metadata schemas.

== User Experiences ==

https://www.libnova.com

== Development Activity ==


https://www.libnova.com

KoLibRI (Kopal Library for Retrieval and Ingest)

2020-07-02T16:59:21Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=The kopal Library for Retrieval and Ingest (koLibRI) represents a library of Java tools that have been developed for the interaction with the DIAS system of IBM within the kopal project.
|image=
|homepage=http://kopal.langzeitarchivierung.de/index_koLibRI.php.en
|license=
|platforms=
}}


[[Category:Preservation System]]
[[Category:METS]]

= Description =
The kopal Library for Retrieval and Ingest (koLibRI) represents a library of Java tools that have been developed for the interaction with the DIAS system of IBM within the kopal project.

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=kopal Library for Retrieval and Ingest (koLibRI)
}}

Fedora Commons

2020-07-02T16:55:13Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=Fedora provides the back-end foundation for digital repository systems responsible for managing and preserving all types of digital content.
|image=
|homepage=http://fedora-commons.org/
|license=
|platforms=
}}


[[Category:Preservation System]]
[[Category:METS]]

= Description =
[http://fedora-commons.org/ Fedora] provides the back-end foundation for digital repository systems responsible for managing and preserving all types of digital content.
====Provider====
DuraSpace/Fedora Commons
====Licensing and cost====
[http://www.apache.org/licenses/LICENSE-2.0.html Apache 2.0] – free.
====Development Activity====
Version 3.6.2 was released 15 November 2012.
Development is ongoing. The [https://wiki.duraspace.org/display/FF/Fedora+Futures+Home Fedora Futures] initiative was created in December 2012 to take a long-term view of Fedora development. This initiative is developing Fedora 4.0, re-architecting the software to accommodate recent software and technology advances as appropriate.
====Platform and interoperability====
Fedora is written in Java, and was tested under Linux, Solaris, Windows, and Mac OS X.
====Functional Notes====
In the Fedora digital object model, an object consists of a persistent identifier, an XML document for object properties, and a number of datastreams each holding a content file or metadata record (the object can have more than one of each). Each object can assert relationships to any number of other objects using RDF. The XML object properties documents contain information such as an audit trail of actions that have affected the object and policies about the object; as long as these files, along with the content itself, are backed up properly, they can be used to reconstruct an entire running instance of the repository without relying on any external software.
While the Fedora Repository is capable of operating as a standalone content server, it is designed for use with other software to provide full system functionality. Such software might include authoring or ingest applications, search engines, workflow management, or security components such as user identity management.
====Documentation and user support====
The Fedora Commons community is extensive, with active [http://www.fedora-commons.org/community/userlist user] and [http://www.fedora-commons.org/community/developers/devlist developer] mailing lists; DuraSpace also hosts a Fedora [https://wiki.duraspace.org/display/FEDORA/Home wiki], which includes tutorials, user and installation guides, and other resources.
The Fedora site also links to a number of [http://www.fedora-commons.org/resources/serviceproviders registered service providers], which offer assistance with design, installation, and implementation.
====Usability====
Fedora provides a web-based Administrator GUI for low-level object editing; users, however, interact with the repository using APIs for management, access, search, and queries. Usability more broadly is dependent on the interfaces that the system administrator has chosen as front ends for the APIs: this model was chosen so that different interfaces can be designed to suit different needs. The Fedora wiki includes a registry of community-developed software that provides these kinds of interfaces; frameworks to facilitate such development include [http://projecthydra.org Hydra] and [http://islandora.ca Islandora].
====Expertise required====
Installation and configuration require detailed system administration knowledge, as well as expertise in XML and interface design. The Hydra and Islandora frameworks seek to alleviate this by 'hiding' Fedora behind simpler system environments based on Ruby on Rails and Drupal, respectively.
====Standards compliance====
Fedora supports OAI-PMH (and by extension, Dublin Core and other metadata standards), and also provides support for RDF.
====Influence and take-up====
The [https://wiki.duraspace.org/display/FCCommReg/Fedora+Commons+Registry Fedora Commons Registry] lists nearly 200 organisations with Fedora instances, from broadcast services such as WGBH, to government agencies such as the U.S. Centers for Disease Control and Prevention, to academic archives such as Oxford University.

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=Fedora Commons
}}

DSpace

2020-07-02T16:43:21Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=DSpace is an institutional repository system which enables easy deposit, preservation, and access for all types of digital content.
|image=
|homepage=http://www.dspace.org/
|license=BSD
|platforms=
}}


[[Category:Preservation System]]
[[Category:Access]]
[[Category:METS]]

= Description =
[http://www.dspace.org/ DSpace] is an institutional repository system which enables easy deposit, preservation, and access for all types of digital content. 
====Provider====
DuraSpace
====Licensing and cost====
[http://www.linfo.org/bsdlicense.html BSD Open Source License] - free
====Development Activity====
DSpace 1.8.1 was released in December 2011.
Development is ongoing. In late 2011 the DSpace Community Advisory Team decided to forgo releasing a version 2.0; instead, version 3.0 was released on November 30, 2012. DSpace 3.2 was officially released to the public on July 24, 2013.

====Platform and interoperability====
DSpace is written in Java, providing a web based interface that can be installed in Linux, Mac OSX or Windows environments. It requires either a PostgreSQL or Oracle database. The software comes with plugins for most university authentication methods, including: LDAP (and hierarchical LDAP), Shibboleth, X.509, and IP-based.
====Functional Notes====
The DSpace data model is intended to reflect the structure of the organization using the system. Each DSpace site is divided into communities, which can be further divided into sub-communities reflecting the typical university structure of college, department, research centre, or laboratory. Communities contain collections, which are groupings of related content. Each collection is composed of items, which are the basic archival elements of the archive. Items are further subdivided into named bundles of bitstreams.
Workflows are unidirectional – e.g. an item can’t move from Live to Pending.
DSpace administrators can create multiple user roles, which allows for extremely fine-tuned access rights.
====Documentation and user support====
DSpace offers a wealth of documentation and user support. The website includes an extensive [https://wiki.duraspace.org/display/DSDOC/All+Documentation Documentation Wiki], and supports a number of mailing lists. Users can report and track errors through a JIRA system. The site also links to tutorials, how-to’s, and other training materials.
As of 2011, there are seven registered service providers and 22 non-registered providers, offering presumably fee-based support . DSpace also has an Ambassador Program, which attempts to identify a DSpace user in every country or region who is willing to volunteer to be a point of contact for organizations just getting started.
====Usability====
DSpace does not include an installation and configuration tool, or ‘wizard,’ which makes these processes time consuming and challenging for users without system administration training.
A number of organisations using DSpace have performed usability analyses of their repositories. While the overall structure works well, many organisations found that naming conventions were sometimes confusing for users. In addition, many users expected that the search mechanism would automatically include a Boolean AND, which is not the case.
====Expertise required====
Installation and configuration greatly benefit from system administration knowledge, as well as a deep understanding of repository structures and workflows.
====Standards compliance====
DSpace supports OAI-PMH, OAI-ORE, SWORD, SWORD2, WebDAV, OpenSearch, OpenURL, RSS, and ATOM.
DSpace metadata uses the Dublin Core standard.
====Influence and take-up====
As of 2011, over 1100 organizations currently use the DSpace software in a production or project environment. A full list of known DSpace instances can be found at [http://www.dspace.org/whos-using-dspace http://www.dspace.org/whos-using-dspace].

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=DSpace
}}

Curator's Workbench

2020-07-02T16:37:00Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=Curator's Workbench is a tool that automates and streamlines the process of preparing collections of digital materials for submission to a repository
|image=
|homepage=https://github.com/UNC-Libraries/Curators-Workbench
|license=
|platforms=
}}


[[Category:Preservation System]]
[[Category:Metadata Processing]]
[[Category:METS]]

= Description =
The [https://blogs.lib.unc.edu/cdr/index.php/about/cdr-development-and-collab/curators-workbench/ Curator’s Workbench] is a tool that automates and streamlines the process of preparing collections of digital materials for submission to a repository. The Workbench will capture and stage files, generate manifests that include fixity information, arrange folders and objects, normalise metadata to custom requirements, and finally create a submission package for ingest into the archive.

====Provider====
Carolina Digital Repository, an initiative of the University Libraries of UNC Chapel Hill.

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

====Platform and interoperability====
Curator’s Workbench has been tested in Windows, Mac, and Linux environments. It is built upon the Eclipse Rich Client Platform, using Eclipse’s Modeling Framework and Graphical Modeling Framework. The software incorporates iRODS jargon client libraries, and is extensible by plug-in.

====Functional notes====
The Workbench’s crosswalk tool is able to map user-supplied metadata fields to MODS elements, allowing the user to define how each MODS record is created, which elements are used and where they come from in the source metadata. This can be done at the project level, allowing batch staging; the software is capable of migrating thousands of descriptive records at a time and linking them to data objects.
As materials are selected, arranged, and described, the software generates a METS file that documents these processes. In addition, it generates checksums and UUIDs for each object. When a project is ready for submission, an export function translates the internal METS into an XML-viewable submission package ready for ingest.
Curator’s Workbench was designed for use in the Carolina Digital Repository, which uses a web interface for ingest into a Fedora repository with iRODS storage. To address the unreliability of web ingest, the software can stage files in advance. In the CDR setup, individual users have accounts in a staging area within the iRODS grid; files placed there by the Workbench are readable by the Fedora instance at ingest time, at which point they are also copied into archival storage.

====Documentation and user support====
While CDR does not provide direct support, there are Google groups for developers and users. The Users group was active as of December 2011, but the Developers group was then not yet active. There is also an “Issues” page on the Github wiki, which was active as of February 2012.
The Workbench incorporates its User Manual into its help system but does not provide a PDF instance of the document. Some technical information is available on a GitHub [https://github.com/UNC-Libraries/Curators-Workbench/wiki wiki].

====Usability====
The Workbench GUI is extremely simple and easy to use, although solid familiarity with metadata standards is essential.

====Expertise required====
Installation and configuration require deep system administration knowledge.

====Standards compliance====
The Workbench uses METS XML for project definition files and submission files, and incorporates MODS XML for description.

====Influence and take-up====
Curator’s Workbench is used within the UNC library system.

= User Experiences =

= Development Activity =

Curator’s Workbench version 3.0 was released in October 2011 and the last version 5.x in September 2015.
The software was created for the Carolina Digital Repository, originally developed to support the workflow needs of UNC Libraries, however, it is no longer in use at UNC Libraries nor being further developed or supported by the repository team. The last “Version 4.1.5 - a stable Build” can be downloaded from [https://github.com/UNC-Libraries/Curators-Workbench/issues Github Issues page].

All development activity is visible on GitHub: http://github.com/UNC-Libraries/Curators-Workbench/commits

====Release Feed====
Below the last 3 release feeds:
<rss max=3>https://github.com/UNC-Libraries/Curators-Workbench/releases.atom</rss>

====Activity Feed====
Below the last 5 commits:
<rss max=5>https://github.com/UNC-Libraries/Curators-Workbench/commits/master.atom</rss>

{{Infobox_tool_details
|ohloh_id=Curator's Workbench
}}

Archivematica

2020-07-02T16:34:20Z

Jukervin: Added METS Category.

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

CONTENTdm

2020-07-02T16:23:54Z

Jukervin: Added METS Category.

{{Infobox_tool
|purpose=CONTENTdm is a digital collection management system
|image=
|homepage=http://www.contentdm.org/
|license=
|platforms=
}}


[[Category:Preservation System]]
[[Category:METS]]

= Description =
[http://www.contentdm.org/ CONTENTdm] is a software solution that handles the storage, management, and delivery of library digital collection to the web by providing access to web-based digital collection tool where data and digital items are prepared in large batches, a server where data and images are stored and can be edited, a Web-based discovery interface optimized for customization, self-service tool to upload the metadata of your digital content to WorldCat using the Digital Collection Gateway, and integration with OCLC products for building collections with cataloging workflows, as well as the option of harvesting from the Web sites and adding long-term preservation. Developed by OCLC. A hosted version is available.
====Provider====
OCLC
====Licensing and cost====
CONTENTdm uses fee-based licenses for both the software and the hosting service; a range of optional services and tools is available as well. Pricing is unclear on the OCLC website.  
====Development activity====
CONTENTdm version 6.9 was released in November 2014.
OCLC is a self-funded not-for-profit organisation; CONTENTdm is one of their core services, receiving ongoing development and support.

====Platform and interoperability====
CONTENTdm Server runs on IIS with Windows 2008 or Apache with Linux (requires PHP 5.3). The CONTENTdm website has similar requirements. The software was designed to integrate with other OCLC products, including Connexion and Web Harvester. The CONTENTdm Project Client requires the Microsoft .NET Framework 3.5 or higher running on Windows P SP2 or later.
CONTENTdm offers an API to allow users to customise their workflows and extend website functionality.
====Functional notes====
Some licenses include an OCR Extension to generate full-text transcripts, and an Image Rights tool to designate ownership of items in the collection. The customisable web access platform integrates with OCLC’s WorldCat to promote greater discoverability. Collections can be stored on distributed drives, enabling collaboration between organisations.
====Documentation and user support====
Email- and telephone-based user support is included in the licensing fee. Users are also granted access to a [http://www.oclc.org/contentdm/support/default.htm User Support Center] with installation guides, Help files, tutorials and a Support FAQ. The Center also supports forums and blogs for the CONTENTdm community.
====Usability====
CONTENTdm provides a web-based administration interface, and includes number of options for managing and adding content to collections. For its latest iteration, extensive usability testing was conducted as part of a user-centered design approach.
====Expertise required====
If an organisation wishes to host its own server, installation and configuration will require system administration knowledge.
====Standards compliance====
CONTENTdm heavily advertises its standards compliance in a number of arenas: supporting Unicode for character display; offering Dublin Core, VRA Core, and METS/ALTO for metadata assignment; serving as an OAI repository for those who wish to make their metadata available for harvesting; and supporting Z39.50 for search and retrieval.
====Influence and take-up====
The CONTENTdm website advertises use by over 2,000 organizations, including public libraries, academic libraries, historical societies, and museums.

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=CONTENTdm
}}