Archivematica Camp Houston Slides Stream1.pdf

Houston, Texas
November 14, 2018

Day 1 - Welcome!
▪ Logistics
▪ Food and drink
▪ Location
▪ Code of Conduct
▪ Outline
▪ Introductions

Day 1 - Outline
9:00-9:15 Welcome & introductions
9:15-10:30 Module 1 – Archivematica in context
10:30-12:00 Module 2 – How does it work
12:00-1:00 Lunch
1:00-5:00 Module 3 – Core functionality (with exercises!)
6:00-??? Social event @ 8th Wonder Breweries

Day 1 - Introductions
■ Artefactual
■ Ashley Blewer
■ Jesús García Crespo
■ Evelyn McLellan
■ Ross Spencer
■ Team Texas
■ Courtney Mumma
■ Bethany Scott
■ Camp Counsellors
■ Andrew Berger
■ Nick Krabbenhoeft

Module 1
Archivematica
in context

“active management of digital content over time to ensure ongoing
access” (LOC)
“series of managed activities necessary to ensure continued access to
digital materials for as long as necessary” (DPC glossary)
Definitions may vary but certainly DP is more than mechanics, more than
software, hardware, networks, 0s and 1s. DP also includes governance,
fiscal commitment, and a designated community
What is digital preservation?

Digital preservation is:
▪ Software and hardware
▪ Networks of systems that manage content
▪ The actual bits and bytes of data that we’ve decided need preserving
and the actions that we take to preserve them
But significantly, it is also:
▪ Governance
▪ Fiscal commitment
▪ A community

Three-legged stool
Archivematica easily fits in as the
technology leg of the three-legged
digital preservation stool, but it also
helps fulfil organizational elements
like preservation planning.

Organizational Infrastructure
What are the requirements and parameters for the organization's digital
preservation program?
Technological Infrastructure
How will the organization meet defined digital preservation requirements?
Resources Framework
What resources will it take to develop and maintain the organization’s
digital preservation program?

- Ingests digital content and perform various tasks to make
sure the same content is secure, identifiable, accessible and
capable of supporting the presumption of authenticity over
time
- A framework of policies and processes
- Helps to couple actions that enable long-term management
and accessibility of digital objects
What is a digital preservation
system?

What is a digital preservation
system?
A system built from tools that
perform a variety of
functions to ensure the
integrity and authenticity of
digital content
▪ Identifier assignment
▪ File format identification
▪ File format validation
▪ Metadata extraction
▪ Fixity checking
▪ Normalization
▪ Metadata generation
▪ AIP packaging

Responsibilities of the
institution
▪ Policies
▪ Organization
▪ Financial sustainability
▪ Designated community
▪ Above all, human behaviour

● Audit and certification of trustworthy digital
repositories – sets out comprehensive
metrics for what an archive must do
● Based on the OAIS functional model
● Archivematica fulfills many of digital object
management criteria in ISO 16363, but other
aspects must be fulfilled using
complementary systems
Archivematica and Trusted
Digital Repositories (TDRs)

What does Archivematica
promise?
■ Standards-based
■ Open source
■ Make system-agnostic, self-describing AIPs
■ Connect to producer / consumer interfaces
■ Connect to policies (preservation planning)

Development timeline
2008 2018
2014
2010
2009
Qubit-OAIS conceived
of as back end for
ICA-AtoM
Qubit-OAIS decoupled
from ICA-AtoM and
renamed Archivematica
City of Vancouver
Archives and UNESCO
fund the first alpha and
beta releases
Archivematica 1.7 was
released on May 1
Archivematica 1.0 is
released

BagIt
Standard for packaging multilevel, hierarchical content,
developed by the Library of Congress (USA)
METS
XML schema for encoding descriptive, administrative, and
technical metadata, also developed by the Library of Congress
Standards, standards, standards

PREMIS
Standard for defining preservation metadata, including
technical information about objects and information about
the actions taken on the objects in the preservation
repository
Dublin Core (ISO 15836:2009)
Standard for capturing descriptive metadata, developed by
the Dublin Core Metadata Initiative

PRONOM
Technical registry providing impartial and definitive
information about file formats, software products and other
technical components required to support long-term access
to electronic records, developed and maintained by the
National Archives of the UK.

Workflows and preservation actions

Archival Information Package (AIP)
Dissemination Information Package (DIP)
Information packages

● PREMIS, or Preservation Metadata Implementation Strategies, is the recognized standard for
metadata about objects in a digital preservation system.
● It captures technical information about an object in order to support the implementation of
preservation strategies such as normalization, migration or emulation (PREMIS Object)
● It describes relationships between digital objects (PREMIS Object)
● It provides an audit trail of actions taken by the digital preservation repository to preserve the object
(PREMIS Event)
● It names the individuals, organizations and software tools responsible for taking actions to preserve
digital objects (PREMIS Agent)
● It specifies the actions a repository is allowed to take to preserve digital objects (PREMIS Rights)
What is PREMIS for?
25

What is METS for?
● METS, or Metadata Encoding and Transmission Standard, was designed to support inter-repository
data exchange.
● It provides a wrapper for other metadata, such as PREMIS and Dublin Core.
● It defines relationships between digital objects and other digital objects, and between digital objects
and their metadata.
● It can be used to provide technical metadata about digital objects, although Archivematica doesn’t
implement it that way (we wrap PREMIS in it instead)
26

● Archivematica creates system-agnostic AIPs, meaning
that you do not require a particular system to store and
read AIPs in the future
● AIPs can be stored in any file system that permits
packaged formats (.tar files, .zip files)
● You can migrate AIPs between systems just like any
other type of file or package
System-agnostic packages

Microsoft Azure
Storing the AIPs

Sending DIPs to AtoM (Access To Memory)

Module 2
How does
Archivematica
work?

Deployment
Because Archivematica is not a single application but instead
consists of dozens of different components and tools, there are
many possible deployment configurations

Micro-services
•‘granular system tasks which operate
on a conceptual entity that is
equivalent to an OAIS information
package’ (archivematica.org)
•Micro-services are provided by a
combination of scripts and one or more
FOSS (Free and Open Source) tools
bundled in the Archivematica system
•Each micro-service results in either a
success or error state and the package
is then processed accordingly by the
next micro-service
Transfer
•• standard
•• bag
•• disk image
SIP
(DIP)
AIP

•Micro-services are
strung together
into workflows
•These workflows
are configurable
• Can be highly
automated or …not
Workflows

● AtoM
● BagIt
● Bulk_extractor
● ClamAV
● Django
● ElasticSearch
● ExifTool
● ffmpeg
● FFprobe
● Fido
● Python-lxml
● Seigfried
● Sleuthkit
● Tesseract
● Ubuntu Linux
● UUID
● Unar
● Zip
● FITS
● Gearman
● Imagemagick
● Inkscape
● JHOVE
● Md5deep
● Mediaconch
● MediaInfo
● NFS-common
● p7zip
FOSS tools

Storage
spaces
•Need to move
packages in and
out
• Transfer source
• Failures
• AIP storage
• DIP storage

Preservation planning (FPR)
•Business rules and tool commands for preservation events
• Identification (Fido, Siegfried)
• Characterization (Exiftool, FFprobe, FITS, Sleuthkit,
MediaInfo)
• Extraction (7zip, unrar-free, tsk_recover)
• Normalization (convert, ffmpeg, imagemagick, ps2pdf,
ghostscript, inkscape)
• Transcription (tesseract)
• Validation (mediaconch, JHOVE)

<metsHdr> METS header
<dmdSec> Descriptive metadata
<amdSec> Administrative metadata
<fileSec> File section
<structMap> Structural Map
The AIP METS file

METS Header
<mets:metsHdr
CREATEDATE="2016-03-28T23:15:51"/>
46

<mets:dmdSec ID="dmdSec_1"> The METS file can have more than one dmdSec
<mets:mdWrap MDTYPE="DC"> mdWrap means the metadata are included in the METS file, not referenced by it
<mets:xmlData>
<dcterms:dublincore xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dc="http://purl.org/dc/elements/1.1/"
xsi:schemaLocation="http://purl.org/dc/terms/ http://dublincore.org/schemas/xmls/qdc/2008/02/11/dcterms.xsd">
<dc:title>Pictures at an Exhibition</dc:title>
<dc:creator>Mussorgsky, Modest<dc:creator>
….etc.
47
METS DMDSEC

<mets:amdSec>
<mets:techMD>
<mets:rightsMD>
<mets:digiprovMD>
<mets:digiprovMD>
<mets:amdSec>
<mets:techMD>
PREMIS: OBJECT
<mets:rightsMD>
PREMIS: RIGHTS
<mets:digiprovMD>
PREMIS: EVENT
<mets:digiprovMD>
PREMIS: AGENT
48
METS AMDSEC

<mets:amdSec ID="amdSec_1">
<mets:techMD ID="techMD_1">
<mets:mdWrap MDTYPE="PREMIS:OBJECT"> The PREMIS Object entity semantic units go into METS techMD
<mets:xmlData>
<premis:object xmlns:premis="info:lc/xmlns/premis-v2" xsi:type="premis:file"
xsi:schemaLocation="info:lc/xmlns/premis-v2 http://www.loc.gov/standards/premis/v2/premis-v2-2.xsd"
version="2.2">
<premis:objectIdentifier>
<premis:objectIdentifierType>UUID</premis:objectIdentifierType>
<premis:objectIdentifierValue>bb52e3a0-ac5d-42c5...</premis:objectIdentifierValue>
….etc
49
METS AMDSEC: TECHMD

<premis:objectCharacteristics>
<premis:compositionLevel>0</premis:compositionLevel>
<premis:fixity>
<premis:messageDigestAlgorithm>sha256</premis:messageDigestAlgorithm>
<premis:messageDigest>a58b87cd1c92881f95f41a35b8b2945970ebf0876b4f…..</premis:messageDigest>
</premis:fixity>
<premis:size>186012</premis:size>
<premis:format>
<premis:formatDesignation>
<premis:formatName>Microsoft Word Document</premis:formatName>
<premis:formatVersion>97-2003</premis:formatVersion>
</premis:formatDesignation>
<premis:formatRegistry>
<premis:formatRegistryName>PRONOM</premis:formatRegistryName>
<premis:formatRegistryKey>fmt/40</premis:formatRegistryKey>
</premis:formatRegistry>
</premis:format>
50
METS AMDSEC: TECHMD CON’T

<premis:objectCharacteristicsExtension>[raw tool output]</premis:objectCharacteristicsExtension> This is
where technical metadata from ingested files go, having been extracted by tools like FIDO, Siegfried, Exiftool, MediaInfo, etc.
</premis:objectCharacteristics>
<premis:originalName>%transferDirectory%objects/letter.doc</premis:originalName>
<premis:relationship> This information shows a relationship between an ingested file and its normalized version, along with
a relationship to the normalization Event
<premis:relationshipType>derivation</premis:relationshipType>
<premis:relationshipSubType>is source of</premis:relationshipSubType>
<premis:relatedObjectIdentification> This is the relationship to the related normalized file
<premis:relatedObjectIdentifierType>UUID</premis:relatedObjectIdentifierType>
<premis:relatedObjectIdentifierValue>b041d811-879f-4640-8ea…</premis:relatedObjectIdentifierValue>
</premis:relatedObjectIdentification>
<premis:relatedEventIdentification> And this is the relationship to the normalization Event
<premis:relatedEventIdentifierType>UUID</premis:relatedEventIdentifierType>
<premis:relatedEventIdentifierValue>25ccf003-a007-4f12-be…</premis:relatedEventIdentifierValue>
</premis:relatedEventIdentification>
51
METS AMDSEC: TECHMD CON’T

METS AMDSEC: DIGIPROVMD (Events)
<mets:digiprovMD ID="digiprovMD_8">
<mets:mdWrap MDTYPE="PREMIS:EVENT">
<mets:xmlData>
<premis:event xmlns:premis="info:lc/xmlns/premis-v2" xsi:schemaLocation="info:lc/xmlns/premis-v2
http://www.loc.gov/standards/premis/v2/premis-v2-2.xsd" version="2.2">
<premis:eventIdentifier>
<premis:eventIdentifierType>UUID</premis:eventIdentifierType>
<premis:eventIdentifierValue>0e7fb257-ae9c-47f2-b4d9….</premis:eventIdentifierValue>
</premis:eventIdentifier>
<premis:eventType>message digest calculation</premis:eventType>
<premis:eventDateTime>2016-03-28T23:04:31</premis:eventDateTime>
<premis:eventDetail>program="python"; module="hashlib.sha256()"</premis:eventDetail>
….etc.
52

METS AMDSEC: DIGIPROVMD (Events)
<premis:linkingAgentIdentifier>
<premis:linkingAgentIdentifierType>Archivematica user pk</premis:linkingAgentIdentifierType>
<premis:linkingAgentIdentifierValue>1</premis:linkingAgentIdentifierValue>
</premis:linkingAgentIdentifier>
<premis:linkingAgentIdentifierType>preservation system</premis:linkingAgentIdentifierType>
<premis:linkingAgentIdentifierValue>Archivematica-1.6</premis:linkingAgentIdentifierValue>
<premis:linkingAgentIdentifierType>repository code</premis:linkingAgentIdentifierType>
<premis:linkingAgentIdentifierValue>NRI</premis:linkingAgentIdentifierValue>
53

PREMIS Events in Archivematica
● Ingestion
● Message digest calculation
● Fixity check
● Name cleanup
● Unpacking
● Virus scan
● Format identification
● Validation
● Normalization
● Compression
54

PREMIS Agents in Archivematica
● Institution
● Logged-in user
● Digital preservation system
55

METS AMDSEC: DIGIPROVMD (Agents)
<mets:digiprovMD ID="digiprovMD_58">
<mets:mdWrap MDTYPE="PREMIS:AGENT">
<mets:xmlData>
<premis:agent xmlns:premis="info:lc/xmlns/premis-v2" xsi:schemaLocation="info:lc/xmlns/premis-v2
http://www.loc.gov/standards/premis/v2/premis-v2-2.xsd" version="2.2">
<premis:agentIdentifier>
<premis:agentIdentifierType>repository code</premis:agentIdentifierType>
<premis:agentIdentifierValue>NRI</premis:agentIdentifierValue>
</premis:agentIdentifier>
<premis:agentName>Not a Real Institution</premis:agentName>
<premis:agentType>organization</premis:agentType>
</premis:agent>
56

METS FILESEC
<mets:fileSec>
<mets:fileGrp USE=“original”>
<mets:file>
<mets:file>
<mets:fileGrp USE=“submissionDocumentation”>
<mets:file>
<mets:file>
<mets:fileGrp USE=“preservation”>
<mets:file>
<mets:file>
57
Other categories include
“metadata”, “license”, “text/ocr”
and “deleted”.

METS FILESEC CON’T
<mets:fileSec>
<mets:fileGrp USE="original"> Identifies what the role of the file is in the context of this AIP
<mets:file GROUPID="Group-b041d811-879f-4640-8ea5-821920a81cf9" ID="file-b041d811-879f-4640-8ea...."
ADMID="amdSec_2"> Note the link to the related amdSec, which has all of the PREMIS data in it
<mets:FLocat xlink:href="letter.doc" LOCTYPE="OTHER" OTHERLOCTYPE="SYSTEM"/> This shows where the file
is located in relation to other files within the AIP
</mets:file>
<mets:file GROUPID="Group-002db941-78e1-4cbf-9bd9-afe7ef9c7466"
ID="file-002db941-78e1-4cbf-9bd9-afe7ef9c7466" ADMID="amdSec_4">
<mets:FLocat xlink:href="report.doc" LOCTYPE="OTHER" OTHERLOCTYPE="SYSTEM"/>
</mets:file>
58

<mets:fileGrp USE="preservation">
<mets:file GROUPID="Group-b041d811-879f-4640-8ea5-821920a81cf9" Remember the GROUPID on the previous slide?
ID="file-ty41d811-879f-4640-8vj5-848573a84jf9" ADMID =”amdSec_3”>
<mets:FLocat xlink:href="letter.pdf" LOCTYPE="OTHER" OTHERLOCTYPE="SYSTEM"/>
</mets:file>
<mets:FLocat xlink:href="report-f3d84155-3df1-427e-9ff8-5b480895372a.pdf" LOCTYPE="OTHER"
OTHERLOCTYPE="SYSTEM"/>
</mets:file>
59

<mets:fileGrp USE="submissionDocumentation"> Submission documentation gets its own fileGrp
<mets:file "Group-c01feb1d-cbcc-4a4b-a27a-3c1ba7618e99" ID="file-c01feb1d-cbcc-4a4b-a27a-3c1ba7618e99"
ADMID="amdSec_7">
<mets:Flocat xlink:href="objects/submissionDocumentation/Transfer1-
8e3003b8-a136-4bfc-b2f7-75d4fb637136/METS.xml” LOCTYPE="OTHER" OTHERLOCTYPE="SYSTEM"/>
</mets:file>
<mets:FLocat xlink:href="objects/submissionDocumentation/Transfer1-
8e3003b8-a136-4bfc-b2f7-75d4fb637136/DeedOfGift.pdf” LOCTYPE="OTHER" OTHERLOCTYPE="SYSTEM"/>
</mets:file>
60

METS STRUCTMAP
<mets:structMap>
<mets:Div> Directory
<mets:Div> Item
<mets:Div> Item
<mets:Div> Item
<mets:Div> Item
61

<mets:structMap ID="structMap_1" LABEL="Archivematica default" TYPE="physical"> The default Archivematica METS structMap
provides a simple physical listing of the AIP’s contents
<mets:div LABEL="Images-298af460-fdf4-4c78-ac8b-2f9266495f77" TYPE="Directory">
<mets:div LABEL="objects" TYPE="Directory" DMDID="dmdSec_1"> This is a link to the AIP’s descriptive metadata
<mets:div LABEL="letter.doc" TYPE="Item">
<mets:fptr FILEID="file-b041d811-879f-4640-8ea5-821920a81cf9"/> fptr = file pointer, a link to the relevant entry in the fileSec
</mets:div>
<mets:div LABEL="letter-f3d84155-3df1-427e-9ff8-5b480895372a.pdf" TYPE="Item">
<mets:fptr FILEID="file-eb4a2422-93e2-4c70-ab4c-a56b4eeadab0"/>
</mets:div>
….etc.
</mets:div>
<mets:div LABEL="submissionDocumentation" TYPE="Directory">
<mets:div LABEL="transfer1-540aec2f-9b01-463e-bf16-f12d6b58680c" TYPE="Directory">
<mets:div LABEL="DeedOfGift.pdf" TYPE="Item">
<mets:fptr FILEID="file-612db941-78e1-4cbf-9bd9-afe7ef9c7466"/>
….etc.
62
METS STRUCTMAP

ANOTHER METS FILE - THE AIP POINTER FILE
63

What does the pointer file describe?
● The format of the AIP (e.g. 7zip format) (PREMIS: OBJECT)
● Information about the compression event (PREMIS:
EVENT)
● The institution and preservation system that performed the
compression (PREMIS: AGENT)
● The location of the AIP (METS: fileGrp)
64

Core Functionality
▪Transfer (standard)
▪Ingest
▪Administration
▪Preservation planning

Hands-on exercises
Task #1 - Start a standard transfer
Task #2 - Review microservices
Task #3 - Create an AIP for long-term preservation
Task #4 - Examine microservice failures
Task #5 - Add descriptive metadata
Task #6 - Add rights metadata
Task #7 - Review your AIP
Task #8 - Automate workflow through configuration
Task #9 - Add item-level metadata using metadata.csv
Task #10 - Upload a DIP to AtoM

VMs
http://houston-amcamp-1.archivematica.org
…
http://houston-amcamp-15.archivematica.org
User: houston
PW: amcamp

Standard Transfer
• The most common kind of transfer for the kinds of documents we
often have in archives - images, video, audio, documents
• Standard transfers are a directory of digital content

Importing Submission Documentation
● Donor agreements, appraisal reports, notes about the
collection that aren’t part of the collection, etc.

Importing Descriptive Metadata
● Descriptive metadata added via a CSV file
● Works with any transfer type

Metadata.csv format
● You can mix metadata standards within your CSV, but only
Dublin Core will be natively recognized by Archivematica
(anything else will be categorized as “other”)

Metadata.csv Dublin Core ->
METS

Metadata.csv Non-Dublin Core
-> METS

Day 2
Houston
November 15, 2018

Archivematica Camp Day 2
9:30-11 Stream 1 - Building on core: Archivematica's specialized workflows
Stream 2 - Supporting Archivematica workflows
11:00-12 Community profile: University of Houston
12:00-1 Lunch
1:00-3:00 Stream 1 - Archivematica's non-core functionality
Stream 2 - Understanding Archivematica's logs and performance evaluation
3:00-4:00 Community profile: Computer History Museum and
New York Public Library
4:00-5:00 Agenda adjustment for Day 3 - what do you want to talk about tomorrow?
6:00-??? Small group dinners

Building on Core
▪ Transfer types
▪ Zipped files
▪ Manual normalization
▪ A peek at automation tools

Why use specialized workflows?
● to accommodate our pre-Archivematica workflows
● content is arriving at the Archivematica pipeline in a
packaged format
● formats with special requirements
● we want to do unique and customized things with
our data

Zipped/unzipped bag transfers
Zipped transfers:
● A .zip file of content that is organized using the BagIt
specification
● Includes data subdirectory, bagit.txt, bag-info.txt, etc. and has
been packaged in ZIP format
Archivematica can:
● Unzip the file to perform tasks and reuse some of the
metadata

Common use cases:
● Organization uses BagIt locally to package digital content
which they would then like to preserve in Archivematica
● Organization uses Exactly to transfer content from creators
to the archive

Unzipped transfers are:
● A directory of content that is structured according to BagIt
specifications
● Includes a data subdirectory, bagit.txt, bag-info.txt,
sha512-manifest.txt, etc.
Archivematica can:
● Reuse some of the metadata

Disk image transfers
Common use case:
● An organization has disk images for preservation
Archivematica can:
● Use forensic disk image tools to analyse the image (The
Sleuth Kit’s fiwalk)
● Append imaging metadata to the transfer

Hands-on exercises
Task #11 - Manual normalization
Task #12 - Follow that format: JPEGs

Manual Normalization
Common use case:
■ Organization manually normalizes files for access and
preservation and would like Archivematica to recognize
that work
Archivematica can:
■Work with manually normalized files on the Transfer tab
or on the Ingest tab

Other Specialized Workflows
● DSpace
● Including checksums
● Organization creates checksums locally and would like
Archivematica to recognize them

Module 5
Non-core
functionality

Non-core Functionality
▪ Automation tools
▪ Backlog and appraisal tabs
▪ AIP reingest
▪ Examine contents using BulkExtractor

Automation Tools
▪Set of python scripts to automate
▪Transfers
▪Create DIPs
▪Upload DIPs to AtoM
▪ https://github.com/artefactual/automation-tools

Non-core functionality
Hands-on exercises
#13 Send transfer to backlog
#14 Examine contents using Bulk Extractor
#15 Re-ingest an AIP

AIP Reingest
▪Metadata only
▪Partial reingest
▪Full reingest

Extra time?
AIP encryption
AIP deletion

Agenda adjustment for Day 3
What else would you like to see?
Anything you’d like us to cover more?

Day 3
Houston
November 16, 2018

Archivematica Camp Day 3
9:00-9:30 Arrival
9:30-10:30 Module 6: Stream 1 - Special Topics
Module 6: Stream 2 - AIPs for devs/syadmins
10:30-11:30 Module 7: Archivematica in the community
11:30-12:30 Brown Bag Lunch and Community topics
12:30-2:00 Module 8: Implementation roundtable

Module 6
Stream 1
Special Topics

Special Topics
▪ Handling complex media
▪ MediaConch
▪ ArchivesSpace integration
▪ PREMIS and Linked Data

Forensic disk images
- Disk image transfer type
- Funded by Yale in 2013
- Adds imaging metadata to the transfer
- Some limitations within microservices
- We use The Sleuth Kit’s fiwalk command
- Worked with UCLA/NYPL on HFS disk image analysis
- Extract or don’t extract? Depends

Follow That Format: MKV
▪ Validation tool – allows users to use MediaConch to
check the conformance of .mkv files (originals and
derivatives) against the Matroska spec
▪ Checks validity of media files against user-provided
policies
▪ Sponsored by PREFORMA Project
http://www.preforma-project.eu/

Looking to the future: PREMIS as linked data

Module 7
Implementation
Roundtable

Sharing is
Caring
How is your
institution
using
Archivematica?

Module 8
Archivematica in the
Community

Photo credits
▪ http://archives.newwestcity.ca/permalink/71868/

Archivematica Camp Houston Slides Stream1.pdf

Recommended

Recommended

More Related Content

Similar to Archivematica Camp Houston Slides Stream1.pdf

Similar to Archivematica Camp Houston Slides Stream1.pdf (20)

Recently uploaded

Recently uploaded (20)

Archivematica Camp Houston Slides Stream1.pdf