[Previous] [Contents] [Next]
An audience of about 25 attended this forum to hear discussions on issues specific to RLIN and RLG services. Karen Smith-Yoshimura represented RLG. Present to respond to questions were Innovative staff members Aaron Blazer, Doug Randall, Steve Silberstein, and Chick Markley.
Record transfer follow-up from last years meeting: Fewer libraries have been reporting problems with record transfer. Release 12 will include the ability to generate the required label file information, per specs provided by RLG after last years discussion. RLG now requires libraries to put their INNOPAC system number in the 001 and the RLIN record ID in the 035, prefaced by (CStRLIN). This is table-driven and can be done now without waiting for Release 12. Yale Laws load demonstrated that what RLG asked for last year can be done. As requested by users, RLG now retains text as entered in the 908 field for records transferred using PUT; this formerly was changed to all upper-case. The 908 field is not in the RLIN record and stays attached as a local note.
Representing Holdings: There has been no consistent method for libraries to upload holdings from INNOPAC. Many libraries strip item information and send bibs only. Some libraries, including the Getty Museum and Tarleton Law, are using 930s for summary holdings. These can potentially be in bibs, check-ins or both. For ILL purposes, it displays as SHS in the PAR display. Innovative has changed tags for output of 85x fields and RLG was asked to address this but has not yet reported back. Karen S-Y will come up with some guidelines on summary holdings so we can all begin to use a common field.
Retrolink Records: Original records created for projects for which RLG was the source copy will be loaded on RLIN using URLP identifier. These will be bibs without holdings information, but will be available for deriving records. RLG expects these to be used by libraries finishing off recon projects. RLIN libraries who contracted with Retrolink for their projects will be loading their records under their own LIs.
PUT, PASS, Z39.50, GUICAT: Only five users reported that they use PUT as their only method to transfer records from RLIN to INNOPAC. Half of the users reported using PASS alone or in combination with PUT. Only a few sites have GUICAT and Z39.50. Using PUT requires 24 separate steps but they can be scripted or combined in macros to streamline processing. RLG thinks PASS and PUT are interim solutions and all libraries will be moving to Z39.50 in the future. Release 12 will allow PUT records to overlay existing PAC bibs.
RLIN uses the 952 field to carry the holding library record ID in $a and holding library name in $b. Each holding library in an RLIN cluster has a separate 952. Libraries that use RLIN for cataloging copy must be able to view the holdings libraries and easily retrieve records in a given cluster. RLIN Zephyr has made this searching possible by Z39.50 clients with Use Attribute 12. INNOPACs Z39.50 client as implemented with GUICAT is deficient in respect to access to the RLIN 952s. First, the Z39.50 record is loaded through the librarys primary load table BEFORE it can be viewed. In order to view holding libraries (952s) you must also download all these fields when you add the record to your PAC. GUICAT users want separate tables for view and download similar to the character-based INNOPAC. Second, GUICAT users want the INNOPAC Z39.50 client to allow users to retrieve any record identified in a 952 field without rekeying (i.e., by doing a subsequent local number index search on 952 $a). Release 12 will support searching by all indexes supported by Zephyr including local number; any unmapped fields will be flagged by a $y tag. However, Release 12 does not remedy the GUICAT problems of a single view/load table or the inability to search RLIN IDs without rekeying. Other Z39.50 clients such as GEAC now offer the capability to display and search by the RLIN IDs in the 952 fields. Innovative has made no comparable commitments. [Clarifications added post-conference on much of this by Mary Chapman & Karen S-Y.]
Enhanced & Modified CC Definitions: These and other user definitions and documentation are being added to the RLG web site listed above. RLG has clarified the definition of full level records to specifically mean full level English language records, as records from foreign library members may be full according to different rules. Karen S-Y asked for volunteers to help review documentation going up on the web. If interested, contact Karen at firstname.lastname@example.org.
Adding Elements to Zephyr Full Record: RLG is surveying users now to see what additional elements they want to get when they pull Z39.50 records from Zephyr. Responses are still being compiled. A straw poll of those present had call number (950 and 955 fields) as the number one choice (090 field is already exported). Other possibilities include 952 subfields for microform generation, presence of electronic access, CC value, etc.
European Library Data Initiative: Records from the national libraries of Spain and France have been loaded into the RLIN bibliographic files. Records from CURL and the Deutsche Bibliotek are too large to be loaded the usual way. A Z39.50 client gateway is under development. Users will select files on RLIN and searches will be performed on the remote database and converted on the fly into RLIN MARC for display and USMARC for Z39.50 clients retrieval. This is a virtual expansion of the resource files. Release date is set for September 1, 1998. Early user candidates were recruited to test from both RLIN and GUICAT. For more information, see the European project web site listed above.
ISO for ILL Protocols: All RLIN ILL commands have been mapped to the ISO ILL protocols. Innovative has implemented only two ISO ILL transaction protocols. RLG plans to implement ISO ILL protocols so when documents are sent and received through Ariel the ILL records in ISO-ILL compliant systems could be updated automatically. The Innovative ILL module includes only borrowing, not lending. Some mutual development is ahead. RLGs goal is to be interoperable with multiple local systems.
Table of Contents Access: Blackwell Table of Contents records are available on a separate file through RLIN or Eureka, or Zephyr. Authors and titles are subfielded correctly. Titles are indexed but authors are not, as they are not in authorized form. A change request was submitted to index this particular file only but it is low on the priority list.
Record Transfer (continued): Users asked how long it takes to get dataload projects through the RLG queue. RLG members have higher priority than non-members; SHARES participants have higher priority than non-participants. RLG is working through big problems with regular contributors who have changed library systems and need to be reprofiled. Dataloads staff is small and involved in other competing projects.
SCIPIO records: Auction catalogs are a separate category with private attribute numbers. Getty has loaded these records and has a Date of Sale search capability.
[Previous] [Contents] [Next]