Business activity: Difference between revisions

From wiki.dpconline.org
Jump to navigation Jump to search
No edit summary
Line 14: Line 14:
''See the full business case example for more information: [[Jpylyzer business case template]]''
''See the full business case example for more information: [[Jpylyzer business case template]]''


{{:ScapeProjectBusinessActivity}}
{{:ScapePlatformBusinessActivity}}


''See the full business case example for more information: [[SCAPE Platform business case template]]''
''See the full business case example for more information: [[SCAPE Platform business case template]]''

Revision as of 16:09, 2 May 2014

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 business case examples

Use this to see how a business activity can be articulated within a particular organisational context.

This section provides example text from SCAPE Project case studies along with explanatory discussion notes.

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 business case example for more information: Jpylyzer business case template

SCAPE Platform business activity

An example Business Activity description.

Digital collections at this organisation have grown to a sufficient size that assessment of the data for preservation risks has becoming virtually impossible. Execution time of a simple file format identification process is taking several months to complete. The proposed business activity will expand the web archiving department's Hadoop cluster, connect the organisation's digital repository to the cluster and apply the SCAPE Platform to enable all repository data to be characterised and assessed on a more frequent and practical basis.

The main activities are:

  • Purchase new hardware and expand existing cluster
  • Implement SCAPE Platform connector to enable movement of content from the digital repository to the cluster
  • Implement SCAPE Platform tools, specifically Nanite, to enable file format identification, metadata extraction and characterisation of collection data
  • Perform frequent re-assessment of data using the latest tools and file format signatures available

The web archiving department have agreed to allow digital preservation to utilise their existing Hadoop cluster in return for expanding the cluster with some additional hardware.

Discussion

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

The organisation is struggling to assess it's digital collections due to the length of time it takes to assess the growing numbers of files. Without any file format analysis, the potential for unknown preservation risks is significant. The business case therefore suggests leveraging (and expanding) an existing Hadoop cluster for running preservation processes. Web archiving departments have been early adopters of Hadoop technology in libraries and archives, and so this scenario has been used by some SCAPE Project partners.

See the full business case example for more information: SCAPE Platform business case template