Evolution Layer Sample Clauses
Evolution Layer. The Evolution Layer contains three new workflows: the Situation Change workflow is responsible for monitoring semantic changes in the Active System and to propagate them into the DPS, in order to keep the preserved content understandable; the Setting Change workflow deals with changes in practices, formats and technology in the environment of the preservation (setting); finally, the System Change workflow is responsible for situa- tions, where one of the involved systems changes. The first two workflows are described in more detail below, whereas the last workflow is left to the revised version of the PoF Ref- erence Model which will be reported in deliverable D8.5 [ForgetIT(2016)]. In support of the aforementioned workflows, the Evolution Layer includes additional functionalities: Evolu- tion Monitoring, Context Evolution Management, Content Value Re-assessment and Context-aware Preservation Management. The Situation Change workflow consists of four steps (as depicted in Figure 8): (1) change monitoring, (2) change assessment (assessment of detected changes), (3) change notification (notification of involved components as well as the DPS on rele- vant changes) and (4) change propagation, which performs different types of actions depending on the observed change and the chosen change propagation strategy. For monitoring, assessing the changes and deciding about the consequences, in support to the Situation Change workflow, the functionalities Evolution Monitoring (mainly part of Active System), Context Evolution Management and Content Value Re-assessment have been introduced in the Evolution Layer: The Setting Change workflow consists of four different phases with two different starting points (as depicted in Figure 9): the activity monitoring which (1.1) logs the bi-directional communication between the Active System and DPS and (1.2) receives a change request from a DPS, (2) the change assessment that detects and triggers change requests, (3) the change estimation of suitable change recommendations based on content value, purpose of use, and use statistics, (4) the change recommendation, namely the notifi- cation of recommended actions to DPS, which could be of different types, such as change of content or change of physical and logical content structure.
Evolution Layer. A preservation framework per definition exists in a long-lived environment aimed to sur- vive at least decades. Clearly, most of the involved parts widely ranging from formats, technology and systems to semantics, and relevant real world situations (represented by the application) will not remain stable (i.e. unchanged) over such long period of times. This implies that adequately dealing with changes is a core property that is required from such a framework. The purpose of the Evolution Layer is to adequately deal with the upcoming changes, such that the preserved content remains accessible and understandable. Clearly this means different things for different types of changes. Other types of actions are, for example, required in case a media format gets out of use as compared to the situation that an organization is re-organized. The Evolution Layer, therefore, groups the changes considered in three classes, each handled by its own type of change workflow. Thus, the Evolution Layer contains three new workflows: the Situation Change workflow is responsible for monitoring semantic changes in the Active System and propagating them into the DPS, in order to keep the preserved content understandable; the Setting Change workflow deals with changes in practices, formats and technology in the environment of the preservation (setting); finally, the System Change workflow is responsible for situations, where one of the involved systems changes. In support of the aforementioned workflows, the Evolution Layer includes additional func- tionalities: Content Value Re-assessment, Evolution Monitoring, Context Evolution Management and Context-aware Preservation Management.
3.4.1 Situation Change Active Systems such as the semantic desktop reflect real world processes and situations and thus the content and structures in such systems are subject to change, which we capture under the notion of ”Situation Change”. Since the preserved content co-exist with such changes, this raises the question, if such changes have implications for the pre- served content. Even if the content is not directly affected, changes such as re-structuring in an organization or change in life situation of an individual might have implications for the interpretation and contextualization of preserved content. For this purpose a Situation Change Workflow has been defined. This workflow consists of four steps (as depicted in Figure 8): (1) change monitoring, (2) change assessment (assessment of detect...