• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Pekin eca2010-v2
 

Pekin eca2010-v2

on

  • 487 views

Gareth Knight's presentation at ECA2010 conference, 28-30 April 2010

Gareth Knight's presentation at ECA2010 conference, 28-30 April 2010

Statistics

Views

Total Views
487
Views on SlideShare
487
Embed Views
0

Actions

Likes
0
Downloads
4
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • I will present a case study of work being performed King’s College London case study to revise records management strategy to cater for current needs Themes: Re-appraise definition & criteria for a Record Challenges posed when attempting to archive digital Records Technical architecture and processes that may be developed to curate digital records
  • Introduce record and contrast to information
  • Key themes of a record
  • Introduce notion that criteria for definition of a record is influenced by external factors and therefore subject to change over time Records are a specialized form of information. Essentially, records are information produced consciously or as by-products of business activities or transactions and retained because of their value. Legal compliance requirements can change over time Subject to changing understand of business activities
  • KCL Archives & Information Management (AIM) operate as a central unit Institutional business records records created in the course of day-to-day business to the private papers of academics and ensure scrutiny of decision making by a wider audience and to demonstrate transparency and openness within publicly funded bodies. What do you keep and for how long? Increase paper content places strain upon physical storage space + increased storage costs Increasing staff time necessary to locate material to fulfil FOI requests Many, but possibly not all records, provide a specific function
  • New challenges, but also new opportunities New types of information are part of institutional business Management procedures are well defined for paper records, but undeveloped for hybrid or digital collections Information increasingly produced in digital form Increasing amount of content, but does it all have value in short and long-term?
  • a joint project with AIM and the fact you have a professional archivist and records manager on the team.
  • Introduce audit framework as a method of understanding To understand the types of information that are being produced, sought to examine data assets being produced Developed an assessment strategy based upon 6 stages Defines process for performing audit within college Consists of 6 stages Combines sections of Data Audit Framework (DAF), DRAMBORA, DIRKS & other audit work
  • Selected academic units that had data of particular value and/or identified as being at risk.
  • A second aspect of the audit work was to develop an understanding of the lifecycle of a digital object.
  • Applied DRAMBORA frameworks to identify and assess risks in data creation/management lifecycle
  • Storage - Potential for data loss in future
  • Project team identified several actions necessary to reduce likelihood of risks occuring: Policies: Review collection and curation policies for
  • The primary method that we intend to use to mitigate many of the risks is through the implementation of a
  • OAIS Reference model provides a standardised method of expressing the components of an digital repository – Ingest, Data Management, Archival storage, Administration, Preservation Planning and Access. These components process 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
  • Submission component: Alfresco CMS Community Edition provides submission interface and data processing functionality Archive component: Fedora Commons as back-end data archive Access component: Evaluating Muradora to provide web front-end for accessing archived content
  • Actions may be performed in sequence or in parallel jBPM may be used to
  • Majority of automated actions will be performed on deposit, once data has been submitted to archive
  • Authoritative Records ISO 15489 Information and Documentation -- Records Management, describes an authoritative record as being a record that has the characteristics of: authenticity reliability integrity usability As explained in ISO 15489, the aim of all records management systems should be to ensure that records stored within them are authoritative. Summarizing, an authoritative record: can be proven to be what it purports to be can be proven to have been created or sent by the person purported to have created or sent it can be proven to have been created or sent at the time purported can be depended on because its contents can be trusted as a full and accurate representation of the transactions, activities or facts to which it attests; is complete and unaltered can be located, retrieved, presented and interpreted Collection held in Alfresco until complete. It is only transferred into Fedora when one of two parameters are met Data files deleted from Alfresco

Pekin eca2010-v2 Pekin eca2010-v2 Presentation Transcript

  • Who Decides? Reinterpreting archival processes for the management of digital research Gareth Knight Centre for e-Research, King’s College London
  • Presentation Themes
    • Need to re-appraise definition & criteria for a Record
    • Challenges posed when attempting to archive digital records
    • Technical architecture and processes required to manage digital records
  • What is a record?
    • “ information created, received, and maintained as evidence and information by an organization or person, in pursuance of legal obligations or in the transaction of business ”
    • ISO 15489-1:2001. Records management
    • “ a specific piece of recorded information generated, collected or received in the initiation, conduct or completion of an activity and that comprises sufficient content, context and structure to provide proof or evidence of that activity “
    • The International Committee on Archives (ICA) Committee
  • What is a record?
    • “ information created, received, and maintained as evidence and information by an organization or person, in pursuance of legal obligations or in the transaction of business ”
    • ISO 15489-1:2001. Records management
    • “ a specific piece of recorded information generated, collected or received in the initiation, conduct or completion of an activity and that comprises sufficient content, context and structure to provide proof or evidence of that activity “
    • The International Committee on Archives (ICA) Committee
  • What is a Record today? What is a Record tomorrow?
    • Criteria for defining records that have archival value is subject to range of factors and may change over time:
    • Legal obligation:
      • Varies between institution of different type
      • Geographic location
      • E.g. Public Records Act 1958 (government), Data Protection Act, Freedom of Information (FoI) Act 2000, Environmental Information Regulations (2004), etc.
    • Proof of business:
      • What type of business? Commercial, non-commercial
      • Research as a business activity
    • Proof of activity:
      • May be broad. Influenced by function, evidential value, uniqueness
    • Memory of institution
      • Same as above – requires consideration of function, value, uniqueness and other criteria
  • Re-evaluating Records management at King’s College London
    • College Archives acquire, preserve and makes available all material of long-term, evidential and research interest that forms part of the College’s heritage
    • Acquisition policy:
      • Paper and electronic records of day-to-day business operation, private papers of academics and researchers and material related to College heritage
    • Preservation policy:
      • Preserve archives in their original physical format (storage, packaging).
      • Maintain in appropriate environmental conditions – in c ompliance with BS5454: 2000
    • http://www.kcl.ac.uk/iss/archivespec/spcm.html
  • New archiving challenges
    • New types of information:
      • Published research papers, research data – funder requirements for data management
    • Creation of increasingly diverse content types:
      • Hybrid (paper+digital), digital content
      • CAD designs, interactive resources, datasets. Publication of dynamic content
    • Update frequency:
      • Web site, blogs, twitter, object revisions. Versioning
    • Access lifecycle:
      • Technology dependencies – software & hardware
    • Uncertain value:
      • What is the business value? What period of time?
  • Preservation Exemplars at King’s (PEKin)
    • Project objectives:
      • Develop a management system capable of handling digital business records AND research material
      • Adopt a management strategy that brings together archival AND data curation approaches
      • Embed preservation practices within the institution through a multi-layered strategy:
        • work with central services to develop a preservation strategy and service for digital records
        • work with academic units and professional services to ensure local data producers and systems managers are provided with targeted advice, guidance and tools to support decision-making
    • Project Partners:
    • Centre for e-Research (CeRch) & Archives & Information Management (AIM) at King’s College London
    • Funder:
    • JISC Information Environment 09-11 preservation exemplars strand
  • Audit framework PEKin audit framework combines sections of DAF, DRAMBORA, DIRKS & other audit work
  • Audit management practices
    • Purpose of audit was to identify:
      • Functions within the organisation that create records
      • Who used records and for what purpose
      • Location and responsibility for storage
      • Time period they are currently / should be retained for
      • Future stakeholders that need/may wish to use records
    • Survey academic and business units
    • Core business units:
      • College Estates, Student Records, College Committees
    • Research groups:
      • Twins Early Development Study, Regional Information Collection Centre, Environment Research Group, Randall Division of Cell and Molecular Biophysics
  • Types of digital information
    • Business records:
      • Estates records – Property records, contract for building maintenance, Computer Aided Design (CAD)
      • Student Records – Students, courses, grades
      • Committee Records – Structure, operation
    • Research records:
      • Commercial – research data created for commercial purposes, e.g. pollution monitoring, patents
      • Funded research – Contracts awarded by funding bodies
      • Unfunded research – Academic researcher who has interest in topic
    • Each record has different value and retention period.
  • Many types of lifecycle Record lifecycle (variants: Information, data lifecycle) Access lifecycle (e.g. digital lifecycle)
  • Analysis of lifecycle risks
    • Identify & evaluate risks that occur in the lifecycle
    • Applied a ‘light touch’ DRAMBORA ( http://www.repositoryaudit.eu/) methodology to case studies. Influenced by DIRKS
    • Risk categories
      • Organisation Management, Staff, Tech Infrastructure, Acquisition & Ingest, Preservation & Storage, Access & Dissemination
    • Risk Description
      • Definition, manifestations, consequences, severity (risk impact x probability), mitigation strategies
  • Recognised risks
    • Storage:
      • Insufficient capacity: local drives, network drives, 3rd party server
    • Authenticity & integrity:
      • Unidentified/unknown change. Some staff rely upon print-outs of digital original
    • Archival value and retention period:
      • Different criteria & quality thresholds
      • Business records – Recognised legal value & retention period
      • Research data – Archival value of research papers understood. Retention period of data has, until recently, not been recognised
    • Access and usage:
      • Business records have well-defined period of primary use, but unrecognised secondary use
      • Research papers understood, but do not always consider datasets & other outputs
  • Risk management Strategy
    • Storage and management infrastructure:
      • Technical infrastructure to store and manage their data
    • Education:
      • Develop staff understanding of data management and archival principles
        • Topics include: Authenticity and integrity, assessment of archival value
        • Methods: Practical documentation on data creation/management, training events
    • Policies:
      • type of record collected, time period for collection, appraisal criteria for long-term retention
    • Procedures:
      • Data capture, curation, preservation
    • Developed with consideration of cost implications
  • KCL Archives Preservation Repository
    • An preservation repository for college data of short/long-term value:
    • Standards compliance
      • OAIS Reference Model, TRAC, ISO 15489
    • Bitstream preservation:
      • fixity creation/verification, online + offline storage
    • Information Content Preservation:
      • Format conversion, event logging – audit trail
    • Access:
      • Limited to archive reading room, catalogue descriptive MD to common standard
    • Interoperable:
      • Interact with other college & public systems eg student records
  • OAIS Reference Model
  • Technical Infrastructure
  • Alfresco Actions
    • Actions - a parameterized unit of work that can be applied to a node
    • Parameters – rules for action execution and type to be performed
    • jBPM synchronous or asynchronous workflows
    • Actions be performed at different stages of workflow
  • Ingest Actions
    • Content model compliance
      • Conforms to defined structure & object types
    • Fixity generation
      • All: MD5, SHA-1, CRC
    • Format identification
      • All: File(1), DROID
    • Technical metadata extraction
      • Format specific: JHOVE, MP3Info, others
    • Specification conformance
      • branch workflow according to threshold
    • Conversion to preservation & dissemination derivative
      • parameters for each format & licence
      • OpenOffice, ImageMagick, SoX
    • Data Packaging
      • Generate METS package, record action results as PREMIS Event
  • Archiving actions
    • Transfer into Fedora archive
      • when collection closed (e.g. all papers submitted for meeting collection
      • After specified time period, e.g. 3 months
    • Fixity verification:
      • Conform that fixity unchanged
    • Manual activity for future date:
      • Anonymisation in 2 years,
      • Re-appraisal in xx years – Retain or remove
    • Obsolescence monitoring?
      • Possible future implementation
  • Content Models
    • Content models define rules that govern collection structure, data type & behaviour
    • Preservation Archive Content Models designed with consideration of resource type and Alfresco & Fedora capabilities
    • Content model for each resource type composed of 3 layers
    • Each layer is a Fedora Object that contains different metadata
    Filing Cabinet Drawer Folder
  • 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
  • Findings (so far)
    • Data audit & risk analysis provide useful frameworks for analysing data management practices & justifying data archiving
    • No single definition of archival value – different criteria & quality thresholds
    • Application of archival principles to data assets provide demonstrable benefits
    • Duration requirements of business & research data are broadly similar
    • Digital repository architecture provide sufficient flexibility to manage data assets created for different purposes
  • Contact
    • Gareth Knight
    • Centre for e-Research, King’s College London
    • [email_address]
    • 020 7848 1979
    http://www.kcl.ac.uk/iss/cerch/projects/portfolio/pekin.html Centre for e-Research : www.kcl.ac.uk/iss/cerch Archives and Information Management (AIM) : http://www.kcl.ac.uk/iss/explore/team/aim