Process Layer Sample Clauses

Process Layer. The proposed solution elaborates on the creation and description of information packages to control the media obsolescence vulnerabilities that occur when the representation format becomes obsolete and unable to be rendered, even if the "bit stream" survives over time. Since the information package is composed by the data to be preserved, along with its contextual and representation information, a network of object have to be aggregated to create a meaningful object in whatever e-science context. The Metadata Encoding and Transmission Standard (METS5) is a widespread metadata representation to encode structural metadata in XML. The use of METS provides and extensible way to represent the aggregations required by the scenario described. On the other hand, to address the management of schema representations and their dynamic nature (new or updated schemas to represent the same information), it is critical to manage metadata that describes the information representation. This is not a new requirement in the community, where, for instance, previous work developed the Metacat framework [9], which is able to store, retrieve and transform XML documents managed stored in a relational database. In this work, we use the concept of Metadata Registry (MDR), which was conceived to represent a system that allows the management of multiple schemas (not limited to XML) and the export of information about the schema. It also supports the creation and management of mappings between different schemas. This concept is formalized by the ISO 111796 series of standards. For demonstrating the preservation of data in these scenarios, we developed a Service Oriented Architecture (SOA) solution, as shown in Figure 8. Our proposal comprises services for: harvesting the data to be preserved from a configured data provider, acquiring a description of the schema representation, packaging the data together, and ingesting the data package into the archival system. Such a solution is controlled by a service orchestrator (Service Orchestration component), which orchestrates the following services, controlling their flow and execution: • Data Extractor: Extracts data from the source system, according to the parameters defined by the Assembly Orchestration. To support the dynamic nature of e-science data, it has the option to define the time window for data extraction, full extraction, incremental extraction and the type of items to extract. The recursive use of full data sets uses more space...