This work is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.

SJSU iSchool Colloquium Sarah Romkey, MAS/MLIS, Archivematica Program Manager

lead developers of Archivematica and Access to Memory (AtoM)

archivists, librarians, technologists

free and open-source digital preservation (AGPLv3)

best practices and standards

no barrier to user groups, community or documentation

consistent, system independent Archival Information Packages (AIPs)

Bagit, Dublin Core, METS, PREMIS

bigger on the inside

more than storage: metadata, logs, formats and structure to protect against software

obsolescence

Archivematica makes Archival Information Packages (AIPs)– integrity & virus checks, format identification, characterization & metadata extraction, forensic activities, validation, arrangement, transcription, etc

– normalization on ingest + preservation of the original file to sustainable formats

– bagged AIP with logs and metadata (METS.xml)

– include or add metadata, including PREMIS rights and restrictions

– storage agnostic

Archivematica makes Dissemination Information Packages (DIPs)– normalizes to access-friendly formats (when possible)

– integrates or hand-shakes with a number of access systems:

• AtoM (Access to Memory)

• CONTENTdm

• Archivist’s Toolkit

• ArchivesSpace

• Islandora (deposit system)

• DSpace (deposit system)

Digital Preservation options

- Rely on functionality within other systems- E.g. repository system

- Home-grown system- You must maintain the code- You/your staff are the only ones with expertise

- Manage digital preservation actions tool-by-tool- Difficult to maintain- Need relatively high level of expertise

- Digital preservation systems- Come in proprietary and open-source forms

Why open source for digital preservation?

- Understand your system and what’s happening “under the hood”

- No vendor lock-in: take your AIPs and store in another system if desired.

- Use open standards and open formats for metadata and packaging

- Benefit from the “network effect” of information sharing and constantly improving software tools

- Actively participate in the future of the tools that you use

What makes open source hard?

- Free like a kitten- no such thing as a free lunch!- Need some in-house technical ability, or willingness to

buy services- Active participation in open-source community takes

time- Institutional buy-in (although this is improving)

documentation: archivematica.org & accesstomemory.org

online demo: sandbox.archivematica.orgUser: demo@example.comPassword: demodemo