|Overview||For users||For resource providers||Infrastructure status||Site-specific configuration||Architecture|
|Federated Cloud Communities menu:||Home •||Production use cases •||Under development use cases •||Closed use cases •||High level tools use cases|
- Status: Test & Integration
- Start Date: 08/07/2014
- End Date: -
- EGI.eu contact: Diego Scardaci / email@example.com
- External contact: Luigi Briguglio / firstname.lastname@example.org, Pietro Fragnito / email@example.com
SCIence Data Infrastructure for Preservation with focus on Earth Science (SCIDIP-ES) is a European 7th Framework project. It brings together the state of the art in preservation technologies, represented by Earth Science repositories, and researchers for digital data preservation techniques.
SCIDIP-ES HAPPI supports the archive manager and curator to capture and manage part of the Preservation Descriptive Information (PDI).
This part of PDI, which includes provenance, reference, evidences of changes and integrity, is called Evidence History. Evidence History is the set of information for all the transformations and events a digital object has undergone since its creation. Each single transformation and event is documented by the so-called Evidence Record: in this perspective, an Evidence History is composed by a set of Evidence Records.
The structure of an evidence record is mainly characterised by three main sections:
- Header – includes reference to the content information which is focus of digital preservation, as well as external references used in the description of the current evidence record;
- Entities – defines entities involved in the event/transformation: i.e. the result of event/transformation (called representation), the transformation that generated the result and who controlled the transformation (called agent);
- Description – describes the event/transformation by providing details which could be used later in order to assess authenticity: e.g. timestamp, fixity, annotations.
Deploy the SCIDIP-ES HAPPI toolkit in the EGI Federated Cloud.
- 1 VM
- 2 CPU cores
- 4 GB of RAM