Downloaded 17 times
Uploaded byArtefactual Systems - Archivematica
Digital Preservation with Archivematica
The document covers the features and development of Archivematica, an open-source digital preservation application designed to ensure long-term access to authentic digital content. It emphasizes the importance of organizational readiness in digital preservation according to ISO standards and discusses community-based development practices. Additionally, it highlights partnerships and micro-services architecture for integration with various systems.
More Related Content
Similar to Digital Preservation with Archivematica
More from Artefactual Systems - Archivematica
Digital Preservation with Archivematica
- 1. Archivematica Digital Preservation with DanGillean Glenstone Digital Preservation Roundtable November 4th, 2016
- 2.
- 3. • Governance • Organizationalstructure • Staffing • Procedural accountability • Preservation policy framework • Documentation • Financial sustainability • Security ISO 16363Reminds us that much of digital preservation readiness is not technical – it’s organizational
- 4.
- 5.
- 6. WhatisArchivematica? Archivematica is aweb- and standards-based, open-source application which allows your institution to preserve long-term access to trustworthy, authentic and reliable digital content. Standards based Open source Customizable Integrated w 3rd party systems Active community
- 7. 20142008 2007: UNESCO REPORT0.1-ALPHA DASHBOARD INTRODUCED Archivematica’s development 0.7 1.0 RELEASED!0.9 0.8 Bradley, K., Lei, J., Blackall, C. Towards An Open Source Archival Repository and Preservation System (2007) Planning and development begin. Initial Funding via UNESCO MotW Subcommittee, IMF Archives, City of Vancouver Archives 0.6-ALPHA February 2010 May 2010 February 2011 February 2012 PREMIS in METS 0.10 April 2013 August 2012 STORAGE SERVICE 0.2 January 2014
- 8. Standards-based ISO 14721 (OAIS)PREMIS METS BagIT
- 10. PREMIS in METSXML ArchivematicaAIPstructure Packaged according to BagIt specifications Virus scan, normalization report, extraction log, etc For browsing in Archivematica Original + normalized objects, submission docs, original metadata included at SIP creation
- 11. <mets:amdSec> <mets:techMD> PREMIS: OBJECT <mets:rightsMD> PREMIS: RIGHTS <mets:digiprovMD> PREMIS:EVENT <mets:digiprovMD> PREMIS: AGENT PREMISinMETS METS SECTIONS <metsHdr> METS header <dmdSec> Descriptive metadata <amdSec> Administrative metadata <fileSec> File section <structMap> Structural Map
- 12. EmbracingOpenness Open Source Open Standards OpenFormats Open documentation https://commons.wikimedia.org/wiki/File:Postcards_and_magnifying_glass.jpg
- 13. A program isfree software if the program's users have the four essential freedoms: 1. The freedom to run the program as you wish, for any purpose (freedom 0). 2. The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this. 3. The freedom to redistribute copies so you can help your neighbor (freedom 2). 4. The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this. Free Software Foundation Free Software Definition https://www.fsf.org/licensing/essays/free-sw.html What isFree Software?
- 14. Whatis Freedom? https://commons.wikimedia.org/wiki/File:Beer_mug_transparent.png “ ” Freeas in… Beer? Speech? Kitten? http://www.freestockphotos.biz/stockphoto/9343
- 15. Whatis Freedom? “ ”It’sall 3…and that’s not a bad thing
- 16.
- 17.
- 18. Development Philosophy Community-based developmentBounty model of business • Standards-based • Open source / Creative Commons • Generalize specific use cases • Include all features in public release • Accept community improvements • Iterative development via multiple contributions over subsequent releases • Maintain: documentation, software, wiki, • Produce additional resources (e.g. videos, presentations, webinars) • Participate in user forum • Offer additional paid services • Always include development in public project
- 19. Do one thingwell… Micro-services Handshakes Partnerships Gears – Joe DeSousa. https://www.flickr.com/photos/mustangjoe/22711070429 Metal Handshake – Grey Geezer. https://commons.wikimedia.org/wiki/File:Metal_Handsha ke.jpg Hands Passing Baton - tableatny, https://www.flickr.com/photos/53370644@N06/497649 7160
- 20.
- 21.
- 22. Micro-services: Tools Used Bulk_extractor ClamAV Elasticsearch ExifTool Ffmpeg Fido FITS Gearman gzip Imagemagick Inkscape JHOVE md5deep MediaInfo NFS-common Python-lxml unar UUID …and more…
- 23.
- 24. Handshakes: AtoM ArchivesSpace Archivist’s Toolkit Arkivum Binder CONTENTdm Dataverse DSpace DuraCloud Fedora HPTrim Hydra Islandora LOCKSS OpenStack Still fromthe film Color Blind - Photograph by Pui Shan Chan February 2009. https://en.wikipedia.org/wiki/File:Black_%26_White_Handshake_-_Still_from_the_film_Colour_Blind_(2009).JPG
- 25.
- 26. archivesDIRECT • Partnership withDuraSpace • U.S. Based • Launched August 2014 • Secure storage and monitoring via DuraCloud • Artefactual provides AM technical support http://archivesdirect.org/
- 27. Perpetua • Partnership withArkivum • U.K. Based • Launched July 2016 • Secure storage and monitoring via Arkivum • Artefactual provides AM technical support http://arkivum.com/perpetua/
- 28. ArchivesCANADA Digital Preservation Service •Partnership with The Canadian Council of Archives (CCA) • Canada Based • Launched September 2016 • Artefactual provides AM technical support, storage, monitoring http://archivescanada.ca/ACDPS
- 29.
- 30. RESOURCESAM homepage: https://www.archivematica.org AMdemo: http://sandbox.archivematica.org Wiki: https://wiki.archivematica.org Documentation: https://www.archivematica.org/docs/
- 31. RESOURCESRoadmap: https://wiki.archivematica.org/Development_roadmap:_Archivematica Issue tracker:https://projects.artefactual.com/projects/Archivematica Code repo: https://github.com/artefactual/Archivematica Forum: https://groups.google.com/forum/#!forum/archivematica
Editor's Notes
- #7 Standards based: OAIS, PREMIS, METS, BagIt, Dublin Core Open source: A-GPLv3 license, free to study, use, modify, etc Customizable: Add/change/remove FPR rules as needed Integrated: dSpace, CONTENTdm, Islandora, LOCKSS, AtoM, DuraCloud, OpenStack, Archivist’s Toolkit, Arkivum, ArchivesSpace… etc Active community:
- #19 To support the original and ongoing aims of the project, Archivematica has always been, and will continue to be, released as open source software - currently, we release it under a strong viral license (AGPLv3) to ensure that the application is not forked or incorporated by someone wishing to charge access to its enhancements. In maintaining our commitment to the original project aims, we also seek in every way we can to lower or remove barriers to the project resources: to this end, Artefactual not only releases the code via our code repository, we also make our documentation available, our webinar recordings, our wiki resources, our presentation slides, and even as much free support as we can offer via the Archivematica user forum, all free of charge. With every major release, we also budget time to review and address many of the bugs reported to us by our user community, with the hope of seeing the project improve progressively in both large and small ways with each public release. To sustain ourselves as a business and be able to continue maintaining and developing Archivematica, Artefactual also offer additional paid services - including application hosting, consultation, training, theming, data migrations, and of course, custom development. This business model is sometimes known as "Professional open source" - at Artefactual, we think of it as the Bounty model of open-source development. As a company, we use our resources from these additional services to continue supporting the ongoing maintenance work required to keep the AtoM project sustainable and growing. Every time we are contracted to develop a custom feature for an institution, we work with the client to ensure the feature respects established national and international standards, and we try to generalize its implementation so it can not only meet the use case of the institution in question, but also be of benefit to the entire Archivematica user community. We then include all of these enhancements in the next public release. Whenever possible, we also accept bug fixes and code contributions from our user community, and will handle the review and merging of this code into public releases, as well as its maintenance through subsequent releases, thereby reducing the burden on individual contributors over time. We have a number of development resources on our wiki to help users get started. This is the community-based development heart of the Archivematica project. The growth and direction of Archivematica is determined by the individuals and institutions who recognize that open-source software requires maintenance to continue to be viable and relevant in the long-term, and who sponsor features, enhancements, and bug fixes that will benefit the project as a whole in addition to meeting their particular institutional or individual needs. This means that Archivematica, as an application, is truly what our community makes of it - the current version, like all versions before it, has been made possible thanks to contributions large and small from dozens of institutions and individuals. You can see this on the release announcements we maintain and on the Roadmap part of our wiki for the upcoming releases, where we try to acknowledge all the different institutions and individuals that have helped to make the new features possible. This is one of the joys of community-based development - seeing what we can accomplish as a community when we are all working towards common goals. It also means that institutions with more resources are able to invest in solutions that not only meet their needs, but also benefit the community at large and assist smaller, under-resourced institutions to have access to the same tools and applications. Everyone benefits from any single contribution - whether it is development or contributions to the project in other ways (documentation, user forum participation, papers and presentations, provision of services by other service providers, formation of user groups, and more).
- #24 From source systems Hand-off to access and description systems Hand-off for archival storage – repositories or other secure storage Administrative hand-off
- #25 From source systems Hand-off to access and description systems Hand-off for archival storage – repositories or other secure storage Administrative hand-off