The SCIDIP-ES manager constantly provides support in terms of archive definition and refinement. In details the data producer/manager:
- preserves objective and designated communities of the data in the SCIDIP-ES platform;
- defines the preserved data set content consisting of the set of data, information and SW tools necessary to achieve the preservation objective for all the identified designated communities;
- creates an inventory and collects all the data, information and SW tools previously identified;
- defines a Preservation Network Model (PNM) addressing the preservation of all those elements;
- set-up the Archive.
The Data Producer/manager plans the preservation of a specific dataset. He/she collects all data and related knowledge to be preserved. In addition he/she defines the preservation objective, the designated community, the dataset to be preserved, creates a checklist to identify where the dataset component are, identifies the main risks for preserving each piece of data and, after a risk assessment analysis, designs the dataset’s Preservation Network Model (PNM). Once the PNM has been defined, all the needed data has been chosen, he/she is ready to implement the archive.
Step 1: Identification of the preservation objective.
This results in the creation of a basic set of information related to the data to be preserved. This is done by taking into account the related preservation policies.
Step 2: Definition of communities and PNM
Definition of the designated communities (DC) and relative knowledge.The data producer defines a draft PNM. This is done by firstly identifying the dataset content, then by creating the data inventory, collecting all information related to all data set content to be preserved (location, physical state and ownership). The data producer and the data manager refine the PNM iteratively on the basis of the choices made about risk management helped by the Preservation Strategy Toolkit.
Step 3: PNM Consolidation
The PNM is consolidated and then stored by the SCIDIP-ES Manager using the Preservation Strategy Toolkit and the RepInfo Registry Service. Approach for preservation of each component of the data set content is now identified.
Step 4: Designated communities analysis
SCIDIP-ES Manager analyses the different DC knowledge. SCIDIP-ES manager implements the knowledge modules and dependencies by means of the Gap Identification Service and RepInfo Registry Service. In this way the knowledge of the different designated communities and the information to be accessed by those communities to fill the respective gaps is identified.
Step 5: Rep Info creation and association
Creation and association of additional RepInfo. Using the RepInfo Toolkit and, if needed, the Data Virtualisation Toolkit and the Process Virtualisation toolkit. In this way additional Representation Information relevant for the data (i.e. additional information, description, etc) can be generated and included in the Preserved Data Set Content to fill identified gaps and to enhance description.
Step 6: Notification set-up
Setup of all notifications between all involved actors (using the Orchestration Service). The Finding Aids (for example including GENESI-DEC) are notified about the creation of the archive and its characteristics.
Step 7: Archive implementation
Creation of SIP and then AIP by means of the Packaging Toolkit and the Storage Service. In this way the archive is created starting from the previous steps results.