Workplan

WORKPACKAGE 1: Determine tool requirements and investigate possible components

Objective

To understand what metadata we need for preservation, what existing tools can give us this metadata, and how we map data that can be extracted to the metadata standards needed for preserving different kinds of object.

Activities

  1. Articulate curator use-cases to develop workflows for tool. This is intended to tell us what curators need to be able to do, and so what metadata they need at ingest.
  2. Investigation of appropriate technical metadata standards for object types (e.g. MIX for images).
  3. Survey existing tools to evaluate their suitability for inclusion, including mapping to Dublin Core, PREMIS and object-specific technical metadata standards such as MIX and TechMD.
  4. Scope object-types and define object-specific content models.

Outputs

  • Published ingest use cases to project website
  • Knowledge on which content-models typology and schema (task 1.4) will be based.
  • Report on tools survey
  • Content-models typology and schema based on work undertaken in 1.1-1.3.

October 2006 - August 2008

WORKPACKAGE 2: Design and publish model and specification for CAIRO tool

Objective

Develop model and specification for software based on outputs of WP1 and seek feedback from focus groups. Outputs of this work package will be of interest to the community, and not solely a basis for developing the ingest service.

Activities

  1. Agree development timetable based on outputs of WPs 1&2 and discussions between curators and developers
  2. Develop and submit modules for testing according to development timetable

Outputs

  • Model for tool
  • Specification for developers

December 2006 - August 2008

WORKPACKAGE 3: Development phase based on results of work package two

Development will take place on a modular basis; once the specification has been created a more detailed plan of work for the development phase will need to be drafted. It is the intended that the development will adopt a release early release often philosophy, and meet weekly with the project's curators so that feedback can be rapidly incorporated in incremental development.

Objective

Produce software according to specification developed in WP2.

Outputs

  • Development timetable
  • Modular ingest tool with installer

April 2007 - August 2008

WORKPACKAGE 4: Testing on archival materials

The project will follow an iterative development cycle, releasing code often and using the feedback to inform development. As well as releasing code for feedback via the SourceForge and Fedora communities, the project will conduct regular testing within the core project team and with its target audience via a focus group of curators. To provide a good spread of use cases, testing will be undertaken using new and legacy collections and with standardised dummy collections; the earlier phase of this work package will therefore include sourcing this material.

Objective

Ensure product is fit for purpose and meets end-user needs.

Activities

  1. Developers report weekly changes and curators undertake testing and provide rapid feedback
  2. At significant releases, testing and feedback is undertaken with external focus groups
  3. Curators create dummy collections for testing
  4. Curators survey existing collections for archival materials to use in testing.

Outputs

  1. Results of tests
  2. Refinement of tool according to user needs

March 2007 - August 2008

WORKPACKAGE 5: Dissemination

Objective

To share the project's results with appropriate audiences

Activities

  1. Dissemination via articles, meetings, papers, posters, presentations, etc.
  2. Create project web site and register project with SourceForge
  3. Release code instalments via SourceForge under OSI-approved open-source licence
  4. Publish online curator manual
  5. Publish technical documentation for tool

Outputs

  1. News and articles about the project presented to relevant audiences
  2. User documentation (administrator and normal user)
  3. Technical documentation
  4. Project and SourceForge web sites

October 2006 - August 2008

 

Contributing institutions

The Joint Information Systems Committee University of Oxford The University of Manchester Wellcome Library
Last updated: 28 April 2008