Output – IESR – Latest Additions RSS feed

Title: IESR Latest Additions RSS feed

Date Released: Unknown

URI for Output: http://iesr.ac.uk/feeds/latestadditions.xml

Summary of contents:

Allows applications or users to subscribe to the 10 latest resources added to IESR.

Additional information:

Comments:

Output – IESR – OpenURL Link-To Resolver

Title: IESR OpenURL Link-To Resolver

Date Released: Unknown

URI for Output: http://iesr.ac.uk/use/openurl/

Summary of contents:

“The IESR OpenURL ‘Link-To’ Resolver service provides retrieval of IESR XML records for single entities using Z39.88-2004, OpenURL Framework, syntax. Currently support for OpenURL syntax is limited allowing retrieval by identifier only using a Key/Encoded Value (KEV) request inline by HTTP. Values must be URL-encoded.”

Additional information:

Comments:

Output – IESR – Registry m2m Interfaces (OAI-PMH, SRU/W and Z39.50)

Title: IESR Registry Machine to Machine Interfaces (OAI-PMH, SRU/W and Z39.50)

Date Released: Unknown

URI for Output:  http://iesr.ac.uk/use/oaipmh/, http://iesr.ac.uk/use/sru/http://iesr.ac.uk/use/z3950/

Summary of contents:

These outputs provide m2m interfaces for cross, meta- or federated search applications.

Additional information:

Comments:

Output – SAFIR: Policy – overview

Title: York Digital Library: Digital Library Policy

Pages: all
Date Released: 12 Feb 2009

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

Summary of contents:
This document provides the policies of York Digital Library; the digital library has stated policies on:

  • Metadata
  • Code and documentation
  • Resources
  • Content [scope]
  • Submission
  • Rights
  • Preservation

York Digital Library has chosen to use Creative Commons (NC ND BY) licenses for its Metadata, documentation, and resources (where possible).

Comments:

Although the sample policies are in themselves useful – covering things like takedown policy – the explicit use of Creative Commons for the work of the digital library team is worth noting both for its use and for the instituional view it indicates.

Project – From Entry to ETHOS

Project Name: From Entry to ETHOS

Short Project Name: From Entry to ETHOS

Programme Name:  Repositories and Preservation

Strand: SUE

JISC Project URIhttp://www.jisc.ac.uk/whatwedo/programmes/reppres/sue/entry.aspx

Project URIhttps://www.kcl.ac.uk/blogs/etheses/

Start Date: 1 September 2007

End Date:  31 December 2008

Governance: JISC IEE

Contact Name and Role:   Russell Burke and Catriona Cannon (Project Managers)

Brief project description:

The project will develop an e-theses repository, entirely compliant with EThOS and designed to support the easy deposit and ready exchange of data. The project will expand and enhance the EThOS Toolkit by addressing key institutional administrative questions.  It will explore in detail the entire process of submission and handling from examination entry form through to the upload of the final thesis. The project will chart the varied workflows of students, of examiners and of the Examinations Office, school offices and the Bibliographic Services team.

Name of Trawler: Mahendra Mahey

Outputs: (just link to individual output postings) as a bulleted list

  • Workflow models and workflow tools to support students, examiners and administrators through the tasks of creating, submitting, processing, describing and publishing e-theses
  • A model institutional policy for e-theses along with supporting procedures and forms
  • Guidance notes to support the implementation of an e-theses policy
  • An EThOS compliant repository that meets required standards in terms of format, structure, metadata and so on

Project – OpenDoar

Project Name: OpenDoar

Programme Name:Digital Repositories Programme 2005-7

Strand: Information Environment, e-Administration

JISC Project URI: http://www.jisc.ac.uk/whatwedo/programmes/digitalrepositories2005/opendoar.aspx

Project URI: http://www.opendoar.org/

Start Date: 1st Jan 2005

End Date: 30th June 2006

Governance:

Contact Name and Role: Bill Hubbard, Project Manager

Brief project description:

“OpenDOAR will categorise and list the wide variety of Open Access research archives that have grown up around the world. Such repositories have mushroomed over the last 2 years in response to calls by scholars and researchers worldwide to provide open access to research information.

OpenDOAR will provide a comprehensive and authoritative list of institutional and subject-based repositories, as well as archives set up by funding agencies – like the National Institutes for Health in the USA or the Wellcome Trust in the UK and Europe. Users of the service will be able to analyse repositories by location, type, the material they hold and other measures. This will be of use both to users wishing to find original research papers and for third-party “service providers”, like search engines or alert services, which need easy to use tools for developing tailored search services to suit specific user communities.”

Outputs:

  • Descriptive list of open access repositories of relevance to academic research.
  • Comprehensive & authoritative list for end users wishing to find particular types of, or specific repositories.
  • Comprehensive, structured and maintained list with clear update and self-regulation protocols to enable development of the list.
  • Crominent international role in the organisation of and access to open access repository services.
  • Supporting Open Access outreach and advocacy endeavours within institutions and globally.
  • Survey the growing field of academic open access research repositories and categorise them in terms of locale, content and other measures

Output – SAFIR: Requirements Specification – OAIS

Title: Digital Library Project (SAFIR): Requirements Specification

Pages: 5-13
Date Released: 07 March 2008

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

Summary of contents:

This section of the specification uses the Reference model for Open Archival Information Systems (OAIS) as a basis for analysing the repositories context and creating a specific reference model on which to base the requirements specification.

The following the OAIS model the analysis considers:

  • the designated communities of the repository
  • how it aproaches different functional areas (ingest, archival storage, data management, administration, preservation planning, and access)
  • the information model and information lifecycle that has to be supported
  • issues of interoperablity and integration

Comments:

This provides an example of a lightweight use of OAIS as a method of describing and analysing the context of a repository. As such it considers the whole information lifecycle as part of the planning process.

Project – IESR

Project Name: Information Environment Service Registry (IESR)

Programme Name: Information Environment

Strand: Shared Infrastructure Services programme

JISC Project URI: http://www.jisc.ac.uk/whatwedo/services/mimas/iesr.aspx

Project URI: http://www.iesr.ac.uk/

Start Date: 1st Jan 2003

End Date: 31st Match 2009

Governance: JISC Integrated Information Environment committee?

Contact Name and Role: Vic Lyte, Project Manager

Brief project description:

“The IESR has been developed to provide a registry of information about electronic resources that are of value to teachers, researchers and learners. The IESR project is part of JISC‘s Shared Services Programme.

The aim is to create a reliable source of information that other applications, such as portals, can freely access through machine-to-machine protocols, in order to help their end users discover resources of assistance to them.

The IESR contains information about the resources themselves, technical details about how to access the resources, and contact details for the resource providers. For resource providers the IESR will hold a master description of their electronic resources, to which other potential users of the resources may be directed.

The registry is held in an XML repository using Cheshire information retrieval software.”

Outputs:

Output – VIF: Version labels or taxonomies

Title: VIF: Version labels or taxonomies

Pages: webpage
Date Released: May 2008

URI for Output: http://www.lse.ac.uk/library/vif/Framework/Essential/taxonomies.html

Summary of contents:
“Clarity of versions is important; but the terminology, even for just articles, is not static or decided. Consistent usage within one repository, possibly for particular items may be achievable, such as at LSE, but care should be taken in their use and their implementation should be supported by clear policy and definition.

Explicit definition of vocabulary used is a minimum requirement if taxonomies are used.”

Suggested taxonomies are the those produced by the following projects:

Comments:
In light of their survey results (noted here: https://rrtsynthesis.wordpress.com/2009/02/03/output-vifthe-results-of-the-vif-user-requirements-study-taxonomy/ ) VIF had already noted that widespread consistency in the use of any taxonomy is unlikely. Here they have recommended some appropriate standard taxonomies and noted that within a single repository consistent use may be possible.

Outputs – VIF: Dates

Title: VIF:Dates

Pages: webpage
Date Released: May 2008

URI for Output: http://www.lse.ac.uk/library/vif/Framework/Essential/dates.html

Summary of contents:

“# If there is ever only one option for a date, then it is critical that you find a way to make it clear which date you are referring to. You should agree on what the most relevant to your repository is, apply it consistently and provide information to users about it.
# VIF recommends is that if you only use one date, it should be Date Modified (by the author, not the repository) and wherever possible, this should be accompanied by a description of who made the changes and why.
# A key thing to remember when considering which date to use to enhance version identification, is that it should relate to the object at hand, not to the repository or to an understanding of the workflow.”

Comments:
The VIF project provides guidance about the, often ambiguous, use of dates in repositories.