First Proof of Concept

Here below is the list of scenarios which served as a starting point to run the Proof of Concepts. Click on the specific theme to obtain a more detailed description of the scenarios.

To learn more about the experiments conducted in this phase, please take a look at D5.3 Report on first Proof of Concept (.pdf 1,014 kb)

  1. Theme 1 – “Organisational challenges”
    • Scenario 1.1.     Use specialised DP tools on in-house data
    • Scenario 1.2.     Integrating a new tool into existing infrastructure
    • Scenario 1.3.     Select an existing DP solution at an institute with best effort IT support
    • Scenario 1.4.     Preservation from a consortium of collections on the cloud
    • Scenario 1.5.     Preserving a 3D visualisation
    • Scenario 1.6.     Retrieve archived data
  2. Theme 2 – “End user concerns”
    •  Scenario 2.1.     Researcher discovers a historical database
    •  Scenario 2.2.     Research and select a tool serving a specific purpose
    •  Scenario 2.3.     Accessing digitised content from schools
    •  Scenario 2.4.     Gain access to archived websites
  3. Theme 3 – “New services & infrastructure integration”
    •  Scenario 3.1.     Proof of authenticity in distributed archiving
    •  Scenario 3.1a.   Extend 3.1 with repository safeguarding policies
    •  Scenario 3.2.     Defining new services
    •  Scenario 3.3.     Integrating new services into existing infrastructure

The results of this round of experiments clearly demonstrated two key lessons to be learned for the DCH community.

When beginning to collaborate with external service providers (such as academic e-Infrastructure providers), the community of CH researchers will have to learn new skills to be able to make such collaborations a success: not all service providers are domain experts (though it is desirable that they are or will be).

Moreover, whichever tools and services are considered for inclusion in preservation platforms, service providers and integrators must take into account that the typical preservation scientist is not an IT savvy person. Hence tools must be easy to use and easy to install (if this is necessary at all), and the management & configuration of the tools must be easy too.