Slide notes for presentation to Toronto Area Archivists' Group, Sept. 11th 2015. See also slides: http://www.slideshare.net/Archivematica/getting-started-with-atom-and-archivematica-for-digital-preservation-and-access-52764372
3. ability to strip filenames that come from Archivematica
accessibility enhancements including better keyboard navigability
table view of institutional browse
a “clipboard” for researchers to save groups of records
an optional new treeview which takes up the same width as the description column
much more!
slide 16
● Archivematica must be installed on an ubuntu web server. To install Archivematica, you
should be comfortable logging into a server, downloading packages and running
installation scripts.
● Archivematica in a sense comes with three parts to install the dashboard, which we just
looked at, a separate application called the Storage Service, and a package of
dependencies so that Archivematica can run them as microservices.
● Folks often ask, how big of a server do I need? How much storage do I need? We have
recommendations in our documentation, but the short answer is larger collections will
require more processing space and obviously more storage space. In addition to the
space you need to store the collection, you should have at least 20 additional GBs.
● If you’re just trying it out, we have an online demo you can use; if you want to run tests
with your own material, you might consider downloading to a desktop running Ubuntu.
slide 17
● We’re offering a hosted service with DuraCloud now called ArchivesDirect. DuraCloud is
part of Duraspace, an American nonprofit which is dedicated to helping libraries and
archives preserve and make available digital assets. Because DuraCloud is American,
the servers are in the States which causes some problems for many Canadian
institutions who want to use the service.
● We’re also involved in a consortial hosting systems through the Council of Prairie and
Pacific University Libraries. The hosting is done at UBC, but is only available to COPPUL
members.
● Plans are in the works for a Canadianbased hosting solution for Archivematica. You can
expect more news on this by early next year. We want Canadian institutions to be able to
use Archivematica more easily, and by offering the system in a hosted environment, you
can worry less about the tech and more about the actual archivist work needed to
preserve digital material.
slide 18
● There are different “flavours” or “levels” of digital preservation and I’m not here to tell you
that it’s our way or the highway. But the advantage of using a system like Archivematica
is that it bundles together many discrete digital preservation tasks and runs them all on
your content tasks like fixity checking, virus scanning, file format identification and
4. characterization, and normalization into formats that are considered friendly for longterm
preservation and access. A repository system like Fedora or Islandora can be
complemented nicely by Archivematica, allowing you to sleep a little better at night
knowing that you’ve taken additional steps towards longterm digital preservation.
slide 19
● Archivematica is purposefully storage agnostic, which allows it to connect to a number of
different storage options:
○ You can store your preserved material on networked servers
○ You can use cloudbased storage like DuraCloud or Arkivum
○ You can use an object store like Swift
○ You can store packages in LOCKSS
○ Fedora storage could be experimented with at this stage
○ In the future you’ll be able to store preservation packages in DSpace.
● Archivematica comes with a Storage Service to help you manage the packages you’ve
put in storage, but deciding on which type of storage to use is outside the purview of
Archivematica’s activities. It’s most likely to depend on your institutional environment.
slide 20
● We consider AtoM to be the “default” access system for use with Archivematica, but
other systems that have some manner of integration include CONTENTdm, Islandora,
DSpace, Archivists’ Toolkit, and soon, ArchivesSpace.
● You can also make packages of material for access and store them/download them and
manually upload them to other systems if you desire.
● Our philosophy is, your preservation system shouldn’t dictate how you provide access to
your digital material. We believe in creating many possible connections between the
software in your arsenal we like to think of it as “handshaking”.
● This process can also work the other way around you may have an institutional
repository such as DSpace into which students and faculty deposit material directly, and
then you can use Archivematica to ingest that material as a preservation backend.
slide 21
● The degree of automation is largely up to you. Most of Archivematica’s processes can be
automated by changing the administrative settings in the web interface.
● Further automation can be achieved through special scripts that we call “automation
tools”. We have users who have Archivematica running in the background on materials
with literally no human intervention unless there is an error to troubleshoot. To use these
tools, you would need to alter the scripts for your particular situation the scripts can do
things like look for particularly formated filenames, use metadata csv files to make
matches between metadata and digital objects, etc.
● I think of automation like this: the more uniform your materials are, the more likely you’ll