Output – SAFIR: Requirements Specification – Scenarios

Title: Digital Library Project (SAFIR): Requirements Specification

Pages: 14-15
Date Released: 07 March 2008

URI for Output: https://vle.york.ac.uk/bbcswebdav/xid-89716_3

Summary of contents:
Five scenarios are presented for the use of a mulitmedia repository.
Each is focused around a key type of use; they are:

  • finding image materials
  • sharing resources, advice and guidance
  • streaming
  • archival collections
  • video materials


The five scenarios are relevant to the growing knowledge/ innovation  base connected to the e-Framework.

Output – CAIRO: Cairo Use Cases

Title: Cairo use cases: a survey of user scenarios applicable to the Cairo ingest tool

Pages: all
Date Released: 21 May 2007

Summary of contents:
The CAIRO “project will develop a tool for ingesting complex collections of born-digital materials, with basic descriptive, preservation and relationship metadata, into a preservation repository.” The tool is designed to aggregate and interface with other tools and so reduce the computing skills overhead on archivists awnting to create AIPs. p3
“This document outlines a set of [55] use cases describing the different interactions users of the Cairo tool have with that tool. The use cases also describe the behaviour of the tool in response to those user interactions.”p5

URI for Output: http://cairo.paradigm.ac.uk/projectdocs/cairo_project_use_cases_pv1.pdf

This document provides a selection of use cases that have shaped the developed of an ingest tool. As such they inform not only this tools but software/service development more generally and institutional preservation planning.

Output – CLAReT – Personas


Pages: all

Date Released: not known

URI for Output: http://www.claret.ecs.soton.ac.uk/presentations/CLAReT%20PERSONAS.ppt

Summary of contents:

The output contains persona and corresponding scenarios for six end users of a system managing digital learning materials in the context of language learning. The personae were used in the context of roleplay in workshops to develop and test the concept/ domain map of language learning in HE.

The personae provide a useful reference for system desginers in this domain.

Project – ROAD

Project Name: Robot-generated Open Access Data

Programme Name: Repositories and Preservation Programme

Strand: Tools and Innovation

JISC Project URI:http://www.jisc.ac.uk/whatwedo/programmes/reppres/tools/road

Project URI: http://www.inf.aber.ac.uk/projects/road/

Start Date:01 June 2007

End Date: 31 June 2009

Governance: Repositories and preservation advisory group, Integrated Information Environment Committee (JIIE)

Contact Name and Role: Stuart Lewis, Project Manager

Brief project description:

The aim of the two year JISC funded project (start date June 2007) is to investigate the use of current open-source digital repository software to enable the automatic curation of robot-generated experimental data and metadata.

The intention is to demonstrate the feasibility of using current open-source digital repository software for management of data acquired directly from automatic integrated laboratory equipment, specifically the Robot Scientist created at UWA.

It is expected that the project will also contribute to research on the sharing of experimental data as well as providing a case study for similar scientific installations in other institutions and for other scientific domains. The vision for data repositories in Digital Repositories Roadmap: looking forward has an information environment in which raw research data is made available on an open access basis. This vision includes the idea of direct linking between laboratory equipment and a departmental or institutional repository. The link with the Robot Scientist constitutes a sophisticated demonstration of this vision.

Development work and testing will focus on three open source repository systems: DSpace, Fedora and EPrints.

Name of Trawler: Mahendra Mahey

Output:  No outputs are available at present. The plan suggests the following:
• A report detailing the ability of different repository platforms to ingest and store the requisite data in a suitable fashion
• Quarterly project reports giving updates on the progress of the project.
• Final report detailing the investigations undertaken, the software written, and the evaluation performed.
Software (specific to chosen repository platform)
• A suitable data repository to hold the data from the Robot Scientist
• Software to perform the ingest of large amounts of data into the chosen repository platform
• Suitable interfaces to allow people and machines to easily download the data help within the repository

Output – SOURCE – User Case Studies of Bulk-Migration in HE

Title: User Case Studies of Bulk-Migration in HE

Date Released: 25th May 2007

URI for Output: http://www.bbk.ac.uk/lib/life/source/UserCases/player.html

Summary of contents: Slide and audio description of the SOURCE project use cases by David Flanders. Twelve bulk transfer use cases are presented in addition to architecture, object model and GUI overviews. Most use cases describe either full or partial bulk transfer of objects and/or metdata between repositories.  The scenarios are based on the transfer of learning objects but are applicable more widely.

Additonal information: Six R&D case studies and six deposit API use studies are described as part of the same presentation.

Comments: Although the slide and audio description are useful and detailed, the output in the form of a Adobe Flash movie limits it’s usefulness and re-usability. No other form of the use cases is provided via the project website. The notes section of the presentation provides textual description of the use cases but this can’t be copied.

Output – Lirolem – SUM: service arrangement

Title: LIROLEM – Service Usage Model

Section: Structure & Arrangement

Page: 6

Summary of contents:

(section reproduced)

Services: Security, user management, submission, object store, metadata management, search, transcoding, rights management, dissemination and reporting.

Data Sources: User profile information; data object & object representation information (SIP); provenance, context, reference and fixity information (AIP); METS, IMS Packages, IEEE LOM, PBCore, Dublin Core/OAI-PMH (DIP). For SIP, AIP & DIP, see OAIS Reference Model.


  • The Security service authenticates and authorises the user to use the upload, metadata management, search, transcode and download services.
  • The User Management service creates, modifies and removes users and their permissions.
  • The Submission service permits the ingest of data objects and and object representation information (SIP) to the repository.
  • The Object Store service tracks data objects being submitted and disseminated from the repository.
  • The Metadata Management service, creates, modifies, verifies and removes all content metadata (descriptive, administrative and technical) in the repository, as well as private user metadata (notes, bookmarks) and shared user metadata (tags, comments). Metadata is linked to objects (items, sets, resources), Licences and users. Provenance, context, reference and fixity information (AIP) is comnpleted for the data object and validated.
  • The Search service allows a user to search data managed by the metadata management service, according to permissions granted by the user management service. The search service returns and displays search results drawing from the object store service and metadata management service.
  • The Transcoding service converts data objects from the source format to another format. This occurs at submission time to create preview thumbnails of images and clips of video and audio and also as requested by the user prior to dissemination. Transcoding is performed according to rights applied to the data object.
  • The Rights Management service requires the application of terms and conditions (a ‘Licence’) to the data object.
  • The Dissemination service permits the download of transcoded data objects and selected metadata (DIP) according to the Licence applied to the data object.
  • The Reporting service permits the audit and reporting of transactions by each of the above services.”
  • Comments:

    this section presents the key service arrangement part of the SUM. this outlines the arrangement of software services and standards LIROLEM used to support the management and use of multimedia resources. As such it provides a point of reference for other software development and delineates what standards the development/ implementation used.

    it would have been helpful if the SUM had explicitly linked standards with specific service arrangements – however the connections will, in general, be deducible.

    Date Released: 2007 -11- 07 (Note: although this SUM is complete it is currently still on the eFramework development wiki – it may move)

    URI for Output: https://e-framework.usq.edu.au/users/wiki/DevelopmentSUMLiroLem

    Output – Lirolem – SUM

    Title: LIROLEM Service Usage Model

    Summary of contents:

    “The Lirolem/Virtual Studio is a means of digitally managing and preserving the output of students and staff at the University of Lincoln, irrespective of the format in which they are produced. Initially, the repository will concentrate on teaching and learning outputs within the School of Architecture, but it is intended that the repository will also manage research and teaching and learning outputs from all University departments. The repository will permit members of the University community to deposit, describe, search for, interact with and extract material that they deem valuable for use in their research, teaching and learning. This SUM describes the specific business processes involved in the operation of the repository and the services it provides. ”

    The SUM contains a business process model of LIROLEM; a SUM diagram of it, lists of eF service types used by LIROLEM their arrangement, design trade offs, and relevant standards.


    although excerpts from this SUM will create or be part of other outputs.  I consider a reference to the SUM as a entity to provide the most appropriate direct evidence of support for the eFramework.

    Page numbers: all

    Date Released: 2007 -11- 07 (Note: although this SUM is complete it is currently still on the eFramework development wiki – it may move)

    URI for Output: https://e-framework.usq.edu.au/users/wiki/DevelopmentSUMLiroLem

    Project – Lirolem

    Lincoln Repository of Learning Materials

    Short Project Name: Lirolem

    Programme Name: Repositories and Preservation Programme

    Strand: Matching funding for digital repository development /SUE

    Brief project description:

    ‘The University of Lincoln is developing a repository in which research outputs, exemplars of student outputs in non text based disciplines, and teaching materials, including copyright cleared digitised texts will be stored. […]

    The primary aim of the project is to lay the groundwork for the establishment of an institutional repository that will support a wide variety of non textual materials, e.g. digital animations of 3-D models, architectural documentation such as technical briefings and photographs, as well as supporting text based materials. By ‘groundwork’ we mean an infrastructure that includes both software and supporting documentation including a service definition, setting out what the repository will offer users, a model of content organisation which will set out how material will be organised within the repository (for example, where an object in the repository consists of multiple parts, how these parts link to each other), and a specification describing how object metadata will be created.

    More specifically the objectives of the project are to test the suitability of existing repository software, (such as e-prints) as a medium to store multimedia products, and to make such a repository publicly available, to document the four principal business processes associated with the repository, (depositing, cataloguing, searching, and retrieval), promote awareness and encourage use of the repository among academic colleagues, initially in the School of Architecture, and to provide training and documentation for users.’

    JISC Project URI: http://www.jisc.ac.uk/whatwedo/programmes/reppres/sue/lirolem.aspx

    Project URI: original site dead – content moved onto (multipurpose) wiki see:

    Start Date: 2007-04-01

    End Date: 2008-03-31


    Contact Name and Role: Julian Beckton (Project Manager)

    Name of Trawler: John

    Available Outputs:


    Project – SOURCE

    Project Name: SOURCE: Sharing Objects Under Repository Control with Everyone

    Programme Name: Repositories and Preservation Programme

    Strand: Information Environment

    JISC Project URI: http://www.jisc.ac.uk/whatwedo/programmes/reppres/tools/source

    Project URI: http://www.source.bbk.ac.uk/

    Start Date: October 2006

    End Date: October 2008

    Governance: RPAG

    Contact Name and Role: David Flanders, Project Manager

    Brief project description:

    “The primary aim of the SOURCE project is to create a standard and commonly used repository “plug” which will enable a bulk migration tool to “plug-in” and automatically transfer content from one repository to another … This project will therefore create two new tools to use with digital repositories.”

    • An interoperable ‘plug’ that will allow data to move in/out of the repository in a format that other repositories and services can immediately understand and will therefore enable a commonly understood method for access to the repository.
    • A bulk migration tool that can plug into the common repository plugs of two or more repositories and migrate content interchangeably from one repository to another.
    • Project Final Report

    Output – REMAP – User Requirements for RMDP: Use Cases

    Title: User Requirements for RMDP – Section 4: Identified Use Cases
    Number of pages or page numbers: pp 26-27
    Section: 4

    Date Released: November 2007

    URI for Output: http://edocs.hull.ac.uk/muradora/objectView.action?parentId=hull%3A25&type=1&pid=hull%3A97

    Summary of contents: Web services development to support records management, a specific form of preservation, has so far tended to be through the provision of commercial systems, though there is potential applicability of preservation Web services to be focused around specific records management needs.

    Web services, whilst offering great potential, do not in themselves offer integration between a digital repository and the desktop applications used to create digital materials. This gap can, though, be addressed through notifications, alerting material owners and/or creators to specific records management and/or digital preservation tasks that need to be carried out. The repository can thus enter into an engagement with the end-user in order to encourage RMDP processes over a period of time.

    The JISC-funded RepoMMan project4 based at the University of Hull has developed a tool to orchestrate Web services using WSBPEL (or just BPEL) over a Fedora repository5. The tool allows the user to interact with the repository in a variety of ways; the REMAP project will enhance and extend this tool to provide support for RMDP. The work will be based on user requirements for institutional RMDP and the development of related models describing RMDP workflow. REMAP will develop a notification layer as part of the overall orchestration to inform users of repository tasks that require their attention and encouraging their engagement with the system.

    The first stage in the project was a user needs gathering exercise to determine records management and preservation requirements. This work, which forms the substance of this report, was conducted with a range of people from the University of Hull (UoH) and staff from Spoken Word Services (SWS) at Glasgow Caledonian University. The interviews at Hull concerned themselves primarily with material in text form whilst the work with SWS concentrated on their work with audio material. The underlying intent of REMAP’s work is to embed digital repository interaction within working practices for RMDP purposes and thereby demonstrate the potential benefits of so doing.

    Additonal information: Section 4 outlines some prioritised use cases.