Update archival_software
parent
ad39ca2549
commit
afa3d087d1
1 changed files with 49 additions and 52 deletions
|
|
@ -1,52 +1,49 @@
|
|||
# Archival software
|
||||
|
||||
There are many options for choosing archival software.
|
||||
A link on [that page](https://www.nationalarchives.gov.uk/archives-sector/advice-and-guidance/managing-your-collection/cataloguing/cataloguing-and-archives-networks/) contains **[a spreadsheet with a comparison of archival management software](https://www.nationalarchives.gov.uk/documents/archives/cms-dams-options-for-archives.xls)**. Abbreviations: CMS=ContentManagmentSystem, DAMS=DigitalAssetManagementSystem
|
||||
|
||||
There is also a [German list of archival software solutions](https://de.wikipedia.org/wiki/Archivsoftware).
|
||||
|
||||
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](https://en.wikipedia.org/wiki/Open_Archives_Initiative_Protocol_for_Metadata_Harvesting) for publishing metadata feeds, so that our data can be hoste locally and shared vie federation. Cf. the [list of open archives](https://www.openarchives.org/Register/BrowseSites).
|
||||
|
||||
Relevant OSS (=OpenSourceSoftware) solutions with annotations:
|
||||
|
||||
* ☉: [Archivist's toolkit](http://archiviststoolkit.org/) [user manual](https://www2.archivists.org/sites/all/files/BHS%20Archivists'%20Toolkit%20Manual_2015%20revisions.pdf)
|
||||
* (too) old ("the first open source archival data management system to provide broad, integrated support for the management of archives")
|
||||
* written in java
|
||||
* ☉: [collectiveaccess](https://collectiveaccess.org/) [demo](https://demo.collectiveaccess.org) [manual: data modelling](https://manual.collectiveaccess.org/providence/user/dataModelling/index.html)
|
||||
* since 2003; developed by company [Whirl-i-Gig](https://www.linkedin.com/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](https://manual.collectiveaccess.org/providence/user/dataModelling/profiles/MetadataStandards.html)), 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](https://archivesspace.org/features)
|
||||
* seems to require membership (if not now, it may do so later) with membership fee costs
|
||||
* ☉: [AtoM](https://www.accesstomemory.org/de/) [wikipedia](https://en.wikipedia.org/wiki/AtoM_(archival_software)) [demo](https://demo.accesstomemory.org/) [docs](https://www.accesstomemory.org/en/docs/)
|
||||
* since 2007
|
||||
* requires PHP+MySQL, still php7 (PostgreSQL ["potentially compatible"](https://www.accesstomemory.org/en/docs/2.8/user-manual/overview/intro/)); [roadmap](https://projects.artefactual.com/projects/atom/roadmap); requires Elasticsearch as separate service
|
||||
* supports [standards](https://www.accesstomemory.org/en/docs/2.8/user-manual/overview/descriptive-standards/) ISAD(G)+EAD, EAC-CPF and SKOS (and ISAD, ISAAR, ISDIAH, ISDF) and Dublin Core, MODS
|
||||
* ☉: [Archivematica](https://www.archivematica.org/en/)
|
||||
* 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](https://archium.org/Archivdatenbank.html)
|
||||
* archium website is German only - seems to be a small company; risk of commercialization and relatively small user base
|
||||
* ☉: [Omeka](https://omeka.org/) 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](https://en.wikipedia.org/wiki/Linked_data)
|
||||
* 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
|
||||
|
||||
* [General resources and toolkits](https://www2.archivists.org/advocacy/publicawareness/resourcesandtoolkits)
|
||||
* Other archives
|
||||
* [list of open archives](https://www.openarchives.org/Register/BrowseSites)
|
||||
* https://de.wikipedia.org/wiki/Liste_von_Archiven
|
||||
# Archival software
|
||||
|
||||
There are many options for choosing archival software.
|
||||
A link on [that page](https://www.nationalarchives.gov.uk/archives-sector/advice-and-guidance/managing-your-collection/cataloguing/cataloguing-and-archives-networks/) contains **[a spreadsheet with a comparison of archival management software](https://www.nationalarchives.gov.uk/documents/archives/cms-dams-options-for-archives.xls)**. Abbreviations: CMS=ContentManagmentSystem, DAMS=DigitalAssetManagementSystem
|
||||
|
||||
There is also a [German list of archival software solutions](https://de.wikipedia.org/wiki/Archivsoftware).
|
||||
|
||||
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](https://en.wikipedia.org/wiki/Open_Archives_Initiative_Protocol_for_Metadata_Harvesting) for publishing metadata feeds, so that our data can be hoste locally and shared vie federation. Cf. the [list of open archives](https://www.openarchives.org/Register/BrowseSites).
|
||||
|
||||
Relevant OSS (=OpenSourceSoftware) solutions with annotations:
|
||||
|
||||
* ☉: [Archivist's toolkit](http://archiviststoolkit.org/) [user manual](https://www2.archivists.org/sites/all/files/BHS%20Archivists'%20Toolkit%20Manual_2015%20revisions.pdf)
|
||||
* (too) old ("the first open source archival data management system to provide broad, integrated support for the management of archives")
|
||||
* written in java
|
||||
* ☉: [collectiveaccess](https://collectiveaccess.org/) [demo](https://demo.collectiveaccess.org) [manual: data modelling](https://manual.collectiveaccess.org/providence/user/dataModelling/index.html)
|
||||
* since 2003; developed by company [Whirl-i-Gig](https://www.linkedin.com/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](https://manual.collectiveaccess.org/providence/user/dataModelling/profiles/MetadataStandards.html)), 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](https://archivesspace.org/features)
|
||||
* seems to require membership (if not now, it may do so later) with membership fee costs
|
||||
* ☉: [AtoM](https://www.accesstomemory.org/de/) [wikipedia](https://en.wikipedia.org/wiki/AtoM_(archival_software)) [demo](https://demo.accesstomemory.org/) [docs](https://www.accesstomemory.org/en/docs/)
|
||||
* since 2007
|
||||
* requires PHP+MySQL, still php7 (PostgreSQL ["potentially compatible"](https://www.accesstomemory.org/en/docs/2.8/user-manual/overview/intro/)); [roadmap](https://projects.artefactual.com/projects/atom/roadmap); requires Elasticsearch as separate service
|
||||
* supports [standards](https://www.accesstomemory.org/en/docs/2.8/user-manual/overview/descriptive-standards/) ISAD(G)+EAD, EAC-CPF and SKOS (and ISAD, ISAAR, ISDIAH, ISDF) and Dublin Core, MODS
|
||||
* ☉: [Archivematica](https://www.archivematica.org/en/)
|
||||
* 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](https://archium.org/Archivdatenbank.html)
|
||||
* archium website is German only - seems to be a small company; risk of commercialization and relatively small user base
|
||||
* ☉: [Omeka](https://omeka.org/) 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](https://en.wikipedia.org/wiki/Linked_data)
|
||||
* 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
|
||||
|
||||
* [General resources and toolkits](https://www2.archivists.org/advocacy/publicawareness/resourcesandtoolkits)
|
||||
|
|
|
|||
Loading…
Reference in a new issue