View Source

h2. Preservation Scenario

* Large Scale Migration of TIFF images from digitised books and periodicals.
* Digitisation performed 90s - 2010, originals in poor state.
* Migrated to JP2Ks, during 2012 to cut down storage volume.

h2. Preservation Issues

Ensuring that the migrated image is identical to the original digitised image. This is done by:
* Pixel by pixel comparison.
* Jpylyzer to check that image is valid JP2K and check key properties.

h2. SCAPE solution (unique selling point)

The only tool capable of validating JP2K images, hence it has been incorporated into the Debian repositories

h2. Success Story Champion

Internal - KB, BL
External - Wellcome trust

Who could use it? anyone who is using a debian based distro (apt-get install jpylyzer)


Institution wants to save on long term storage costs, thus migrates TIFF to JP2000. Jpylyzer enables the validation of derived JP2000s against the specification. Thereby JP2000 becomes a much more attractive alternative to TIFF. Jpylyzer can also be used to validate JP2000 images delivered by a service provider against a technical profile,

"Jpylyzer - JP2000 validation made easy"

Why validate? And how?

What did SCAPE contribute?

Examples of use (Intranda/Goobi, Wellcome Library)

Given some JP2000 files (from migration, from digitisation provider, other) validating these against the specification will reveal damaged images and ensure the quality of the produced files (validty is reassuring everything ẃas done correctly)

"Jpylyzer - better than random sampling" (Maureen)