View Source

{info}These Scenarios describe specific preservation issues that will drive the development and evaluation of a number of key outputs from the [SCAPE Project|]. During the first year of SCAPE the focus of these pages has primarily been on development of Preservation Components (Characterisation, Action and Quality Assurance). Over time, they will be expanded to describe developments in Preservation Watch and the underlying infrastructure provided by the SCAPE Platform. We welcome feedback on these pages from both SCAPE participants and external developers and practitioners. If you would like to contribute, please [sign up here|KB:Joining the OPF Labs site], and then comment on individual pages using the wiki.{info}

* Please note that these pages are a work in progress, and will reflect ongoing developments throughout the life of the Project.
* As the goal of the Scenarios is to capture how SCAPE outputs are evaluated, the focus is on specific issues rather than on the more general problems SCAPE will solve.
* Some information and data (such as particular Datasets) are not currently shareable outside of the Project.

The pages below form a network of *Datasets*, preservation *Issues* with those Datasets, and *Solutions* to those Issues. Triples composed of a Dataset, Issue and a Solution are called *Scenarios*. These Scenarios provide a convenient view onto a set of SCAPE activities that will be spread across a number of workpackages and sub projects (each Scenario page merely includes by reference the relevant details from the Dataset, Issue and Solution wiki pages). This structure was first developed as part of the [AQuA Project|AQuA:Home] hackathons, which captured preservation issues and solutions on similar wiki pages [here (AQuA)|AQuA:Collections, Issues, Contexts and Solutions] and [here (in a subsequent DPC/OPF hackathon)|REQ:Datasets, Issues, Contexts and Solutions]. These results may be of interest, and indeed some have already been incorporated or linked to from these SCAPE pages.

The aims of the SCAPE Scenarios are to:
# Provide a record of SCAPE Project developments and identify what will be evaluated in SCAPE Testbeds
# Ensure effective liaison and collaboration between the various WPs and SPs within the project, by illustrating how each piece of work fits together
## Issue Owners can see what solutions are being developed for them and ensure developers understand their requirements
## Solution Owners can see what the challenge is they are being asked to solve (with associated requirements) and know who they can contact for more information
## Both Issue and Solution Owners can agree on how Solutions will be evaluated in the Testbeds
# Support WP and SP monitoring and management, by describing key project results in one place
# Support the gathering of feedback from outside of the project, publicise project results and engage with interested users/practitioners

{info}To add a new Dataset, Issue, Solution, or Scenario check out the following instructions: [SP:How to add a new Dataset, Issue, Solution or Scenario]. Ensure you are aware of the: [SP:Responsibilities of the roles described on these pages].{info}

_WARNING: There is a Confluence Wiki bug that sometimes causes problems with bulleted lists inside tables. If you're having trouble, don't use a list inside a table\!_

h4. [Datasets]*:*\\


h4. [Scenarios|Scenarios]*:*\\


h4. [Issues|Issues]*:*\\


h4. [Solutions|Solutions]*:*\\


h2. Wiki details