The Library of Congress » Standards » SRU

SRU (Search/Retrieval Using URL)

Implementors

Please send implementation information, including new entries as well as updates, to rden@loc.gov

See Also SRU Tools | SRU Servers    Disclaimer for External Links

  Ministry of Culture of Spain (February 2008)

Subdirectorate General for Library Co-ordination

The Virtual Library of Bibliographic Heritage  has implemented a SRU server that extends its OAI 2.0 implentation.

SRU base url

  • Metadata formats: Dublin Core, MODS, MARC XML
  • Timeframe: available now
  • SRW/SRU: SRU
  • System environment: UNIX
  • Access/restrictions: freely available

Contact: Mara Luisa Mart nez-Conde

Koninklijke Bibliotheek (updated December 5, 2005)

The Koninklijke Bibliotheek (National Library of the Netherlands) uses the SRU protocol as the main access to its databases and to the European Library, which is hosted by the Koninklijke Bibliotheek. SRU base-url for KB is http://www.kb.nl/cgi-zoek/sru.pl? and for the central index of the European Library the base-url is http://www.theeuropeanlibrary.org/sru/sru.pl?. An experimental SRU-portal running in the browser (Asynchronous, Javascript and and XML) is at: http://krait.kb.nl/coop/tel/SRUportal.

  • Metadata formats: Dublin Core plus extensions and internal XML formats
  • Timeframe: available
  • SRW/SRU: SRU
  • System environment: SRU server in Perl and portals in XSL and Javascript
  • Access/restrictions: free
  • Availability of source code: free
  • Toolkits used: none
  • Toolkits developed: none
Contact: Theo van Veen or Julie Verleyen

Adlib Information Systems (updated November 30, 2004)

Adlib Information Systems is developing an implementation of SRU for its customers. This extends the OAI 2.0 implementation which some of our customers are already using.

  • Metadata formats: Dublin Core, adlibXML, probably MODS and MARCXML (user configurable).
  • Profiles: SRW Base Profile and Adlib SRW Profile (yet to be defined)
  • Timeframe: available on Adlib 6.0.1 Q1 2005
  • SRW/SRU: SRU only
  • System environment: Windows 2000 and 2003
  • Access/restrictions: Server program only available for Adlib Internet server customers. They define the access they want to grant.
  • Availability of source code: Closed source.

Contact:ronald@adlibsoft.com

Archimed (updated November 30, 2004)

Archimed is a French software publisher, working on a meta-engine Z39-50 Web, and now implementing SRW 1.1 -- three products -- two commercial programs and a freeware tool. See Tools.

Contact: Guillaume Liékens

Library of Congress (updated August 4, 2004)

LC has implemented Index Data's YAZ Proxy which functions as a SRW/SRU/Z39.50 gateway to the Voyager Z39.50 server for the LC Online Catalog. LC supports the Explain and searchRetrieve operations and conforms to Version 1.1 of the standard.

  • Metadata formats: Dublin Core, MODS, and MARCXML
  • Timeframe: available now.
  • SRW/SRU: Both
  • System environment: Unix
  • Access/restrictions: Freely available
  • Availability of source code: Open source from Index Data
Server configuration information
Contact: Larry Dixson

Mike Taylor (updated July 14, 2004)

I've developed CQL-Java, a suite of free tools for handling CQL queries in Java. details.

  • Metadata formats:
  • Indexes Supported: Dublin Core, Bath
  • Timeframe: available now.
  • SRW/SRU: SRU
  • System environment:UNIX/Linux; untested on Windows but should work.
  • Access/restrictions: Freely available (GNU GPL).
  • Availability of source code: Everything is open source (GNU GPL).
  • Toolkits used: none!
  • Toolkits developed: CQL compiler, API to CQL tree representation, random CQL-query generator, CQL compiler test suite.

Contact: Mike Taylor

OCLC/PICA (updated January 9, 2004)

OCLC PICA's PiCarta service is a ZING /SRU server interoperating with the iPort portal as a client. The iPort portal is developed by the University of Tilburg for OCLC PICA. The products PSI and LBS versions 3 and 4 (Local bibliographic System) also have ZING/SRU server capability indicating holdings availability for the bibliographic records. A test server is available at: http://greta.pica.nl:1080/sru/

  • Metadata formats: Dublin Core, MARC XML
  • Timeframe: available
  • SRW/SRU: SRU
  • System environment: Solaris Sybase
  • Access/restrictions: for test purposes; not a full database
  • Availability of source code: for partners
  • Toolkits used: not applicable
  • Toolkits developed: not applicable

Contact: Janifer Gatenby

OCLC Research (updated January 8, 2004)

See Tools.

OCLC Research has developed a 100% pure Java implementation of an SRW/U server using the Apache SOAP toolkit. The implementation specifies an interface to underlying databases. Currently the interface has been implemented for MIT's DSpace database (using Jakarta Lucene) and for OCLC
Research's Pears/Gwen databases. The SRW/U server and the Pears/Gwen database software are available as OpenSource from OCLC Research.

  • Metadata formats: User defined
  • Timeframe :Available now
  • SRW/SRU: Both
  • System environment: 100% pure Java, runs anywhere
  • Access/restrictions: Freely available.
  • Availability of source code: Everything is OpenSource
  • Toolkits used: Apache SOAP, Apache Log4j, Apache Xalan, Apache
    Xerces, zing.z3950.org CQL parser
  • Toolkits developed: SRW/U server, Pears Text Database, Gwen Search
    Engine

Contact: Ralph LeVan

Index Data (updated January 7, 2004)

See Tools.

Our YAZ toolkit supports SRW/SRU (in addition to Z39.50, of course) in the client and server roles. On the client side, SRW/SRU is hidden under the ZOOM API which means that it's easy to use, but also that it's available with practically no effort in any application or higher-level API that is based on our ZOOM/C implementation. The server side is based on our popular front-end server and requires only minimal changes to enable SRW in any existing application based on that API. We also offer a general-purpose SRW-to-Z39.50 gateway/Z39.50 proxy.

  • Metadata formats: Dublin Core, MARCXML, MODS, etc. etc.
  • Timeframe :Available for test and development
  • SRW/SRU: Both
  • System environment: UNIX, Windows, etc.
  • Access/restrictions: Freely available.
  • Availability of source code: Everything is open source, either GPL or Berkeley-style licenses.
  • Toolkits used: GSOAP, SOAP::Lite, YAZ, MS XML, EXPAT, xmlLite, libXML, .NET.
  • Toolkits developed: SRW/SRU tools, YAZ toolkit, ZOOM/C binding, gateways/proxy servers

Contact: Sebastian Hammer

Cheshire project (updated January 5, 2004)

The Cheshire project has implemented SRW as a front end to their Z39.50 databases and are distributing this as part of their normal package.

  • Metadat formats : DC, MarcXML, MODS, OAI MARC, EAD and others depending on the database.
  • Timeframe: Version 1.1 SRW software and complete CQL parser now available at http://srw.cheshire3.org/downloads/. Feedback isappreciated!
  • System environment :Linux/Win32/Solaris/MacOSX/*BSD. Pure Python.100% Free and Open Source.
  • Access/restrictions: Test server is freely available at http://srw.cheshire3.org:8080/l5r
  • Availability of source code: GPL.
  • Toolkits used: PyZ3950, ZSI
  • Toolkits developed: CQL Parser, SRW client, SRW server

Contact: Robert Sanderson http://srw.cheshire3.org

The Library of Congress » Standards » SRU

March 16, 2010
Contact Us