National Library of France
Main dates of the project
See alsoDigital preservation at the National Library of France [.pdf file – 120 Ko – 10 page(s)]
SeeReference Model for an Open Archival Information System (OAIS) [.pdf file – 706 Ko – 148 page(s)]
Preservation of digital material: the SPAR project
Following the tender for the acquisition of the infrastructure, the National Library of France launched in june 2007 a tender for the realization of the SPAR system, won by the Atos Origin company. The preservation system to realize must be compliant with the OAIS model, offering a high level of modularity to guarantee the permanency of the system, with high response times, and covering all the channels of production of digital material:
Beyond the achievement of the common core of the preservation system, the building of this project within the National Library of France takes place in an iterative manner, channel by channel. The first step covers the whole Digital Library. It is a subset of the overall project and is deployed in priority.
The SPAR system is structured in independant modules which ensures a great permanency of the components (easily change) and allows a distribution according to the required performances.
diagram of the modules of SPAR
The modularity of SPAR is directly based on the OAIS model.
The Ingest module
This module receives the data to ingest (SIP) from the producers according to the ingest policy negociated first with the administration of the Archive. Once the ingest package validated through the different controls, the data ispackaged for archival (AIP) before being given to the storage.
The Storage module
This module ensures the operations connected with the storage of the digital files ("data-objects") that it receives as packages called AIP. It's a abstraction layer of the mechanisms and the systems of storage for the other modules. Mainly, it guarantees the integrity of the data-objects, ensures the adequation of the hierarchy of storage according to the requirements of the producers and the user communities in terms of performance and availability (levels of service).
The Data Management module
This module ensures the functions and services related to the enrichment, the preservation and access of the Descriptive Information (which identifies and describes the collections of the Archive) and to the administrative data needed to manage the Archive.
The Rights Management module
This module aims to manage all the information related to the rights associated with a given data to disseminate. It's fed by rights metadata as well as decision trees, supplied by the SOLON system. It "plays" those decision trees depending on the targeted users in order to add an appropriate license to the outcoming data.
The Access module
This module is in charge of supplying data to the user community to be disseminated as packages called DIP. To achieved this, it offers search functions, reports queries as well as mechanisms to generate and transform the archived data in a displayable form.
The Administration module
This module organizes all the archival procedures and monitors their smooth running. To achieved this, it's in relation with the producers, the users as well as all the others modules which it orchestrates the work; It ensures the right sequencing of all the functions of the Archive and can bring back information.
The Preservation module
This module allows the definition and the monitoring of the formats and standards used by the SPAR system. It's fed by information coming from the business intelligence tool as well as the format registry so that it can monitor the changes of formats or plan the evolutions on storage or policies.
The archival packages (AIP) are made of different kinds of information, classified in the system according to their content and role in the functioning of the Archive.
In SPAR, the main following concepts are distinguished:
Concerning the metadata, the SPAR system uses the most advanced standards:
Over time, it may be necessary to act on archival packages either to make a correction or, more presumably, to migrate to new formats when obsolence occurs.
In SPAR, the archival package follows a lifecycle that depends on the transformations that are applied:
diagram of the lifecycle of an archival package in SPAR
In the end, every archival package has at most three versions:
Tuesday, March 22, 2011