Overview and details of the sessions of this conference. Please select a date or room to show only sessions at that day or location. Please select a single session for detailed view (with abstracts and downloads if available).
P5C: Digital Preservation
Considering Open Access - Digital Preservation of arts research data: AKA Managing your “stuff”
The Glasgow School of Art, United Kingdom
Research data management (RDM) for open access (OA) involves maintaining, preserving and adding value to research data throughout its lifecycle. OA to data and research outputs in the visual arts is complex due to the non-standard nature of visual arts research and the practiced based approaches to research adopted. So how can visual artists comply with the ever-changing open access policies and funder requirements for open access, and suitably manage their “stuff” – a way that data in the arts can defined? This paper aims to highlight the complexities of data management in the visual arts, the management of one’s “stuff”, and relate this to the issues surrounding open access of data and data preservation.
We Don’t Make Your Preservation Program, We Make Your Preservation Program Better
University of Connecticut, United States of America
The Connecticut Digital Archive (CTDA) http://ctdigitalarchive.org is a preservation repository open to Connecticut-based non-profit archives, libraries, cultural, educational, and memory institutions. A service of the University of Connecticut Libraries in collaboration with the Connecticut State Library, the CTDA has adopted a service catalog, use-only-what-you-need approach to providing repository services. Participating institutions may use as few or as many CTDA services as they see fit. With a low barrier to entry and no up-front repository costs, both small and large institutions are able to participate in digital preservation as well as larger presentation and discovery services. The CTDA’s approach is built on developing flexible and extensible services driven by participants’ needs. A continually evolving dialog between repository staff and participants means that repository staff work to tailor services, training, and documentation for participants, keep documentation current, and continually develop on a number of fronts simultaneously. By dis-integrating repository services, we allow each institution to create its own version of perfection.
Bit Preservation at the Digital Repository of Ireland
Trinity College Dublin
The Digital Repository of Ireland is the national digital repository for Ireland's social and cultural data. The goal of the DRI is to build an interactive trusted digital repository (TDR) by following the Trusted Repository Audit Checklist (TRAC)1 and gaining Data Seal of Approval (DSA) certification. To achieve this, it was necessary to build a preservation infrastructure that could address the requirements of TRAC and the DSA. These include the need to have a robust Archive Information Package (AIP) format, independent replicated and fault tolerant storage pools, georeplicated copies, tape cold storage, integrity testing/auditing, disaster recovery and high standards of systems security . Problems encountered included how to deal with versioning and how to implement a delete policy in a preservation infrastructure. Here we present some of our experiences as a guide to others developing a preservation infrastructure.
Archivematica Integration: Handshaking towards comprehensive digital preservation workflows
Artefactual Systems, Inc., Canada
The open repository ecosystem consists of many interlocking systems which satisfy needs at different points in content management workflows, and these differ within and among institutions. Archivematica is a digital preservation system which aims to integrate with existing repository, storage and access systems in order to leverage the resources that institutions have invested towards building their repository over time. The presentation will cover every integration the Archivematica project has completed thus far, including Dspace and DuraCloud, LOCKSS, Islandora/Fedora, Archivists' Toolkit, AccessToMemory (AtoM), CONTENTdm, Arkivum, HP Trim, and OpenStack, as well as ongoing projects with ArchivesSpace, Dataverse, and BitCurator. Each of these projects has had its own set of limitations in scope because of the requirements of the project sponsor and/or the limitations of other system, so in many ways several of them are not, and may never be 'complete' integrations. The discussion will explore what that means and strategies for expanding the functional capabilities of integration work over time. It will address scoping integration workflows and building requirements with limitations on functionality and resources. We will examine how systems can be built and enhanced in ways that accommodate diverse workflows and varied interlocking endpoints.