JpylyzerRisks - Revision history

PRWheatley: /* Jpylyzer digital preservation risks */

2014-05-07T15:45:13Z

Jpylyzer digital preservation risks

← Older revision		Revision as of 15:45, 7 May 2014
Line 1:		Line 1:
	==Jpylyzer digital preservation risks==		==Jpylyzer digital preservation risks==
			''An example of digital preservation risks relevant to a specific business case.''

	A number of a [http://wiki.opf-labs.org/display/TR/JP2 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.		A number of a [http://wiki.opf-labs.org/display/TR/JP2 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 [http://wiki.opf-labs.org/display/JP2/Example+JP2+profiles organisational JP2 profile]. If JP2's are generated that do not meet this profile, management of and access to the files may become problematic.		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 [http://wiki.opf-labs.org/display/JP2/Example+JP2+profiles organisational JP2 profile]. If JP2's are generated that do not meet this profile, management of and access to the files may become problematic.
Line 5:		Line 7:
	[http://wiki.opf-labs.org/display/REQ/Truncated+JPEG2000 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.		[http://wiki.opf-labs.org/display/REQ/Truncated+JPEG2000 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====		====Discussion====
			''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.		*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.		*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.		*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.

PRWheatley: /* Explanation */

2014-04-23T16:21:31Z

Explanation

← Older revision		Revision as of 16:21, 23 April 2014
Line 4:		Line 4:

	[http://wiki.opf-labs.org/display/REQ/Truncated+JPEG2000 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.		[http://wiki.opf-labs.org/display/REQ/Truncated+JPEG2000 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.
	====~~Explanation~~====		====Discussion====
	*A strong business case results from the use of references to real examples of relevant preservation risks.		*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.		*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.		*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.

PRWheatley: /* Explanation */

2014-04-23T14:57:36Z

Explanation

← Older revision		Revision as of 14:57, 23 April 2014
Line 7:		Line 7:
	*A strong business case results from the use of references to real examples of relevant preservation risks.		*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.		*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.		*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.

PRWheatley: /* Explanation */

2014-04-23T14:56:36Z

Explanation

← Older revision		Revision as of 14:56, 23 April 2014
Line 5:		Line 5:
	[http://wiki.opf-labs.org/display/REQ/Truncated+JPEG2000 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.		[http://wiki.opf-labs.org/display/REQ/Truncated+JPEG2000 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.
	====Explanation====		====Explanation====
	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.		*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.

PRWheatley at 14:28, 23 April 2014

2014-04-23T14:28:36Z

← Older revision		Revision as of 14:28, 23 April 2014
Line 1:		Line 1:
	==~~Digital~~ preservation risks==		==Jpylyzer digital preservation risks==
	A number of a [http://wiki.opf-labs.org/display/TR/JP2 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.		A number of a [http://wiki.opf-labs.org/display/TR/JP2 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 [http://wiki.opf-labs.org/display/JP2/Example+JP2+profiles organisational JP2 profile]. If JP2's are generated that do not meet this profile, management of and access to the files may become problematic.		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 [http://wiki.opf-labs.org/display/JP2/Example+JP2+profiles organisational JP2 profile]. If JP2's are generated that do not meet this profile, management of and access to the files may become problematic.

PRWheatley: Created page with "==Digital preservation risks== A number of a [http://wiki.opf-labs.org/display/TR/JP2 digital preservation risks associated with the JP2 format] were identified by early adopt..."

2014-04-23T14:27:43Z

Created page with "==Digital preservation risks== A number of a [http://wiki.opf-labs.org/display/TR/JP2 digital preservation risks associated with the JP2 format] were identified by early adopt..."

New page

==Digital preservation risks==
A number of a [http://wiki.opf-labs.org/display/TR/JP2 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 [http://wiki.opf-labs.org/display/JP2/Example+JP2+profiles organisational JP2 profile]. If JP2's are generated that do not meet this profile, management of and access to the files may become problematic.

[http://wiki.opf-labs.org/display/REQ/Truncated+JPEG2000 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.
====Explanation====
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.