This script modifies the files which appear as the Tag Information in the Aleph Cataloguing client so that links are added to the full MARC 21 manuals on the Library of Congress web-site. This makes it easy for the cataloguer to call up the full manual whenever they are in doubt. The script copes correctly with the 006 and 008 field sub-formats, and provides helpful links to the MARC language and country code lists.

This document (11 pages; see "Files" at the head of this page) focuses on how to reduce as much barriers as possible in Aleph OPAC.

The ALEPH OPAC supports the inclusion of a SFX button. But you could also include the SFX services offered for a bibliographic record by using the SFX API. This is an example of how to do that for records that holds an ISSN. This doesn't change the native ALEPH-SFX integration.

This extension to the Aleph OPAC and to the SFX Menu provides a graphical representation of our often complex serials holdings. It enables the user to see very quickly which years of a journal are available at each library and which are available on-line. Information from the SFX API is combined with the Aleph holdings in a single graphical summary. The bar charts shown for electronic holdings are clickable, taking the user through to the correct year (where supported in the linking syntax).

FindIt is an Aleph record extension script. It's purpose is to offer extended services for items in Aleph. The extended services include maps, openurls to document delivery forms, google book, worldcat.org, books in print, ulrichs, and amazon.com reviews.

We wanted to be able to integrate Google book covers with syndetics in our Aleph OPAC. To do this, we created the following scenario:

• When we have a syndetics image, display link (no covers) to Google.
• When we have no syndetic image, display Google cover. If we have no Google cover, display just a link to google books.
• If neither Google nor syndetics has a cover or link, then display nothing.

There are several ways to provide your OPAC with a spellchecker. This is one way using the Yahoo! webservice. You could hook it up to other spellcheckers like the Google SOAP webservice or Pspell. This example uses the javascript framework of Prototype for DOM manipulation, AJAX call and PHP to handle the communication with the Yahoo! REST webservice. It does require that you register your application with Yahoo! and there is a limit of 5000 requests / day.

When a search is done in the local OPAC the query is passed to MetaLib X-server and search results are displayed in the OPAC. This is a way to give the users a small federated search from within the OPAC. Putting the local search in a broader context.

We can't use PHP, so I've developed this code to read the JSON return from Yahoo! Spelling suggestion service. Suggestions are returned following a search that has 0 hits and then made clickable. However, it could in theory be entered anywhere a search variable is passed.