Archived copy.
This page was recovered from the Internet Archive snapshot of
/pages/viewpage.action?pageId=13041858 taken on 2021-10-21.
The original wiki at wiki.opf-labs.org is being decommissioned.
IS15 Long-term access and decoding of JP2 images
| Title |
Long-term access and decoding of JP2 images |
| Detailed description | The JP2 format is getting increasingly popular for the storage of digitisation masters. A requirement for preservation is that these images remain accessible. Should the format ever become obsolete at some time in the future, this could lead to quite serious problems in decoding and viewing these files. This is especially true because of the poor support of JP2 by currently available open-source software. The lack of performant open-source JP2 decoding options also limits the possibilities for developing quality assurance tools. For instance, quality assurance tools that are based on image analysis require sufficiently performant software libraries that can decode the contents of JP2 images, including very large ones. Although such libraries exist, these are all released under non-free commercial licenses, and this is currently a stumbling block for developers. |
| Scalability Challenge |
Performance of currently available open-source JP2 libraries is problematic (slow, behaviour on large images) |
| Issue champion | Johan van der Knijff (KB) |
| Other interested parties |
|
| Possible Solution approaches | A possible solution would be to improve the JPEG 2000 decoding of an existing open source JPEG 2000 library (OpenJPEG would be the most obvious candidate for this). Note that for this scenario only the decoding functionality is important; encoding (e.g. going from TIFF to JP2) is completely irrelevant here. One might even question whether having open source encoding options is important at all, since typical budgets of a digitisation programs usually amply cover the costs involved in buying licenses for commercial encoders (which also includes vendor support). |
| 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 | KB Newspapers (where the #$%%@@ did the data sets list in the SCAPE Sharepoint go?!) |
| Solutions | Reference to the appropriate Solution page(s), by hyperlink |
Evaluation
| 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 |