Jpylyzer business case template - Revision history

PRWheatley: /* Jpylyzer implementation risks */

2014-05-22T15:21:29Z

Jpylyzer implementation risks

← Older revision		Revision as of 15:21, 22 May 2014
Line 79:		Line 79:
	*Jpylyzer is comprehensive but does not parse/validate every aspect of a JP2		*Jpylyzer is comprehensive but does not parse/validate every aspect of a JP2
	*Jpylyzer has been developed primarily by a single developer, but is now supported by OPF and has seen production use		*Jpylyzer has been developed primarily by a single developer, but is now supported by OPF and has seen production use
	**Jpylyzer is used in a production environment by a number of organisations and embedded in the [http://www.goobi.org/en/ Goobi digitisation workflow tool]		**Jpylyzer is used in a production environment by a number of organisations and embedded in the [http://www.goobi.org/en/ Goobi digitisation workflow tool] and in [https://developers.exlibrisgroup.com/blog/Jpylyzer-Technical-Metadata-Extractor-Plugin Rosetta].
	**Jpylyzer is actively supported at time of writing. See [https://www.ohloh.net/p/jpylyzer Ohloh automated code analysis]		**Jpylyzer is actively supported at time of writing. See [https://www.ohloh.net/p/jpylyzer Ohloh automated code analysis]
	*Application of Jpylyzer does not mitigate all identified [http://wiki.opf-labs.org/display/TR/JP2 JP2 related preservation risks]. Choosing JP2 for storing digitised masters is a trade off between cost, risk and quality		*Application of Jpylyzer does not mitigate all identified [http://wiki.opf-labs.org/display/TR/JP2 JP2 related preservation risks]. Choosing JP2 for storing digitised masters is a trade off between cost, risk and quality

PRWheatley at 19:27, 21 May 2014

2014-05-21T19:27:59Z

← Older revision		Revision as of 19:27, 21 May 2014
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	[[File:Logojpylyzer 399x128.png\|right\|Jpylyzer logo\|link=http://openplanets.github.io/jpylyzer/]]		[[File:Logojpylyzer 399x128.png\|right\|Jpylyzer logo\|link=http://openplanets.github.io/jpylyzer/]]
	~~<blockquote style="background-color: lightblue; border: solid thick lightblue;">~~
	~~</blockquote>~~

	''Use this to help develop a convincing business case for the use of [http://openplanets.github.io/jpylyzer/ Jpylyzer] in your organisation''		''Use this to help develop a convincing business case for the use of [http://openplanets.github.io/jpylyzer/ Jpylyzer] in your organisation''

PRWheatley at 19:27, 21 May 2014

2014-05-21T19:27:45Z

← Older revision		Revision as of 19:27, 21 May 2014
Line 2:		Line 2:
	[[File:Logojpylyzer 399x128.png\|right\|Jpylyzer logo\|link=http://openplanets.github.io/jpylyzer/]]		[[File:Logojpylyzer 399x128.png\|right\|Jpylyzer logo\|link=http://openplanets.github.io/jpylyzer/]]
	<blockquote style="background-color: lightblue; border: solid thick lightblue;">		<blockquote style="background-color: lightblue; border: solid thick lightblue;">
	~~'''This template is a draft and is currently under development by the SCAPE Project!'''~~
	</blockquote>		</blockquote>

PRWheatley: /* Jpylyzer in use */

2014-05-21T17:30:44Z

Jpylyzer in use

← Older revision		Revision as of 17:30, 21 May 2014
Line 91:		Line 91:
	The [http://wellcomelibrary.org/ Wellcome Library] was an early adopter of Jpylyzer. Dave Thompson, Digital Curator, describes how The Wellcome uses Jpylyzer and what value they get from it.		The [http://wellcomelibrary.org/ Wellcome Library] was an early adopter of Jpylyzer. Dave Thompson, Digital Curator, describes how The Wellcome uses Jpylyzer and what value they get from it.
	<blockquote>		<blockquote>
	"We use it in two ways; firstly to automatically validate JP2 images created for us by external agencies and secondly to validate JP2 images we have created ourselves. Building the ~~jpylyzer~~ into our workflow as an automated validation tool allows us to validate the technical properties of every single JP2 image that we process. A level of validation that we’d never be able to achieve if it were performed by a human.		"We use it in two ways; firstly to automatically validate JP2 images created for us by external agencies and secondly to validate JP2 images we have created ourselves. Building the Jpylyzer into our workflow as an automated validation tool allows us to validate the technical properties of every single JP2 image that we process. A level of validation that we’d never be able to achieve if it were performed by a human.
	</blockquote>		</blockquote>
	<blockquote>		<blockquote>

PRWheatley: /* Jpylyzer implementation risks */

2014-05-21T17:27:24Z

Jpylyzer implementation risks

← Older revision		Revision as of 17:27, 21 May 2014
Line 83:		Line 83:
	*Jpylyzer is comprehensive but does not parse/validate every aspect of a JP2		*Jpylyzer is comprehensive but does not parse/validate every aspect of a JP2
	*Jpylyzer has been developed primarily by a single developer, but is now supported by OPF and has seen production use		*Jpylyzer has been developed primarily by a single developer, but is now supported by OPF and has seen production use
	**Jpylyzer is used in a production environment by a number of organisations and embedded in [http://www.goobi.org/en/ Goobi digitisation workflow tool]		**Jpylyzer is used in a production environment by a number of organisations and embedded in the [http://www.goobi.org/en/ Goobi digitisation workflow tool]
	**Jpylyzer is actively supported at time of writing. See [https://www.ohloh.net/p/jpylyzer Ohloh automated code analysis]		**Jpylyzer is actively supported at time of writing. See [https://www.ohloh.net/p/jpylyzer Ohloh automated code analysis]
	*Application of Jpylyzer does not mitigate all identified [http://wiki.opf-labs.org/display/TR/JP2 JP2 related preservation risks]. Choosing JP2 for storing digitised masters is a trade off between cost, risk and quality		*Application of Jpylyzer does not mitigate all identified [http://wiki.opf-labs.org/display/TR/JP2 JP2 related preservation risks]. Choosing JP2 for storing digitised masters is a trade off between cost, risk and quality

PRWheatley: /* Jpylyzer digital preservation risks */

2014-05-21T17:24:49Z

Jpylyzer digital preservation risks

← Older revision		Revision as of 17:24, 21 May 2014
Line 74:		Line 74:

	''For more on identifying and understanding the digital preservation risks that your business activity is targeting see the DPBCT sections on [[Digital preservation risks]], [[Understand your collection]] and [[Why are we writing a business case?]].''		''For more on identifying and understanding the digital preservation risks that your business activity is targeting see the DPBCT sections on [[Digital preservation risks]], [[Understand your collection]] and [[Why are we writing a business case?]].''

	''For more on developing preservation policies see the [http://wiki.opf-labs.org/display/SP/Catalogue+of+Preservation+Policy+Elements SCAPE Project Catalogue of Preservation Policy Elements].''		''For more on developing preservation policies see the [http://wiki.opf-labs.org/display/SP/Catalogue+of+Preservation+Policy+Elements SCAPE Project Catalogue of Preservation Policy Elements].''

PRWheatley: /* Jpylyzer digital preservation risks */

2014-05-21T17:24:21Z

Jpylyzer digital preservation risks

← Older revision		Revision as of 17:24, 21 May 2014
Line 74:		Line 74:

	''For more on identifying and understanding the digital preservation risks that your business activity is targeting see the DPBCT sections on [[Digital preservation risks]], [[Understand your collection]] and [[Why are we writing a business case?]].''		''For more on identifying and understanding the digital preservation risks that your business activity is targeting see the DPBCT sections on [[Digital preservation risks]], [[Understand your collection]] and [[Why are we writing a business case?]].''
			''For more on developing preservation policies see the [http://wiki.opf-labs.org/display/SP/Catalogue+of+Preservation+Policy+Elements SCAPE Project Catalogue of Preservation Policy Elements].''

	==Jpylyzer implementation risks==		==Jpylyzer implementation risks==

PRWheatley: /* Jpylyzer benefit summary */

2014-05-21T17:19:57Z

Jpylyzer benefit summary

← Older revision		Revision as of 17:19, 21 May 2014
Line 29:		Line 29:
	'''Indirect benefits:'''		'''Indirect benefits:'''
	*Enables application of JP2 format (and powerful JPEG2000 compression) for storing digitised masters (by mitigating preservation risks as described above) and therefore:		*Enables application of JP2 format (and powerful JPEG2000 compression) for storing digitised masters (by mitigating preservation risks as described above) and therefore:
	**Significantly reduces storage costs for digitised collections or frees up resource for additional digitisation		**Significantly reduces storage costs for digitised collections or frees up resource for additional digitisation and/or storage
	**Enhances remote access and the optimised delivery of images, providing a better experience for the user		**Enhances remote access and the optimised delivery of images, providing a better experience for the user

PRWheatley: /* Jpylyzer benefit summary */

2014-05-21T17:18:53Z

Jpylyzer benefit summary

← Older revision		Revision as of 17:18, 21 May 2014
Line 26:		Line 26:
	*Ensures created JP2 files comply with an organisation's (policy driven) [http://wiki.opf-labs.org/display/JP2/Example+JP2+profiles JP2 profile]		*Ensures created JP2 files comply with an organisation's (policy driven) [http://wiki.opf-labs.org/display/JP2/Example+JP2+profiles JP2 profile]
	*Reduces data management and processing costs by catching bad files early		*Reduces data management and processing costs by catching bad files early
	*Enables efficient quality assurance of JP2 files created by 3rd party ~~digitisers~~		*Enables efficient quality assurance of JP2 files created by 3rd party digitising organisations
	'''Indirect benefits:'''		'''Indirect benefits:'''
	*Enables application of JP2 format (and powerful JPEG2000 compression) for storing digitised masters (by mitigating preservation risks as described above) and therefore:		*Enables application of JP2 format (and powerful JPEG2000 compression) for storing digitised masters (by mitigating preservation risks as described above) and therefore:

PRWheatley: /* About Jpylyzer */

2014-05-21T17:15:34Z

About Jpylyzer

← Older revision		Revision as of 17:15, 21 May 2014
Line 14:		Line 14:

	====About Jpylyzer====		====About Jpylyzer====
	Jpylyzer is designed to help identify problematic JP2 files that might be broken or invalid in some way ~~and~~ identify JP2 files that do not conform to a particular technical profile. As such it provides useful checking and analysis of acquired JP2 files as well as playing a role in ensuring the quality and consistency of JP2 files in a digitisation workflow.		Jpylyzer is a software tool designed to help identify problematic JP2 files that might be broken or invalid in some way or identify JP2 files that do not conform to a particular technical profile. As such it provides useful checking and analysis of acquired JP2 files as well as playing a role in ensuring the quality and consistency of JP2 files in a digitisation workflow.

	==Jpylyzer benefits==		==Jpylyzer benefits==