JISC

JISC set up the Common Repository Interfaces Working Group (CRIG) to identify and address priorities for enhancing interoperability between the emerging base of UK repositories. The WoCRIG project is funded by JISC to provide expert support on technical and other matters to the CRIG, and to the JISC repositories programmes in general, with the overall aim of ensuring the successful delivery of the CRIG Workplan 2007-8.

Aims and objectives

WoCRIG is the CRIG support project, and its overall aim is to ensure successful delivery of the CRIG Workplan.

Specifically, the project will:

• facilitate an unconference to identify interfaces implied by the CRIG scenarios, and to determine how much they are supported by existing specifications.
• create SUMs based on the functions and interfaces.
• evaluate existing specifications against the scenarios and interfaces.
• facilitate interoperability events to address the issues around the interfaces and specifications.
• facilitate follow-up interoperability events with software developers, particularly from JISC projects.
• contribute to a review of CRIG-related activities.

Project methodology

The project will follow two parallel, interacting strands, each using the CRIG scenarios as a starting point: one specification-centric, top-down; one implementation-centric, bottom-up. The first will define an exemplar set of SUMs based on actual practice and software developed to meet the requirements of the scenario. The second will bring together key stakeholders, including CRIG but also (crucially) software developers, in events (unconference, ‘barcamps’/’codebashes’/’code-a-thons’) that will facilitate and draw on a community work ethos. The streams will impact upon one other, enabling more robust SUMs to be created, and ensuring that development is both innovative and adequately documented.

Anticipated outputs and outcomes

Management documentation:

• Project plan, progress and final reports.
• Ongoing dissemination of developments via blog and DigiRepWiki.

Unconference outputs:

• Podcasted interviews with CRIG members (prior to unconference).
• Unconference briefing.
• Reports of discussions and conclusions at unconference (full and summary versions).

Barcamp/codebash outputs:

• Event briefings.
• Documentation of activities, discussions and conclusions at events (full and summary versions).
• Code bashed at events.

e-Framework outputs:

• SUMs, initially at genre level, later at expression level
• Contributions to international e-framework wiki and website
• Encouragement and facilitation of successful JISC demonstrator projects.
• Repository interface specifications.

Technology / Standards used

In keeping with the highly agile approach the project will take for any development, it would be inappropriate to limit developers at this point to any specific standards. That said, the project is fully aware of the importance of standards, and will keep in mind the standards in the JISC Standards catalogue, as well as other standards, throughout the project. In particular, open source technologies will be used as far as possible.