Business activity

From wiki.dpconline.org
Revision as of 15:55, 23 April 2014 by PRWheatley (talk | contribs)
Jump to navigation Jump to search
Securely archiving digital data.

The contents of this section will depend on who the business case is aimed at. It may only be necessary to describe what you want to do at a very high level.

  1. Identify if you need this section in your business case, or exactly what is required. Possible options:
    • some business case templates require considerable detail to the level of a formal Project Plan, possibly including detailed aims and objectives, scoping, constraints, etc
    • some business case templates will require considerably less detail, perhaps just an outline of the proposed activity

SCAPE Project Case Studies

Example text from SCAPE Project case studies with explanatory discussion notes.

Use this to see how a business activity can be articulated within a particular use case.

Jpylyzer business activity

An example Business Activity description.

The existing digitisation workflow for mass digitisation projects at this organisation migrates camera raw images from the digitisation studio to TIFF files for storage as master images in the long term digital respository. The proposed business activity will instead migrate camera raw images to JP2, and then validate the construction of these files using Jpylyzer. The main activities are:

  • Develop appropriate JP2 profile and compression level targets
  • Assess, select and test JP2 migration software
  • Implement and test workflow to migrate and validate JP2s
  • Large scale trial run

Discussion

Discussion notes explaining the approach in developing the Business Activity example, above.

Moving from TIFF to JP2 for the storage of digitised masters will not suit every collection or organisation. Benefits can include reduced storage cost (particularly if lossy compression is utilised) and improved user experience (if images are optimised and delivered to browser by an appropriate system). However, these benefits introduce preservation risks (some which are not mitigated by the use of Jpylyzer in an assessment workflow). Lossy compression lowers the quality of the stored images. The trade off between, cost and risk will be different in different situations. Making an appropriate choice for the collection and organisation in question is essential, and should be guided by collection needs, institutional policy, a careful evaluation of the alternatives, practical testing of software with real data, and a clear appreciation of the risks involved.

See the full case study for more information: A business case for Jpylyzer