nautilus/archive
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Page: archival_software
Pages
Home archival_metadata_standards archival_software other_archives preservation
2 archival_software
ibu edited this page 2024-08-11 08:34:11 +00:00
Table of Contents

Archival software

There are many options for choosing archival software. A link on that page contains a spreadsheet with a comparison of archival management software. Abbreviations: CMS=ContentManagmentSystem, DAMS=DigitalAssetManagementSystem

There is also a German list of archival software solutions.

Our requirements:

  • A hard requirement for the chosen solution is the possibility to export the data in a standardized encoding (EAD and either DACS or ISAD(G)).
  • The solution should also support OAI-PMH for publishing metadata feeds, so that our data can be hoste locally and shared vie federation. Cf. the list of open archives.

Relevant OSS (=OpenSourceSoftware) solutions with annotations:

  • ☉: Archivist's toolkit user manual
    • (too) old ("the first open source archival data management system to provide broad, integrated support for the management of archives")
    • written in java
  • ☉: collectiveaccess demo manual: data modelling
    • since 2003; developed by company Whirl-i-Gig (few employees), financed through product support it seems
    • requires PHP+MySQL, still php7; v2.0 in preparation
    • supports many standards (table), in particular DACS+EAD and ISAD(G)+EAD
    • highly configurable
    • cataloging app is separated from finding app
    • seems to not provides these functionalities we do not need: Appraisal; Accessioning; Custodial Management/Inventory Control; Preservation Administration
  • ☉: ArchivesSpace
    • seems to require membership (if not now, it may do so later) with membership fee costs
  • ☉: AtoM wikipedia demo docs
    • since 2007
    • requires PHP+MySQL, still php7 (PostgreSQL "potentially compatible"); roadmap; requires Elasticsearch as separate service
    • supports standards ISAD(G)+EAD, EAC-CPF and SKOS (and ISAD, ISAAR, ISDIAH, ISDF) and Dublin Core, MODS
  • ☉: Archivematica
    • supports publication metadata standards, but not archival metadata standards
    • useful for managing digital contents and its metadata
    • not exactly for archival descriptions, but can extend archival catalogs: integration with AtoM and ArchivesSpace
    • development seemingly financed by paid new features
  • ☉: arTUX
    • archium website is German only - seems to be a small company; risk of commercialization and relatively small user base
  • ☉: Omeka comes in 2 variants: Omeka S and Omeka Classic: "Omeka Classic is perfect for smaller projects. Omeka.net is the place to go if you don't want to host your own. And, Omeka S is all linked open data and made for larger ventures"
    • written in PHP
    • useful for online exibitions
    • supports LOD
    • originally launched at the Roy Rosenzweig Center for History and New Media with funding from multiple organizations, team size: 5 people
    • open issues (omega classic) don't look like it's a vera matue project

Conclusion: We should use collectiveaccess or AtoM; not sure yet which one, will have to try them out more.

See also