Jpylyzer digital preservation risks
An example of digital preservation risks relevant to a specific business case.
A number of a digital preservation risks associated with the JP2 format were identified by early adopters of this technology. Without the application of suitable mitigation there is considerable concern for the longevity of material stored in this format. Software applications that generate JP2's have shown some degree of unreliability. Processing large volumes of data can push generating software (and other workflow processes) to the edge. Results can be invalid or badly formed JP2 files, or possibly even truncated files. The JP2 format presents a vast array of options for the design of a particular JP2 file. JP2's can be optimised for delivery and access in a variety of ways and the type and level of lossy compression is crucial in ensuring appropriate file size and quality levels. These policy choices are defined in the organisational JP2 profile. If JP2's are generated that do not meet this profile, management of and access to the files may become problematic.
This image, courtesy of the British Library provides an example of an arbitrarily truncated JP2, created by a faulty workflow process at the British Library. This example was one of many used to test developments in Jpylyzer.
Discussion notes explaining the approach in developing the Digital Preservation Risks example, above.
- A strong business case results from the use of references to real examples of relevant preservation risks.
- The use of images can be a powerful communication tool.
- There should be a clear link from the Business activity to the risks outlined in this section, in this case the focus is on JP2, the format that Jpylyzer (which forms a central part of the business activity) validates.