Along time some 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. This Use Case represents the typical event in the life of a preservation system, which has to be considered as a dynamic process that evolves as new needs arise in order to maintain the capability to preserve, access and understand data.
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
Step 1: Something changes
Notification to data manager of changes that affect the data usability, using the Orchestration service)
Step 2: Manager responds to the change
- 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:
- 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.
- Preservation Network Model needs to be updated, using the Preservation Strategy Toolkit and the RepInfo Registry Service.
Changes in the RepInfo network, using the RepInfo Toolkit and the RepInfo Registry Service.
- 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.