Archivematica integration handshaking towards comprehensive digital preservation workflows
Download as PPTX, PDF•0 likes•594 views
The document discusses the importance of integrating digital preservation workflows with a focus on systems like Archivematica and their role in the cultural heritage community. It highlights integration strategies with various repositories and tools, emphasizing collaboration among institutions to enhance the efficacy of digital preservation efforts. The conclusion underscores the need for interoperable ecosystems to ensure sustainable digital preservation solutions.
Archivematica integration handshaking towards comprehensive digital preservation workflows
- 1. Handshaking towards comprehensive digital preservation workflows Courtney C. Mumma, Artefactual #OR2015 @archivematica @arxiverdama June 10, 2015
- 2. we should be building systems that enable a high-level of linkability repositories need digital preservation
- 3. showing my hand ➢artefactual & archivematica ➢why integration ➢endpoints and how to integrate ➢open source vs. proprietary ➢scoping and requirements ➢some systems integrated with archivematica
- 4. who is artefactual? ➢ b. 2001: FOSS, standards-based solutions for the cultural heritage community ➢AtoM (description and access) and Archivematica (digital preservation) ➢ archivists, librarians and developers ➢ support, hosting, development, migration, training, theming
- 5. what does archivematica do? ➢standards-based digital preservation workflows in a web dashboard ➢incorporates FOSS tools to perform digital preservation functions ➢creates consistent, system independent AIPs, human readable in a file system
- 6. why do integration work? ➢leverage resources already invested ○ acknowledge systems of record and overlapping functionality ➢add value to repository ○ digital preservation workflows for diverse procedural contexts (ex: archives vs digitized content) ○ multiple endpoints for ‘handshaking’
- 7. why do integration work? ➢reduce duplication of effort between projects/systems ➢empower adoption by small/mid-sized institutions ○ if we work together rather than compete the community is larger and more powerful, sharing is possible, implementation is easier and training is more accessible
- 8. archivematica integration endpoints ➢handoff from source systems ➢access and description handoff ➢archival storage handoff ○ repositories ○ secure storage ➢administrative handoff
- 9. how do we do integration work? ➢consistently encourage and drive integration opportunities ○ we pay attention to the needs of the community ○ we pay attention to the direction of cultural heritage projects ○ we pay attention to cultural heritage system innovations ➢bounty model
- 10. system synthesis ➢AtoM ➢ArchivesSpace ➢Archivists’ Toolkit ➢Arkivum ➢CONTENTdm ➢DSpace ➢DuraCloud ➢ Fedora ➢ HPTrim ➢ Islandora ➢ LOCKKS ➢ OpenStack ➢ Hydra? ➢ DataVerse?
- 11. we prioritize integration work with other open source systems (but we’ll integrate with proprietary systems to meet you where you are)
- 12. OS vs proprietary handshaking open source ➢transparency ➢download/instal l current versions ➢configurable ➢aligned ideals proprietary ➢ can’t see the hand ➢ can’t get the hand ➢ what is the hand doing? ➢ too many unknowns
- 13. system synthesis ➢AtoM ➢ArchivesSpace ➢Archivists’ Toolkit ➢Arkivum ➢CONTENTdm ➢DSpace ➢DuraCloud ➢ Fedora ➢ HPTrim ➢ Islandora ➢ LOCKKS ➢ OpenStack ➢ Hydra? ➢ DataVerse?
- 14. scoping integrations ➢sponsoring partners and contributors ○ cultural heritage organizations of any size, including other developers ➢sponsor’s functional needs ○ realistic goals ○ limited resources to allocate to development, testing and training ➢no such thing as ‘complete’
- 15. scoping integrations ➢generalize needs to broader community ○ accommodate diverse workflows ■ no two institutional, or even unit, workflows are exactly the same ○ transparent during the development process ○ consistent attention to ecosystem ○ awareness of other projects, innovations and technological changes
- 16. some of the integration work we’ve done so far
- 17. source endpoints ➢sources of content to be processed in Archivematica ○ DSpace ○ DuraCloud (ArchivesDirect hosting) ○ CONTENTdm ○ BitCurator ○ Islandora ○ HPTrim
- 18. access & description endpoints ➢AtoM ➢Archivists’ Toolkit ➢ArchivesSpace ➢CONTENTdm ➢DSpace (pending)
- 19. storage endpoints ➢Arkivum ➢DuraCloud ➢Fedora (via Islandora integration) ➢LOCKSS ➢OpenStack
- 20. DSpace* ➢ingest exports ○ collection and/or item) ➢dark archive for a DSpace repository ○ descriptive and rights MD preserved ○ community/collection relationships preserved archivematica.org/en/docs/archivematica- 1.4/user-manual/transfer/dspace/#dspace sponsored by University of British Columbia
- 21. CONTENTdm ➢OCLC let’s us see their hand ➢Project Client DIP uploads ○ includes MD for simple and compound object(s) ○ maintains order of files and directories archivematica.org/en/docs/archivematica- 1.4/user-manual/access/contentdm/#contentdm sponsored by University of British Columbia
- 22. Islandora ➢Archidora ○ Islandora front-end ○ archival storage in Fedora ○ notification to Islandora github.com/discoverygarden/archidora sponsored by University of Saskatchewan
- 23. AtoM ➢upload access copies and MD from Archivematica to AtoM description ➢MD parsed into descriptive standards ○ (RAD, DACS, MODS, ISAD-G, EAD) ➢link to the AIP from description ➢arrange to levels of description reflected in AtoM accesstomemory.org
- 24. Archivists’ Toolkit ➢upload DIP MD (incl PREMIS rights/restrictions) from Archivematica ➢AT link to access copies on web server ➢generate EAD from AT archivematica.org/en/docs/archivematica- 1.4/user-manual/access/archivists- toolkit/#archivists-toolkit sponsored by RAC
- 25. ArchivesSpace ➢current integration similar to AT ➢coming soon: arrangement to AS resources from Archivematica Appraisal Tab archivematica.org/wiki/ArchivesSpace_i ntegration sponsored by RAC and by Bentley Historical Library
- 26. DuraCloud ➢store AIPs in DuraCloud ➢process and store AIPs in DuraCloud using ArchivesDirect ➢integration works without ArchivesDirect ○ local installations can leverage archival storage in their own DuraCloud instance created in partnership with DuraSpace
- 27. Other AIP stores ➢DSpace - pending Bentley work ➢Fedora ○ but not Fedora 4 (yet) ○ Archidora ➢LOCKSS ➢OpenStack
- 28. conclusion sustainable, digital preservation ready, repository ecosystems are interoperable
- 29. thank you! archivematica.org @archivematica accesstomemory.org @accesstomemory archivesdirect.org documentation and the user community is free & open