The document discusses challenges in archiving digital records and research data. It summarizes an audit of King's College London to identify digital information created, how it is used, and preservation risks. The project aims to develop a system for managing both business records and research material. Risks identified include insufficient storage, authenticity, and unclear retention periods. Strategies include technical infrastructure, education, and policies to address these risks and help preserve digital assets long-term.
23. Content Model examples Each item represents a Fedora Object Each FO holds user provided metadata Different MD required at each layer Filing Cabinet Drawer Folder
24.
25.
Editor's Notes
I present a case study of work being performed at King’s College London to revise its records management strategy. The presentation will cover 3 key areas: The importance of re-evaluating definitions and criteria for what constitutes a Record to an institution on a regular basis Examine challenges that may be posed when attempting to manage the lifecycle of digital record Tthe technical architecture and processes that KCL has adopted to manage digital records.
This slide introduces a record, describing its purpose and role within an institution. Definitions provided by the ISO Records Management specification and ICA establish a distinction between information and records While an institution will produce or maintain many types of information, not all of this information will constitute a record
In this slide, I highlight key terms in the definition that are useful for making a distinction between the two. Key is the relationship between the data, key stakeholders and the set of activities that are performed within the institution. The Records Management standard places an emphasis upon activities related to business transactions & legal requirements, whereas The ICA adopts a broader perspective, by considering the evidence base necessary to understand any type of activity. It is left to the institution to decide which business transactions or activities should be recorded.
Criteria for determining types of resource to maintain must be continuously reviewed and updated to meet with contemporary aims and objectives of the institution The criteria for determining what is a Record may evolve over time as a result of many factors, including alterations to the legal framework and changing interpretations of the business of the institution. For an academic institution, records traditionally include its operational conduct and teaching activities. In recent years, institutions have begun to recognise that other types of activity play a key role in their business and have developed broad criteria to encapsulate research and other types of information that represent the memory of institution
We are currently addressing many of these issues at King’s College. College data is managed a central archives service. The service currently collects business records, college heritage resources & private papers. For the most part, these resources are paper-based. Evidence of this can be seen in the preservation policy that emphasises maintaining records in their original form & storing them in appropriate environmental conditions.
In recent years there has been a recognition there is an increasing amount of information being created & published of archival value that are not covered by the policy and that new practices are required to manage this content. Specifically, the growth of electronic creation & publication methods presents new challenges in the archival approach that is taken. Resources are increasingly complex, in terms of their composition, e.g. hybrid archives that are composed of paper & digital, as well as the type of content that is created (e.g. CAD drawings, interactive resources). Many of these resources do not have a paper equivalent. The frequency of content creation, revision and publication and technological dependencies presents new challenges for an archivist.
To examine these issues in detail, we obtained JISC funding and are currently developing a management solution that can be applied to the broad range of business and research data that is being produced by the college. Our strategy combines the skills and expertise of archivists and digital curators to ensure that digital resources of archival value remain accessible and usable for the period of retention. This is achieved through a two-layered strategy: Work with academic units to understand their production workflow and identify the type of risks that may limit the long-term access. Work with central services in the college to identify gaps and areas for improvement in their management infrastructure. The outcome of the project will be the development of a digital repository for the preservation of research and business data of archival value and a over-archiving strategy for managing data within the college.
To understand the type of information being produced and their management requirements, we developed a bespoke framework for auditing each academic unit. The framework draws upon and combines sections of several existing methodologies, including Data Audit Framework, DRAMBORA and others We have extended these, through modification of the lifecycle model and extension of the vocabulary that was used. Although certain aspects of these frameworks were designed for a digital repository environment, they have proved useful for understanding data management issues in the wider context
A data audit was applied to selected departments within the college that were identified as having data of particular value or at particular risk. Wished to understand the functional activities performed, the type of information created, the reason that the data was used, who was responsible for these resources and the time period that they were stored for. The audit process was time-consuming to perform and required perserverance. However, by end of audit, we were able to produce a detailed case study for each department or service.
The audit identified many types of digital information being stored in each dept. These were frequently produced in-house, but also came from external sources. Each department considered their data assets to be valuable, but used different criteria for understanding value & adopted different approaches for maintaining them.
A second aspect of the audit work was to develop an understanding of the digital object lifecycle. Digital information may be subject to several types of lifecycle We have the record lifecycle (on left) which emphasises the creation & use of a resource, as well as an appraisal process that may result in its destruction or re-use for different purpose We also have the cycle of access, represented by the digital lifecycle, that focuses upon the access period of the storage format. An encoding format may be created by a business, who will publish it, revise it over time to perform new functionality, and at some stage, make a decision to withdraw the format from usage or make the specification available for use. The ability to access information stored in the format will often depend upon where the format is in its lifecycle. Content stored in a older format that has been subsequently revised, replaced or withdrawn may be more difficult to access and recreate.
As a result of the recognition that digital information has a lifecycle, we must also recognise that events may occur that reduce the likelihood that long-term access can be retained. To understand these events, we applied a ‘light touch’ version of the DRAMBORA risk assessment methodology to each case study. DRAMBORA was originally developed to analyse risks that may occur in a digital repository. For the ‘light touch’ version, we focused upon risks during the lifecycle, from creation to dissemination, as well as aspects of the staff and technical infrastructure components that affected the object. Each risk was documented, describing when it may occur, the potential consequences and one or more mitigation strategies that could be implemented.
As a result of the risk analysis, we identified a number of management issues. These may be classified into four categories: Storage issues were the most common. Many staff were reliant upon USB disks & various free & for-cost 3rd party systems to store their data. This presented the risk that data could be lost or corrupted at any stage. Authenticity was a concern for all staff. Several less technical staff were reliant upon printed copies because they did not trust the digital copy that had been produced. In addition, the archival value & retention requirements were unknown. Assessment of the value of digital information was intrinsic in many department’s operation, but implementation varied between staff members.
To mitigate the risk of loss or corruption of data during its lifecycle, we identified four key issues that we would have to address The First and perhaps most obvious issue is that a technical infrastructure must be provided to each dept. to store their data. These system should provide services to maintain authenticity and integrity Second, education is required to help staff understand data management and archival principles through provision of training events and supporting documents Third, consistent policies are required at the institutional level that indicates the type of digital information that have archival value. Finally, procedures are required to acquire, curate and preserve data in an archival environment.
To reduce the likelihood of many risks, we’re developing a preservation repository that will be used to manage college data of short & long-term value. For the last section of this presentation, I will examine various aspects of the repository. In abstract, it was identified that the repository should: comply with necessary standards, such as OAIS and Trusted Repositories comply with records management strategies, by providing bitstream and content preservation. It should also be able to interoperate with other institution systems and provide controlled access to resources.
A widely known repository specification is the OAIS Reference model, which provides a consistent method of expressing the components of a digital repository – Ingest, Data Management, Archival storage, Administration, Preservation Planning and Access. These components are responsible for processing the digital object at each stage of the workflow, changing it from a Submission Information Package into an Archival Package suitable for preservation and a Dissemination Package suitable for access & use
In practice, the preservation repository is composed of several technical components that enable the archive to fulfil the functions of an OAIS. The Alfresco CMS (on left of screen) is being used to provide submission interface and data processing functions. Alfresco was chosen based upon its extensive plugin support & ability to create complex content models. Data is stored temporarily in Alfresco, until a time when the collection is closed. At this stage the data is transferred into Fedora Commons for archiving. This stores all data and metadata in its various versions. To provide controlled access, we’re currently testing Muradora as a front-end and using add-ons such as Tika and Solr to provide metadata and full text searching
The processing workflow is expressed as a Business Processing Model (BPM). During the workflow, key activities are performed on each digital object. Alfresco actions are used to configure the type of events that occur, when they are initiated and the type of resource they are applied to. These are configured by defining various parameters. These activities can be organised into sequential or concurrent stages as required
The primary stage where actions are performed is on receipt of the data. Actions will include: Checking that the data structure conforms to the specified content model (mentioned in later slide) Creation of fixity values for each file Format identification, which will lead into use of format specific tools to perform technical metadata extraction. And conversion into appropriate preservation and dissemination formats Each activity will be logged & stored as PREMIS Event metadata
At a later stage, the data and metadata will be archived. A collection is held in Alfreso until one of two parameters are met: The collection is designated as closed by an archivist, or A specified time period has elapsed, e.g. 2 months after deposit. The parameters that are set will vary, dependent upon the broad category of data. Actions will be performed at later periods during the lifecycle. E.g. fixity checks will be performed to validate that the on-disk data is unchanged. Additional actions may be set by the archivist or depositor. For example, re-appraise content every 5 years to determine if it should continue to be stored, or to change the access status of the resource after an embargo.
Content models define the organisational structure of different types of collection, type of content that can be stored & behaviours of individual components. For the repository, we adopted a three layer structure for each collection type. These are organised hierarchically. A comparison may be made to a filing cabinet that contains a set of shelves, each of which may contain one or more folders
The diagrams on screen show examples of the content model that have been developed for committee records and research projects. A committee records is sub-divided into meetings that occurred on specific dates. Each meeting will posses an agenda, minutes of previous meeting, various papers. At a later stage, the minutes of the current meeting will also be added. Research project also have a 3 layer structure broken into year of project, which has been separated into different types of content.
To conclude, digital resource represents a challenge for archives to maintain, but also present opportunities for re-assessing implementation of archival practices. We have found that data audit & risk analysis provide useful frameworks for understanding the information lifecycle and justifying archiving of these resources Although digital resources created for business and research purposes perform different functions in institution, process of managing them remains broadly similar and can be automated to some degree in a shared system. Finally, I think the process has demonstrated the value of applying archival techniques to the management of digital resources. It has been invaluable in understanding the storage and management requirements of the college and identifying further areas for development.
![Presentation Themes ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)