COPTR - User contributions [en-gb]

ADDML

2022-12-02T14:16:22Z

TerjePD:

{{Infobox format}} <b>NB! Under construction!</b>
ADDML (Archival Data Description Markup Language) is a format for describing technical structures in a dataset. The format was developed by the National Archives of Norway in the late 1990s. Today normally used versions are ADDML 8.2 or ADDML 8.3. The format are today in use in Norway and Sweden. It is open for everyone interested to take part in the further developement of the format and it is free of use.

[[File:Coptr ADDML Fig1.jpg|thumb]]

The format is describing datasets, hence the element "dataset" is the top level. It is open to describe many datasets within one description. Next level is consisting of three elements that forms a section each. The element "reference" is used to describe metadata about the dataset and the original system from where it is generated, both contextual and content types of metadata. The element "flatFiles" is used to describe in derail a flat file structure of the form - File / Record / Field. The element "dataObjects" is used to describe other structures. This element is not described in detail, but has a structure that is generic and gives the user the possibility to design a structure of need. The top structure would be as shown in figure 1.

Under the element "reference" there is two defined elements - the element "context" and the element "content". The element context is referring to the original system and metadata about this system. The element content is referring to the dataset and metadata about the dataset itself. Under both of them there is defined the element "additionalElements", with the element "additionalElement" as sublevel. There can be many additionalElement under additionalElements, and it is possible to define an additionalElements under additionalElement. This way it is possible to create a hierarchical structure for each ones need. The standard itself do not define any metadata elements. But using the generic posibillities with additionalElements and additionalElement, each user can define what kind of metadata elements they want.

[[File:Coptr ADDML Fig2.jpg|thumb]]

Under the element "flatFiles" there is a structure shown in figure 2 where it is possible to describe files, records and fields in detail. It is possible to define types of files, records and fields and connect a definition to a type at the same level. In this structure there is many elements defined on each level for the descriptive use.

Under the element "dataObjects" it is possible to describe structures which are not flat files. This is again based on a generic structure where the user have to define himself the actual structure.

In addition it is possible on spesific elements to specify a process. This will not actually be a process, but a flag indicating to an application that a certain process should be performed while reading the datafiles.

ADDML

2022-12-02T12:33:20Z

TerjePD:

File:Coptr ADDML Fig2.jpg

2022-12-02T12:28:34Z

TerjePD:

ADDML

2022-12-02T12:27:16Z

TerjePD:

{{Infobox format}} <b>NB! Under construction!</b>
ADDML (Archival Data Description Markup Language) is a format for describing technical structures in a dataset. The format was developed by the National Archives of Norway in the late 1990s. Today normally used versions are ADDML 8.2 or ADDML 8.3. The format are today in use in Norway and Sweden. It is open for everyone interested to take part in the further developement of the format and it is free of use.

[[File:Coptr ADDML Fig1.jpg|thumb]]

The format is describing datasets, hence the element "dataset" is the top level. It is open to describe many datasets within one description. Next level is consisting of three elements that forms a section each. The element "reference" is used to describe metadata about the dataset and the original system from where it is generated, both contextual and content types of metadata. The element "flatFiles" is used to describe in derail a flat file structure of the form - File / Record / Field. The element "dataObjects" is used to describe other structures. This element is not described in detail, but has a structure that is generic and gives the user the possibility to design a structure of need. The top structure would be as shown in figure 1.

Under the element "reference" there is two defined elements - the element "context" and the element "content". The element context is referring to the original system and metadata about this system. Rhe element content is referring to the dataset and metadata about the dataset itself. Under both of them there is defined the element "additionalElements", with the element "additionalElement" as sublevel. There can be many additionalElement under additionalElements, and it is possible to define an additionalElements under additionalElement. This way it is possible to create a hierarchical structure for each ones need. The standard itself do not define any metadata elements. But using the generic posibillities with additionalElements and additionalElement, each user can define what kind of metadata elements they want.

Under the element "flatFiles" there is a structure shown in figure 2 wehere it is possible to describe files, records and fields in detail. It is possible to define types of files, records and fields and connect a definition to a type at the same level.

ADDML

2022-06-08T11:57:37Z

TerjePD:

ADDML

2022-06-08T11:56:07Z

TerjePD:

File:Coptr ADDML Fig1.jpg

2022-06-08T11:46:33Z

TerjePD:

ADDML Top Level

ADDML

2022-06-08T08:47:41Z

TerjePD: Created page with "{{Infobox format}} ADDML (Archival Data Description Markup Language) is a format for describing technical structures in a dataset. The format was developed by the National Arc..."

{{Infobox format}}
ADDML (Archival Data Description Markup Language) is a format for describing technical structures in a dataset. The format was developed by the National Archives of Norway in the late 1990s. Todays normally used versions are ADDML 8.2 or ADDML 8.3. The format are today in use in Norway and Sweden. It is open for everyone interested to take part in the further developement of the format and it is free of use.

The format is describing datasets, hence the element "dataset" is the top level. It is open to describe many datasets within one description. Next level is consisting of three elements that forms a section each. The element "references" is used to describe metadata about the dataset, both contextual and content types of metadata. The element "flatFiles" is used to describe a flat file structure of the form - File / Record / Field. The element "dataObjects" is used to describe other structures. This element is not described, but has a structure that is generic and gives the user the possibility to design a structure of need.

Fedora Commons

2021-08-18T08:58:11Z

TerjePD:

{{Infobox tool
|purpose=Fedora provides the back-end foundation for digital repository systems responsible for managing and preserving all types of digital content.
|homepage=http://fedora-commons.org/
|formats_in=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|function=Preservation System
}}
{{Infobox tool details
|ohloh_id=Fedora Commons
}}
= 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 =

EssArch

2021-08-18T08:39:54Z

TerjePD:

{{Infobox tool
|purpose=An OAIS-based digital archive system to include both PreIngest and PreAccess functions
|homepage=https://www.essolutions.se/essarch/
|platforms=Linux, Windows
|formats_in=PREMIS (Preservation Metadata Implementation Strategies), METS (Metadata Encoding and Transmission Standard)
|formats_out=PREMIS (Preservation Metadata Implementation Strategies), METS (Metadata Encoding and Transmission Standard)
|function=Preservation System
}}
{{Infobox tool details}}




== Description ==
EssArch supports large portions of the archival process according to OAIS. It has modules for ingest, access, and format conversion. It also supports appraisal actions inside the repository.

== User Experiences ==


== Development Activity ==

EPrints

2021-08-17T14:21:28Z

TerjePD:

{{Infobox tool
|purpose=EPrints is an open access digital repository software, which is intended to create a highly configurable web-based repository.
|homepage=http://www.eprints.org/
|license=GPLv3 and LGPLv3
|formats_in=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|function=Access, Preservation System
}}
{{Infobox tool details
|ohloh_id=EPrints
}}
= Description =
[http://www.eprints.org/ EPrints] is an open access digital repository software, which is intended to create a highly configurable web-based repository.
The EPrints organisation also provides a number of services, including hosting, customization, importing legacy data, providing training and support, advising on policy development, assisting with advocacy and promotion, and providing project management.
====Provider====
University of Southampton
====Licensing and cost====
[http://www.gnu.org/licenses/gpl.html Gnu Public License (GPL)] - free
====Development Activity====
EPrints 3.3.7 was released in December 2011.
Development is ongoing as of writing. 
====Platform and interoperability====
EPrints is written in Perl.  It was developed on Redhat Linux, but it can be used on UNIX-like systems including OS-X. It also runs on Windows Vista and XP.
EPrints is able to export data into BibTeX, refer, EndNote & other bibliography managers, as well as Google Earth, Similie TimeLine or other Web Services.
====Functional Notes====
The EPrints data model consists of three core objects: the EPrint, the Document, and the User.  Users have stated that this allows the creation of more complex hierarchies than with other repository software.
EPrints does not automatically support Handle.
====Documentation and user support====
EPrints Services offers fee-based support for repositories. The EP-Tech mailing list offers free support and discussion about EPrints; however, it is unclear how active this mailing list is. The site also links to a bug-tracker.
The EPrints website offers extensive documentation via a [http://wiki.eprints.org/w/Main_Page wiki], including an installation manual, user guide, and training materials. While much of the information is up-to-date and clearly organised, a recent migration (as of November 2011) has left a number of the pages with error messages, or notices that the material “needs sorting out”.
====Usability====
An installation script automates most of the installation processes.
Development for version 3 included an extensive usability analysis, which resulted in substantial redesign of the metadata entry process. A key component is the new auto-complete function.
====Expertise required====
Installation and configuration greatly benefit from system administration knowledge, as well as a deep understanding of repository structures and workflows.
====Standards compliance====
EPrints is OAI compliant. It provides support for METS, Dublin Core and other DL interoperability formats.
====Influence and take-up====
EPrints is widely used in European archives and repositories. Organisations using EPrints include University College London Research, the Glasgow Theses Services, and the Queensland Department of Employment, Economic Development and Innovation.

= User Experiences =

= Development Activity =

Docuteam packer

2021-08-17T14:18:51Z

TerjePD:

{{Infobox tool
|purpose=Creates and edits SIPs
|homepage=https://docs.docuteam.ch/packer
|license=GPLv3
|platforms=Windows, Mac, Linux
|formats_in=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|function=Metadata Processing
|content=Metadata
}}
{{Infobox tool details}}
== Description ==
With docuteam packer, you can create and edit information packages (SIPs/DIPs) that are conforming to the Matterhorn METS profile. Content can be added from your file system. For certain file types, a preview is available. Technical/administratie metadata is automatically collected and stored in PREMIS. Descriptive metadata is stored in EAD, the display in the GUI is configurable.

== User Experiences ==
* SIPs created by docuteam packer can be processed by docuteam feeder which does the proper ingest process
* The distribution can be bundled with the required JRE

== Development Activity ==

DSpace

2021-08-17T14:17:30Z

TerjePD:

{{Infobox tool
|purpose=DSpace is an institutional repository system which enables easy deposit, preservation, and access for all types of digital content.
|homepage=http://www.dspace.org/
|license=BSD
|formats_in=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|function=Access, Preservation System
}}
{{Infobox tool details
|ohloh_id=DSpace
}}
= 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 =

Rosetta

2021-08-17T14:14:25Z

TerjePD:

{{Infobox tool
|purpose=Ex Libris Rosetta enables institutions to preserve and provide access to the collections in their care.
|homepage=http://www.exlibrisgroup.com/category/RosettaOverview
|license=Commercially licensed product.
|formats_in=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|function=Access, File Format Migration, Metadata Processing, Preservation System
}}
{{Infobox tool details}}
== 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 ==

Roda

2021-08-17T14:13:55Z

TerjePD:

{{Infobox tool
|image=RODA-logo-basic.png
|purpose=RODA - Repository of Authentic Digital Objects
|homepage=http://www.roda-community.org
|license=LGPL v3
|platforms=Server runs on Linux. Client runs on any web browser.
|formats_in=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|function=Preservation System
}}
{{Infobox tool details
|ohloh_id=Roda
}}
== 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>

PiM (PREMIS in METS) Toolbox

2021-08-17T14:12:46Z

TerjePD:

{{Infobox tool
|purpose=PREMIS in METS Toolbox was developed to support the implementation of PREMIS in the METS container format.
|homepage=http://sourceforge.net/projects/pimtoolbox/
|license=Public domain
|formats_in=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|function=File Format Migration, Metadata Processing, Validation
|content=Metadata
}}
{{Infobox tool details
|ohloh_id=PREMIS in METS (PiM) Toolbox
}}
= Description =
The [http://pim.fcla.edu/ PREMIS in METS Toolbox] was developed to support the implementation of PREMIS in the METS container format.  It consists of three web-based tools: a validator, which will check a PREMIS or PREMIS in METS document for standard conformance; a converter, which given a PREMIS document will generate a METS document containing the PREMIS elements, and vice-versa; and a describer, which will generate a description of an input file using PREMIS elements.
====Provider====
The Florida Center for Library Automation, sponsored by the Library of Congress
====Licensing and cost====
The Toolbox is free and open source.  No specific license information is available.
====Development activity====
The toolbox was created in 2009, and as of January 2012 is at Version 1.0.1.
No information is available about future development.
====Platform and interoperability====
The Toolbox uses a web interface, and is therefore platform agnostic.  
The Validation tool is based on [http://www.dcc.ac.uk/resources/external/jhove JHOVE] and [http://www.dcc.ac.uk/resource/external/droid DROID]; the Conversion tool is implemented in XSLT; and the DAITSS description service is the underlying system behind the describing function.
====Functional notes====
All three tools support various modes of input: a source document or file can be addressed by URL or uploaded. PREMIS and METS documents can also be typed or copied directly into Validate and Convert.
The interface does not support batch processing; however, the site advertises that the tools output is clean enough to make a PERL implementation possible.
There is anecdotal evidence that the site experiences somewhat frequent outages.  The tools do not appear to be able to recover from inappropriate inputs.
====Documentation and user support====
The PREMIS-in-METS Toolbox website does not provide formal documentation, although there are brief explanations of the tools’ functions.  Contact information is listed for the developer.
====Usability====
The tools themselves are extremely straightforward.
====Expertise required====
Familiarity with preservation metadata standards is essential.
====Standards compliance====
The Toolbox’s sole purpose is to aid curators in working with the PREMIS and METS preservation metadata standards.
====Influence and take-up====
No information available.

= User Experiences =

= Development Activity =

Preservica

2021-08-17T14:11:42Z

TerjePD:

{{Infobox tool
|image=Preservica-top-logo.png
|purpose=Preservica is a complete OAIS Digital Preservation system available on the cloud (hosted in US, EU, CA or AUS) and on premise (Standard and Enterprise versions). It is trusted by over 50 organisations across 4 continents to preserve collections both large (>6Pb) and small (few 100kb)
|homepage=http://www.preservica.com
|formats_in=PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=PREMIS (Preservation Metadata Implementation Strategies)
|function=Preservation System, Service
}}
{{Infobox tool details
|ohloh_id=Preservica(Tessella)
}}
= Description =
Key features include:
* '''Ingest:''' local tool to create SIPs and attach metadata and transfer to server; range of workflows to upload container files : ZIP files, DSpace, ContentDM or SharePoint exports, Outlook or Lotus Notes email files, or by taking a copy of a website; full QA of content plus running DROID and property extraction
* '''Data Management:''' Edit metadata using whatever descriptive schema you want e.g. Dublin Core, METS, EAD, etc; sync with catalogs e.g. CALM or via OAI-PMH; delete content using approval workflow.
* '''Administration:''' Create users, set roles, set access rules to content at fine grain; maintain transfer agreements; produce reports; sync with ActiveDirectory (on premise only)
* '''Access:''' Browse, search and download files and records using powerful interface. Separate public access interface for content with appropriate permissions.
* '''Storage:''' Large range of storage adapters including NAS / File Server, HSM, Centera, Atmos, S3, Glacier, SFTP; will manage multiple storage locations and copy to remote locations asynchronously; maintains metadata and index information; can set interval to check fixity
* '''Active Preservation:''' over 600 migration pathways installed; performs bulk migrations using background workflows then verifies using comparison of properties.
* '''API Access:''' All versions have an OAI-PMH data provider API and API for accessing metadata and content. Enterprise versions have a read/write REST API and a process control API.

===Versions===
* Cloud versions available hosted in EC, US, Canada and Australia
* Enterprise Private Cloud versions for running on a Preservica hosted and supported private cloud
* Enterprise versions for install in your own data centre
* Enterprise version allows development of complete solutions including your own workflows for all functions and a vast range of hosting options

= User Experiences =
* Case studies can be found here http://preservica.com/resources/case-studies/

= Development Activity =

Main release annually, around 4 minor releases per year

Latest 5.10 release information : https://preservica.com/resources/press-releases/latest-version-of-preservica-simplifies-digital-preservation-and-delivers-enhanced-api-capabilities-1

JHOVE (Harvard Object Validation Environment)

2021-08-17T14:10:32Z

TerjePD:

{{Infobox tool
|image=JHOVE.gif
|purpose=JHOVE provides functions to perform format-specific identification, validation, and characterization of digital objects.
|homepage=http://jhove.openpreservation.org/
|license=GNU Lesser General Public License (LGPL)
|platforms=JHOVE should be usable on any UNIX, Windows, or OS X platform with an appropriate J2SE installation. It should run on any operating system that supports Java 1.5 and has a directory-based file system.
|formats_in=PREMIS (Preservation Metadata Implementation Strategies)
|function=Encryption Detection, File Format Identification, Metadata Extraction, Validation
}}
{{Infobox tool details
|ohloh_id=JHOVE
}}
== Description ==
[http://jhove.openpreservation.org/ JHOVE] allows data curators to verify the file formats of the digital objects in their repositories. The analysis consists of three functions: identification, which determines the object’s format; validation, which checks whether the object conforms to its format’s technical norms; and characterization, which gives a report of the object’s salient properties.
Detailed information can be found in the DCC [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study].

==== Provider ====
[http://openpreservation.org/ Open Preservation Foundation]

==== Licensing and cost ====
[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free.

==== Platform and interoperability ====
JHOVE is implemented using Java 2 Standard Edition 5.0 (JDK 1.5). It was designed incorporating an API, which can be used on its own to create compatible tools and applications. Developers wishing to recompile the JHOVE source code will require Apache Ant.

==== Functional notes ====
JHOVE includes modules for the following 12 format types: AIFF; ASCII encoded text; GIF; HTML; JPEG; JPEG2000; PDF; TIFF; UTF-8 encoded text; WAVE; XML; and arbitrary bytestreams. Three of these formats (AIFF, GIF and JPEG) will not be supported by JHOVE2, while a further two (JPEG2000 and PDF) are not currently supported by JHOVE2 but may be in future. HTML is not directly supported by JHOVE2 but can be processed either as SGML or XML.
A number of limitations have come to light since JHOVE was first released, many of which are addressed with the JHOVE2 project. Currently, identification and validation are linked, with successful identification dependent on the validation process.  This means that any trivial error in the validation process can result in an object failing to be identified. In addition, JHOVE cannot analyze objects that are comprised of multiple file formats.
Developers have also remarked that working with the API is difficult.

==== Documentation and user support ====
The JHOVE website includes an excellent introduction and [http://hul.harvard.edu/jhove/using.html tutorial]. It also provides detailed specifications for its modules.
The [http://sourceforge.net/projects/jhove/ SourceForge] code repository includes a forum, which seems to be used only sporadically. It also hosts a mailing list and the usual facilities for filing bug reports, feature requests and support requests.

==== Usability ====
While installation and configuration can be complex, the Swing-based GUI allows for relatively easy use. JHOVE can also be invoked with a command-line interface.

==== Expertise required ====
Installation requires solid knowledge of command line interfaces and experience with manually editing configuration files. Familiarity with metadata outputs is also essential.

==== Standards compliance ====
JHOVE was designed to integrate into the Ingest function of an OAIS. The validation process compares objects’ formats against ISO standards.

==== Influence and take-up ====
The SourceForge website reports approximately 11,400 downloads from the release of JHOVE 1.1 from 2008 to July 2013. Use of JHOVE is widespread in the digital preservation community.
JHOVE is integrated within the Planets Testbed and Plato.

== User Experiences ==

* '''Jisc:''' http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf
* '''Gary McGath:''' https://fileformats.wordpress.com/tag/jhove/
* '''KOST-CECO:''' Used in [[KOST-Val]] as a validation module for TIFF files.
* '''FITS (File Information Tool Set):''' Used in [[FITS (File Information Tool Set)|FITS]]
* '''PDF Association:''' http://www.pdfa.org/2014/12/ensuring-long-term-access-pdf-validation-with-jhove/
* '''Open Preservation Foundation: JHOVE issues and error messages:''' http://wiki.opf-labs.org/display/Documents/JHOVE+issues+and+error+messages/

== Development Activity ==

While much of its development effort has been diverted to [[JHOVE2]], JHOVE is still actively maintained and developed by the OPF [http://jhove.openpreservation.org/] as it supports some common formats that JHOVE2 does not.

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

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

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

=== About Formats ===
JHOVE do only read the format itself, not the spesification as such

JHOVE2

2021-08-17T14:10:03Z

TerjePD:

{{Infobox tool
|purpose=JHOVE2 allows data curators to characterise the digital objects in their repositories.
|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.
|formats_in=PREMIS (Preservation Metadata Implementation Strategies)
|function=Encryption Detection, File Format Identification, Metadata Extraction, Validation
}}
{{Infobox tool details
|ohloh_id=JHOVE2
}}
= 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>

=== About Formats ===
JHOVE2 do only read the format itself, not the spesification as such

JHOVE2

2021-08-17T14:09:31Z

TerjePD:

{{Infobox tool
|purpose=JHOVE2 allows data curators to characterise the digital objects in their repositories.
|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.
|formats_in=PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=PREMIS (Preservation Metadata Implementation Strategies)
|function=Encryption Detection, File Format Identification, Metadata Extraction, Validation
}}
{{Infobox tool details
|ohloh_id=JHOVE2
}}
= 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>

=== About Formats ===
JHOVE2 do only read the format itself, not the spesification as such

JHOVE (Harvard Object Validation Environment)

2021-08-17T14:08:34Z

TerjePD:

{{Infobox tool
|image=JHOVE.gif
|purpose=JHOVE provides functions to perform format-specific identification, validation, and characterization of digital objects.
|homepage=http://jhove.openpreservation.org/
|license=GNU Lesser General Public License (LGPL)
|platforms=JHOVE should be usable on any UNIX, Windows, or OS X platform with an appropriate J2SE installation. It should run on any operating system that supports Java 1.5 and has a directory-based file system.
|formats_in=PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=PREMIS (Preservation Metadata Implementation Strategies)
|function=Encryption Detection, File Format Identification, Metadata Extraction, Validation
}}
{{Infobox tool details
|ohloh_id=JHOVE
}}
== Description ==
[http://jhove.openpreservation.org/ JHOVE] allows data curators to verify the file formats of the digital objects in their repositories. The analysis consists of three functions: identification, which determines the object’s format; validation, which checks whether the object conforms to its format’s technical norms; and characterization, which gives a report of the object’s salient properties.
Detailed information can be found in the DCC [http://www.dcc.ac.uk/webfm_send/109 JHOVE Case Study].

==== Provider ====
[http://openpreservation.org/ Open Preservation Foundation]

==== Licensing and cost ====
[http://www.gnu.org/licenses/lgpl.html GNU Lesser General Public License] – free.

==== Platform and interoperability ====
JHOVE is implemented using Java 2 Standard Edition 5.0 (JDK 1.5). It was designed incorporating an API, which can be used on its own to create compatible tools and applications. Developers wishing to recompile the JHOVE source code will require Apache Ant.

==== Functional notes ====
JHOVE includes modules for the following 12 format types: AIFF; ASCII encoded text; GIF; HTML; JPEG; JPEG2000; PDF; TIFF; UTF-8 encoded text; WAVE; XML; and arbitrary bytestreams. Three of these formats (AIFF, GIF and JPEG) will not be supported by JHOVE2, while a further two (JPEG2000 and PDF) are not currently supported by JHOVE2 but may be in future. HTML is not directly supported by JHOVE2 but can be processed either as SGML or XML.
A number of limitations have come to light since JHOVE was first released, many of which are addressed with the JHOVE2 project. Currently, identification and validation are linked, with successful identification dependent on the validation process.  This means that any trivial error in the validation process can result in an object failing to be identified. In addition, JHOVE cannot analyze objects that are comprised of multiple file formats.
Developers have also remarked that working with the API is difficult.

==== Documentation and user support ====
The JHOVE website includes an excellent introduction and [http://hul.harvard.edu/jhove/using.html tutorial]. It also provides detailed specifications for its modules.
The [http://sourceforge.net/projects/jhove/ SourceForge] code repository includes a forum, which seems to be used only sporadically. It also hosts a mailing list and the usual facilities for filing bug reports, feature requests and support requests.

==== Usability ====
While installation and configuration can be complex, the Swing-based GUI allows for relatively easy use. JHOVE can also be invoked with a command-line interface.

==== Expertise required ====
Installation requires solid knowledge of command line interfaces and experience with manually editing configuration files. Familiarity with metadata outputs is also essential.

==== Standards compliance ====
JHOVE was designed to integrate into the Ingest function of an OAIS. The validation process compares objects’ formats against ISO standards.

==== Influence and take-up ====
The SourceForge website reports approximately 11,400 downloads from the release of JHOVE 1.1 from 2008 to July 2013. Use of JHOVE is widespread in the digital preservation community.
JHOVE is integrated within the Planets Testbed and Plato.

== User Experiences ==

* '''Jisc:''' http://www.jisc.ac.uk/media/documents/programmes/preservation/daat_file_format_tools_report.pdf
* '''Gary McGath:''' https://fileformats.wordpress.com/tag/jhove/
* '''KOST-CECO:''' Used in [[KOST-Val]] as a validation module for TIFF files.
* '''FITS (File Information Tool Set):''' Used in [[FITS (File Information Tool Set)|FITS]]
* '''PDF Association:''' http://www.pdfa.org/2014/12/ensuring-long-term-access-pdf-validation-with-jhove/
* '''Open Preservation Foundation: JHOVE issues and error messages:''' http://wiki.opf-labs.org/display/Documents/JHOVE+issues+and+error+messages/

== Development Activity ==

While much of its development effort has been diverted to [[JHOVE2]], JHOVE is still actively maintained and developed by the OPF [http://jhove.openpreservation.org/] as it supports some common formats that JHOVE2 does not.

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

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

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

=== About Formats ===
JHOVE do only read the format itself, not the spesification as such

DIMAG IngestList

2021-08-17T14:07:06Z

TerjePD:

{{Infobox tool
|purpose=Accompanies ingest process from donor to archive, logs process steps.
|homepage=http://ingestlist.sf.net/
|license=Open Source
|platforms=Linux, MacOS, Windows
|formats_in=PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=PREMIS (Preservation Metadata Implementation Strategies)
|function=Metadata Extraction, Transfer
}}
{{Infobox tool details}}
== Description ==
Manages the transfer process from the source system to the archive, captures files and database extracts from database systems, identifies formats, determines significant properties and delivers files with metadata and logs to the archive system DIMAG.

== User Experiences ==


== Development Activity ==

EchoDep Hub and Spoke Framework Tool Suite

2021-08-17T14:05:59Z

TerjePD:

{{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
|formats_in=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=METS (Metadata Encoding and Transmission Standard), PREMIS (Preservation Metadata Implementation Strategies)
|function=Metadata Processing
|content=Metadata
}}
{{Infobox tool details}}




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

DROID (Digital Record Object Identification)

2021-08-17T14:04:31Z

TerjePD:

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

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

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

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

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

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

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

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

http://apps.nationalarchives.gov.uk/pronom/fmt/579

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

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

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

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

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

=== About Formats ===
DROID do only read the format itself, not the spesification as such

Archivematica

2021-08-17T14:00:48Z

TerjePD:

{{Infobox tool
|purpose=Archivematica is a digital preservation system that automates the process of preparing digital objects for ingest into a repository and an access system
|homepage=https://www.archivematica.org
|license=[http://www.gnu.org/licenses/agpl.html AGPL version 3]
|formats_in=PREMIS (Preservation Metadata Implementation Strategies)
|formats_out=PREMIS (Preservation Metadata Implementation Strategies)
|function=File Format Migration, Preservation System
}}
{{Infobox tool details}}
= 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

PREMIS (Preservation Metadata Implementation Strategies)

2021-07-21T11:20:21Z

TerjePD:

The PREMIS Data Dictionary for Preservation Metadata is the international standard for metadata to support the preservation of digital objects and ensure their long-term usability. The Data Dictionary defines preservation metadata that:
*Supports the viability, renderability, understandability, authenticity, and identity of digital objects in a preservation context
*Represents the information most preservation repositories need to know to preserve digital materials over the long term
*Emphasizes “implementable metadata”: rigorously defined, supported by guidelines for creation, management, and use, and oriented toward automated workflows
*Embodies technical neutrality: no assumptions made about preservation technologies, strategies, metadata storage and management, etc
[https://www.loc.gov/standards/premis/ Documentation and information about the PREMIS editorial committee].
{{Infobox format
|Wikidata ID=Q2108820
}}