|| IS48 Validate archival files against an institutional content policy regarding formats
|Detailed description||A detailed description of the Issue. The Issue MUST focus on the busines or preservation driven challenge, and should not assume or describe a particular solution.|
| Scalability Challenge
|| What requirements are placed on the solution in terms of the SCAPE scales of scalability: content size, volume of content, complexity of content
|Issue champion||Who owns the issue? Identify the owner with a link to their contact page on the SCAPE Sharepoint site, as well as identifying their institution in brackets. Eg: Schlarb Sven (ONB). Also note what the role of the Issue Champion is within their organisation.|
| Other interested parties
||Any other parties who are also interested in applying Issue Solutions to their Datasets. Identify the party with a link to their contact page on the SCAPE Sharepoint site, as well as identifying their institution in brackets. Eg: Schlarb Sven (ONB)|
|Possible Solution approaches|| Brief brainstorm of possible approaches to solving the Issue. Each approach should be described in a single sentence as part of a bulleted list. Note that actual Solutions will be owned by the Solution Provider who should be a different person from the Issue Champion. Reaching a satisfactory conclusion for the Issue should be considered a team effort between these parties.
|Context|| Details of the institutional context to the Issue. (May be expanded at a later date)
|Lessons Learned|| Notes on Lessons Learned from tackling this Issue that might be useful to inform the development of Future Additional Best Practices, Task 8 (SCAPE TU.WP.1 Dissemination and Promotion of Best Practices)
|Training Needs|| Is there a need for providing training for the Solution(s) associated with this Issue? Notes added here will provide guidance to the SCAPE TU.WP.3 Sustainability WP.
|Datasets||mpeg-2 transport stream with Danish TV broadcasts|
|Solutions|| SO35 Use schematron as the content profile language to validate files by evaluating their characterisation information
|Objectives||Which scape objectives does this issues and a future solution relate to? e.g. scaleability, rubustness, reliability, coverage, preciseness, automation|
|Success criteria||Describe the success criteria for solving this issue - what are you able to do? - what does the world look like?|
|Automatic measures|| What automated measures would you like the solution to give to evaluate the solution for this specific issue? which measures are important?
If possible specify very specific measures and your goal - e.g.
* process 50 documents per second
* handle 80Gb files without crashing
* identify 99.5% of the content correctly
|Manual assessment|| Apart from automated measures that you would like to get do you foresee any necessary manual assessment to evaluate the solution of this issue?
If possible specify measures and your goal - e.g.
* Solution installable with basic linux system administration skills
* User interface understandable by non developer curators
|Actual evaluations||links to acutual evaluations of this Issue/Scenario|