Output – HILTIV: demonstrators

Title: HILT phase IV demonstrators

Pages: webpage
Date Released: June 2008
URI for Output: http://hilt.cdlr.strath.ac.uk/hilt4/demonstrators.html

Summary of contents:
HILTIV has produced a number of service demostrators examining “cross-searching multi-subject scheme information environments”. The demonstration aspect of their work is that the mapppings being used are of selected sections of vocabularl schema.

They have a:

• SOAP client http://hiltm2m.cdlr.strath.ac.uk/hilt4/hiltsoapclient.php
• SRU client http://hilt4.cdlr.strath.ac.uk/hilt_sru.cgi
• A cross vocabulary subject browser http://hilt4.cdlr.strath.ac.uk/hilt_srw.cgi
• A spellchecker for subject terms http://hiltm2m.cdlr.strath.ac.uk/lucene/spellchecker.php
• A cross-vocabulary dictionary of subject terms http://hiltm2m.cdlr.strath.ac.uk/wordnet/test.php

They have also embedded the demostrator service within BUBL (an catalogue of resources relating to Library and Information Sciences) http://bubl.ac.uk/hilt4.htm
They have also created some form of client for OCLC http://linuxserv.cdlr.strath.ac.uk/~anuj/cgi-bin/hilt4/oclc_client.cgi

Comments:

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 – IESR – OpenSearch Plug-in

Title: IESR OpenSearch Plug-in

Date Released: Unknown

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

Summary of contents:

“The IESR OpenSearch Plug-in allows you to add an IESR search to your browser in order to discover new electronic resources. OpenSearch is a collection of simple formats for the sharing of search results. The plug-in adds a search box to the top right-hand side of your browser.”

Additional information:

Comments:

Output – IESR – IESR Registry

Title: IESR Registry

Date Released: Unknown

URI for Output: http://iesr.ac.uk/service/iesrbrowse?type=new

Summary of contents:

“IESR is a resource discovery tool intended to benefit the UK academic community. Access is through web and machine interfaces or search plug-ins.”

Additional information:

There are a number of machine to machine interfaces to the IESR. The link above is to the web interface aimed at users.

Comments:

Project – HILT Phase IV

High-Level Thesaurus (Phase IV)

Short Project Name: HILT IV

Programme Name: Repositories and Preservation Programme

Strand: Shared Infrastructure Services

Brief project description:
Pilot terminology service to assist users of the IE with the discovery of the appropriate resources by subject browse and search.

“‘HILT phase IV: Transition to Service Testbed and Future Requirements Study’ aims to research, investigate and develop pilot solutions for problems pertaining to cross-searching multi-subject scheme information environments, as well as providing a variety of other terminological searching aids.

HILT phase IV will build on the work of phase III by moving HILT to a transition to service phase. This will allow an initial entry-level service to be built, tested for user requirements and retrieval effectiveness, refined in line with the findings, and extended to permit the use of a range of distributed terminology services for interoperability. It will also allow an examination of the level of need and interest amongst JISC services in respect of an operational service and, if appropriate, a scoping of the costs and requirements of a future operational phase of the service.

HILT phase IV will also conduct a parallel programme of research into selected topics germane to terminology services, as well research into the costs and requirements of an initial entry-level operational service and any future extension of this. ”

JISC Project URI: http://www.jisc.ac.uk/whatwedo/programmes/reppres/sharedservices/hilt2

Project URI: http://hilt.cdlr.strath.ac.uk/index.html

Start Date: 1st June 2002

End Date: 29th January 2009

Governance: JIIE

Contact Name and Role: Dennis Nicholson (Project Manager)

Name of Trawler: John

Available Outputs:
The following demostrator services are available:

• HILT SOAP client
• Demo of SRU
• HILT2 Emulation
• Vocabulary Browse/Search
• Lucene Spell Checker
• Wordnet
• BUBL Search (example of embedding toolkit elements in a service)
• OCLC client

Comments:

Project – EMBRACE

Project Name:

Embedding repositories & consortial enhancement

Short Project Name: EMBRACE

Programme Name:  Repositories and Preservation

Strand:  Repositories Start-Up and Enhancement

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

Project URI:  http://www.sherpa-leap.ac.uk/embrace.html

Start Date: 1 May 2007

End Date: 30 October 2008

Governance: JISC IE

Contact Name and Role:  Martin Moyle (Project Manager)

Brief project description:

EMBRACE will enhance the SHERPA-LEAP hosted repositories by improving the service architecture and by migrating the partner repositories from EPrints 2.3 to EPrints 3. The Eprints Application Profile will be implemented for the hosted repositories, and advocated to the other LEAP partners. A tool to embed citations and other information into the text of eprints at deposit will be developed, implemented for the EPrints repositories within the consortium, and made available on an open source basis to the community. A training programme will be arranged to support these technical measures.

EMBRACE will also investigate the challenges of embedding repositories of digital assets in institutional strategy. The espida toolkit will be used as a starting point for a focused investigation encompassing e-prints, e-theses, learning objects and primary data. The project will deliver a toolkit to support the institutional embedding of digital repositories.

Name of Trawler: Mahendra Mahey

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

• Upgrade of SHERPA-LEAP repositories to EPrints 3.0, together with more robust architecture for the SHERPA-LEAP hosted repository service.
• Implementation of and advocacy for the Eprints Application Profile.
• Creation of a generic citation support tool for IRs, with an EPrints implementation.
• Testing, evaluation and adaptation of the espida toolkit.
• Report on repository strategy and sustainability, covering a number of types of digital asset, at a minimum of 3 SHERPA-LEAP institutions.
• Consolidated generic, reusable and adaptable toolkit to support the embedding of repositories of digital assets in institutional strategy and policy.

Project – NAMES

Project Name: Names: Pilot national name and factual authority service

Programme Name: Repositories and Preservation Programme

Strand: Information Environment

JISC Project URI: http://www.jisc.ac.uk/whatwedo/programmes/reppres/sharedservices/names.aspx

Project URI: http://names.mimas.ac.uk/

Start Date: 1st May 2007

End Date:30th September 2008

Governance: RPAG

Contact Name and Role: Amanda Hill, Project Manager

Brief project description:

“The project is scoping the requirements of UK institutional and subject repositories for a service that will reliably and uniquely identify individuals and institutions.

A prototype service is under development to test the various processes involved. This includes determining the most appropriate data format, setting up a test database, mapping data from different sources, populating the database with records and testing the use of the data.

This will provide important information about the future usefulness of a name authority service for institutional and subject-based repositories, and other applications beyond the repository sector.”

Outputs:

• Prototype name authority service
• Web interface using NAMES api (mentioned in blog post)
  
• Landscape Report
• Usage Scenarios
• Requirements Report
• Data Analysis and FRAD mappings
• Software Requirements Specification
• NAMES blog

Comments:

The prototype service is now available as at 13th Jan 2009, but some development work is still to be done (acc to Names blog last paragraph).

Output – VIF: Embedding Versioning

Title: VIF: Embedding Versioning Information in an Object

Pages: webpage
Date Released: Jan2008

URI for Output: http://www.lse.ac.uk/library/vif/Framework/Object/index.html

Summary of contents:
Because it is entirely possible for users to access objects within a repository without ever seeing any metadata, VIF recommends that some versioning information is embedded into the object and suggests the following:

“It is strongly recommended that at least one of the following solutions to embed versioning information into object is advocated and used systematically within a repository:

1. ID Tags and Properties Fields
2. Cover Sheet
3. Filename
4. Watermark”

The framework provides some further details about each of these. In essence – use something and use it consistently

Comments:
Supporting interoperabilty, especially interoperability over time is reliant on being able to distinguish between versions. It maybe simple to regard ‘use something consistently’ as a standard but if a repository at least follows it’s own standard. this provides a starting point for interoperability.