This document discusses the Cleveland Museum of Art's project to create an archival repository for its digital assets using cloud storage and open source software. An interdepartmental team was formed to inventory assets, identify standards, select a storage platform and management system, and define workflows. They chose a cloud-based storage solution with an in-house archival management system (AMS) to address concerns about performance and costs. After 9 months of ingesting assets like photographs, documents and audiovisual materials, challenges remain around staff time, storage capacity, and demand for additional systems.
Time, Stress & Work Life Balance for Clerks with Beckie Whitehouse
MW2014 Art in the Clouds Alexander+Krause
1. Art in the Clouds
Creating an Archival Repository
for Museum Assets
using Cloud Storage
and Open Source
Jane Alexander & Niki Krause
Cleveland Museum of Art
13. Inventory & Projections
• artwork photography
• conservation photography
• editorial photography
• business documents
• AV of institutional history
• AV of lectures, performances
• artwork in time-based media
= 20TB now, 35TB by 2018
14. Standards
• LOCKSS & archival best practices
• OAIS reference model
• preservation file formats
• PREMIS
• descriptive & technical metadata schemas
• Dublin Core (DCMI)
• IPTC, XMP, etc. mapped to DCMI
• local metadata needs = local schema
15.
16. Storage Platform Options
• onsite hardware/storage + AMS
• SaaS/hosted solution
• cloud-based hardware/storage,
with in-house AMS administration
…but there were concerns!
27. Ingest Progress @ 9 Months
• editorial photography — ⅔ ingested
• artwork photography — ½ staged, mapped
• conservation photography —
file name review+de-duping underway
• business documents — scripting xformations
• AV — detailed inventory, analog to digital
• artwork in time-based media
– 10 works accessioned so far
– team working on in-house standards
28. Challenges
• developer is leaving the museum
TOMORROW
• staff time
– Digital Archivist
– Conservation and PAMF staff availability
• network storage running high
• demand for more DSpace installs
Notas del editor
A year ago, we started contemplating an “art in the clouds” project… it turned out to be a much bigger project, and fit in a much bigger picture than we originally thought…
When I arrived at the museum, I looked at everything, and started the work of formulating a tech-side digital strategy, using Gallery One and ArtLens as a a test bed...
We found that our back-end systems naturally fell into functional groups, and could be tied together... this diagram shows the backbones, and the context of this presentation is here, in the collection-information and scholarship backbone. (flip to next slide to highlight)
The project started with a visit I made to our photo studio in 2010...
Here is Bruce, our Photo Studio Manager, with the working copies of the artwork photography master DVDs -- there are 3800 here, and twice as many stored in remote locations.
obviously, those masters a vital for both documentation and research, and worth their weight in gold... Bruce keeps them neatly stacked, as you saw.
But finding just the digital file needed for any one purpose was like finding something in the dragon's hoard, and it the process is time-consuming and far from efficient.