Supporting Information Exchanges Clause Samples

Supporting Information Exchanges. ‌ A core functionality, which needs to be enabled for synergetic preservation is information exchange between the Active System and the DPS. Information to be exchanged includes the content to be preserved as well as metadata and context information describing this content. Furthermore, it has to be possible to bring content from the DPS back into the Active System (see Re-activation in Section 3.2). Thus, bi-directional information exchange has to be enabled. Bi-directional exchange can be enabled for example by a repository used by both sides for making content available to the respective other system (plus possibly a notification channel). This approach is investigated in WP5 deliverables (see for example deliverables D5.1 [Nilsson et al., 2013] and D5.2 [Nilsson et al., 2014]). We mention here two different approaches adopted in ForgetIT to exchange information with the Preserve-or-Forget (PoF) Middleware in order to show that different strategies are possible with the actual implementation. As a first example, we consider TYPO3 CMS, the Active System chosen in WP10 to implement the organization preservation use case. WP10 makes use of a standard-based repository leveraging the content ex- change standard CMIS [OASIS, 2013], which enables the exchange between TYPO3 CMS and the PoF Middleware using a CMIS repository as intermediate (see also de- liverable D10.3 [Dobberkau et al., 2015]). Besides these asynchronous channels, more synchronized forms of information exchange are also possible, such as direct service calls. This is done in the second approach, where we consider as a second example the PIMO Server, the Active System chosen in WP9 to implement the personal preser- vation use case. WP9 uses direct service calls between PoF Middleware and the Active System Semantic Desktop. There, CMIS is used as an exchange format for content ob- jects which enables the PoF Middleware to retrieve content directly from the PIMO Server (see also deliverable D9.4 [▇▇▇▇ et al., 2015]). Nevertheless, both approaches use the PoF interfaces for communicating with the PoF Middleware such as registering content, preservation value updates, restore requests, etc.

Supporting Information Exchanges. ‌ A core functionality, which needs to be enabled for synergetic preservation is information exchange between the Active System and the DPS. Information to be exchanged includes the content to be preserved as well as metadata and context information describing this content. Furthermore, it has to be possible to bring content from the DPS back into the Active System (see Re-activation in Section 3.1.1). Thus, bi-directional information ex- change has to be enabled. This can be enabled for example by a repository used by both sides for making content available to the respective other system (plus possibly a notification channel). This approach is investigated in WP5 deliverables (see for example deliverable D5.1 [ForgetIT, 2013b] and D5.2 [ForgetIT, 2014b]). The approach adopted in ForgetIT makes use of a standard-based repository leveraging the content exchange standard CMIS [OASIS, 2013], which enables the interaction with different Active Sys- tems. Besides these asynchronous channels, more synchronized forms of information exchange are also possible, such as direct service call.