Scenario 1

A repository manager must create a sustainable plan for the preservation of a dataset. Steps include:

Activity WP
Arrange training on preservation of datasets covering all the elements in APARSEN - using consistent terminology

Check on consistent vocabulary
agree on the designated community for the dataset WP25
create preservation strategy also SCIDIP-ES
-- identify preservation tools which are likely to be appropriate for this type of data WP14
-- identify services which can help in preservation WP21 and SCIDIP-ES
-- identify optimal storage system to use WP23
-- identify persistent identifiers to use WP22
collect evidence of authenticity WP24
-- integrate provenance which came with the dataset into the repository’s provenance tracking system. Essentially preservation (interoperability and use) of the provenance information WP24
-- check fixity information WP24
collect evidence about the quality of the data WP26
estimate cost of preservation and negotiate with funders about quality of service and acceptable risks WP32
create business case WP36
-- identify potential wider set of users and potential benefits WP25/WP36
attempt to obtain trustworthy status in order to help attract further deposits of data WP33

Scenario 2

The User accessing the SCIDIP-ES data is able to retrieve the data itself and all the additional information needed to understand, analyse and process it. Steps include:

Activity WP
User, belonging to a Designated Community, searches for data required.  
User selects a specific dataset  
Representation Information which enables the dataset to be understood by the Designated Community is made available (if possible) WP25 plus SCIDIP-ES
-- if there are gaps in the Representation Information then new RepInfo may be collected by the Repository WP14 plus SCIDIP-ES
-- the data may be transformed to make it easier for the user WP21 plus SCIDIP-ES
-- the data plus RepInfo may be packaged together of reuqired SCIDIP-ES
-- check fixity information WP24
-- identify persistent identifiers to use WP22
Provide evidence of authenticity WP24
Provide any available evidence about the quality of the data WP26

Scenario 3

Changes take place in the preservation chain. The changes could affect the user community, the data itself (new processors, new formats), or the associated RepInfo (new auxiliary files available, new calibration campaigns). The Preservation Network Model and/or the RepInfo Network associated to the data must be updated correspondingly. Steps include:

Activity WP
The Data Producer/manager is informed (e.g. by data users via the Orchestration Service) that some changes in Designated Community knowledge could limit or prevent the ability to retrieve or to use a dataset properly in the future. He uses services and toolkits to update the archive and to ensure the continuity of data usability. Changes could happen in the following contexts (the following examples are only an indication):
SubCase 1 - Change in the DC (e.g. new DC)
SubCase 2 - Change/Error in the RepInfo Network
SubCase 3- Change in technology (e.g. sw obsolescence, IPR, policies)
SubCase 4 - Evolution of the PNM (Preservation Network Model)
Data Manager accesses the PNM and performs an analysis of the new situation. Dependencies to be investigated by means of the Gap Manager and the RepInfo Registry can include: SCIDIP-ES
-- Changes in the Designated Community, which means new DC to be added; changes in the DC knowledge. By means of the Gap Identification Service and the RepInfo Registry Service, he updates modules and dependencies. WP25 plus SCIDIP-ES
-- Preservation Network Model needs to be updated, using the Preservation Strategy Toolkit and the RepInfo Registry Service. SCIDIP-ES
-- Changes in the RepInfo network, using the RepInfo Toolkit and the RepInfo Registry Service. SCIDIP-ES
-- Change in technology: some elements inside the PNM become out of date, are no longer maintained and some sort of migration/update and/or replacement is needed. The data manager performs the changes needed and uploads the updated PNM and an required RepInfo. These steps use the Gap Identification Service, the RepInfo Registry Service, the Preservation Strategy Toolkit, the RepInfo Toolkit, the Storage Service and the Packaging toolkit. The new AIPs are stored by the Storage Service. SCIDIP-ES
-- May need to Transform the data SCIDIP-ES
Collect evidence of authenticity WP24
Identify additional business case opportunities WP36

Integrating concepts:

  • Glossary based on OAIS terminology
  • Preservation concepts based on OAIS with additional ideas
  • Audit metrics as checklist - as used in WP32, 21 ..
  • insistence on evidence base underpinning claims/ decisions
  • combination of expertise needed to achieve preservation goals
  • there are gaps in our knowledge, some of which have been identified
Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r5 - 2013-08-12 - ReneVanHorik
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback