Content Management System (CMS)

Over the last decade, content management systems (CMSs) have made the creation of websites available to users who do not have much technical knowledge in the development of this type of products. In the field of information and documentation, there has been a convergence between the traditional desktop applications for the management of information unit funds and CMSs, which has led to the emergence of specific web applications integrating both the traditional features of document software and options for publishing these contents on the Web

ArchivesSpace

Website: http://archivesspace.org/

License: Educational Community License v2.

Developer: Andrew W. Mellon Foundation, New York University, University of Illinois Urbana-Champaign and University of California San Diego.

Operating system: Cross-platform.

Main features:

  • Web application written in Java. Lastest version requires 1.7 version or higher and Apache Tomcat server. It is recommended to use the MySQL database. It uses an engine Apache Solr to build a search index, to enrich document processing and the options for grouping search results (clustering). It is compatible with the standards EAD, MARCXML, MODS, Dublin Core and METS.
  • Supports the main administrative processes of an archive (import, description, classification, authorities, rights…)
  • 4 different interfaces for application management (public part, administration part, API and search engine Solr).
  • The template for the creation of archival descriptions follows the DACS North American standard.
  • Digital objects are not stored in the application but are managed by an external URI.  This provides greater flexibility when selecting the storage provider (Amazon, Dropbox, Google Drive, etc.), although it implies the need to update all the URIs in case of future changes.

 

AtoM

WebsIte: https://www.accesstomemory.org

License: GPL v3.

Developer: Artefactual Systems. The first versions of the application, launched under the name of ICA-AtoM were developed in colaboration with the ICA Program Commission (PCOM)

Operating system: Cross-platform.

Main features:

  • Web application written in PHP. The most recent versions of the application require PHP version 5.3.10 v or higher. Uses MySQL database for the storage of information and precise search server Elasticsearch to manage the search engine and filter system. The use of Nginx servers is recommended, although it is compatible with Apache or Microsoft Internet Information Services, among others.
  • Supports the EAD and Dublin Core metadata standards.
  • Oriented essentially to the creation of description tools for the archival sector, according to the international regulations such as ISAG(G), ISAAR-CPF, ISDF, etc.
  • Extendable and customizable through a system of plugins and templates (although there are on limited options).
  • Capacity to manage the main file formats of image, audio and video (mp3, mp4, avi, jpg, png, tif, among others).
  • Able to export metadata in EAD-XML, DC-XML and SKOS formats for controlled vocabularies.

 

CollectiveAccess

Website: http://www.collectiveaccess.org/

License: GPL v3.

Developer: Whirl-i-Gig, with the collaboration of different partner institutions such as the Institute of Museum and Library Services, the National Endowment for the Humanities, the New York State Council for the Arts or the Kulturstiftung des Bundes, among others.

Operating system: Cross-platform.

Main features:

  • Written in PHP programming language that requires PHP version 5.3.6 or higher through Apache servers (although it is compatible with others like Nginx, etc.). Uses a database management system (MySQL). Currently it is possible to implement the application with different metadata profiles such as Dublin Core, DarwinCore, PBCore, Spectrum, VRA Core, etc. but technically, using XML language, it is possible to incorporate any metadata scheme into the system.
  • Made up of two independent software components: Providence and Pawtucket, responsible for the system management module and the public user interface, respectively.
  • Highly configurable cataloging interface from different metadata profiles and customizable fields.
  • Allows for categorization, tagging and geolocation of digital objects.
  • Configurable search engine (MySQL or Solr).
  • Administrative tools aimed at managing the collection (acquisitions, loans, location, conservation status, etc.).
  • Interoperable and compatible with the OAI-PMH protocol.
  • Customizable controlled lists and vocabularies.

 

Omeka

Website: https://omeka.org/ | https://www.omeka.net/

License: GPL v3.

Developer: Roy Rosenzweig Center for History and New Media y George Mason University.

Operating system: Cross-platform.

Main features:

  • Web application written in PHP. The version 2.5 requires PHP version 5.3.2 or higher. Uses MySQL database for information storage and requires the ImageMagick software package to manage the images incorporated into the repository (preview, creation of derivatives, etc.). It is recommended to use Apache servers but it is compatible with Nginx or Microsoft Internet Information Services, among others. Supports Dublin Core (by default) metadata standard and qualified Dublin Core, VRA Core and PBCore (by plugins). Technically it is possible to incorporate any metadata scheme using custom plugins.
  • Low learning curve.
  • Extensible and customizable through a system of plugins and templates.
  • Interoperable and compatible with the OAI-PMH protocol.
  • Allows export of metadata in CSV, DC-RDF, DC-XML, JSON, PBCore XML, VRACore XML formats and proprietary XML and RDF formats
  • Ability to manage the main formats of image, audio and video files: aac, bmp, divx, gif, jp2, jpg, m4a, midi, mov, mp3, mp4, mpeg, ogg, png, tif, wma, among many others.
  • Allows for categorization, tagging and geolocation of digital objects.
  • Public API and free access.
  • Specific module to create virtual exhibitions.