||Determine render-ability of displayable web objects|
|Detailed description|| To make a digital object render-able depends on standards, agreements, and understandings in interfaces and hardware, and there are strong interdependencies between these conditions. Because of these technical dependencies, the content of the web archive might not be render-able.
Generally, in order to preserver web content, it is required to be aware of new hardware expectations that arise. For example, as WebGL becomes standard, then a 3D accelerator card will probably be required for some site. Or, if multi-touch gets added to the standard, there is a dependency on having having multi-touch hardware, etc.
| Scalability Challenge
|Issue champion||Maureen Pennock (BL)|
| Other interested parties
|| SB: <comment_missing>
KB: Low priority. This approach might be of help to improve tools for identification (scenario 1).
ONB: Would be interesting, but low priority
|Possible Solution approaches||
|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.
|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|