Enter application description here...

This modified p-sys-01.xml file can be used in the case where you have multiple ADMs, each with its own pc_server port. 

• - This file would be placed in the $alephe_root/pc_b_eng directory.

This is a simple grep command to find the most common post-indexing error messages which may occur in $data_scratch log files

Earlier this year Bowker released Sydentics Plus which allows the embedding of enhanced data such as tables of contents and summary information without the need for pop-ups.

On-the-fly webOPAC/Primo translation with Google Translate API.
Let users translate your webOPAC or Primo to what language they want.
Save work translating webOPAC or Primo by hand to different languages.

This is a set of VBscript functions and a subroutine we use for converting patron data from the university's PeopleSoft information system to a patron file in PLIF format that can be loaded into Aleph using the Circulation p_file_20 service. It is one component in an overall procedure that consists of:

• Two view tables in PeopleSoft, one containing student data and one for faculty/staff data.
• Another view table made available by the university IS department that maps university ID numbers to network usernames. This is so that one of the ID records placed in the PLIF file can include the network username in the Key Data field, to enable LDAP authentication when logging on to the My Account functions in the online catalog.
• Additional tables in Access that map codes used in PeopleSoft student and staff records to codes we use in our Aleph patron records. (The attached queries show how these tables are used, but since the codes are institution-specific, I have not attached the table data.)
• Simple VBscripts that are invoked by a Windows shortcut to start MS Access and run the macro to build either a student or faculty/staff PLIF file, then copy the output file to a file share on a network server.
• A Microsoft Access database that links to the three tables above using and ODBC connection, and includes a macro, several queries, temp tables populated by the queries, and the VBscript functions and subroutine included here. Most of the functions are invoked by the Make Table query that is used to populate the a temp table that becomes input for the Aleph_Create_PLIF subroutine. The output of that subroutine is a PLIF file saved on the user's hard drive (the script used to invoke MS Access copies this file to a file share when the user exits Access). I've included the Make Table query along with a file of containing the functions, but the query itself is hightly institution-specific, since it maps various status codes used in PeopleSoft to codes we use in our Aleph patron records.
• A custom service on the Aleph server that transfers the PLIF file from the file share (which is also accessible by a web server) to Aleph, and then invokes p_file_20 to load the PLIF file into Aleph.

Here is a simple jQuery snippet you can use to pull additional data into your full view (or any other files in your catalog).
In this example we use it to query the X-Server to show us the number of additional records linked with the given classification code, and link it. Users can instantly see what's linked without having to click through to the default service menu window.

The official SDI service, p_sdi_01, produces rather basic e-mail output which does not use the newer XSL templates. It is hard to control the formatting of the messages. This service allows the e-mail output to be controlled fully by the library, including the provision of links to the catalogue, lists of items, etc. The RSS feeds are also enhanced to comply with standards more fully.