Setting Change Sample Clauses

Setting Change. ‌ Although the DPS should have its own support for typical OAIS functionalities, such as Preservation Planning and Administration, the many-to-many relationship in the PoF Ref- erence Model and the long-term perspective of those functions mean that at least parts of those functionalities need to be shared and communicated over several systems. The OAIS Preservation Planning function could for example benefit from Technology Watch residing in the middleware, thereby gathering and aggregating information about, e.g., usage of file formats in all systems connected to the same middleware. Another example would be when Preservation Planning in a DPS declare a file format as obsolete, this in- formation could then be shared with the PoF Middleware which propagates this to Active Systems and other DPS. The PoF Middleware acts as a man-in-the-middle (broker) between Active Systems and DPS and therefore has a suitable position for capturing these bi-directional interactions. Based on such evidences, it provides additional possibilities to summarize and analyse the usage and, e.g., storage quotas over several systems, thereby giving an overview of the holdings for a particular customer. Since a customer might have several Active Systems, as well as preserved content in several DPS, such an overview is beneficial in locating objects that need preservation actions. This process is part of what is labelled ”Setting Change”. The Setting Change workflow consists of four different phases with two different starting points (as depicted in Figure 9), involving the Context-aware Preservation Management (CaPM) entity (described below): (1) activity monitoring, which logs the bi-directional communication between the Active System and DPS including process activities, systems in action, and digital objects passing through, (2) change assessment that detects and propagates change in usage, (3) change estimation suggests suitable change recom- mendations based on rules defined in Preservation Contract including, e.g., Preservation Value, and use statistics, (4) change recommendation, which propagates recommended actions to DPS, which could be of different types, such as transformation of content or change of physical and logical content structure.