Related product I-Share

Frequently Asked Questions about RDA in the I-Share Environment

New RDA MARC fields

THE 264 FIELD NOW DISPLAYs IN THE OPAC

In VuFind local and the I-Share union catalog, the 264 now displays correctly on the Results page as well as the Record page. The VuFind indexes were rebuilt during summer 2013 to enable the field to display correctly on the Results page. In WebVoyage, this field does not and will not display: updates to WebVoyage have ceased.

WHEN WILL THE 336, 337, 338 FIELDS DISPLAY IN THE OPAC?

At this time, the 33X fields will not display in VuFind, although the 338 now functions like the GMD for faceting purposes. In WebVoyage, these fields do not and will not display: updates to WebVoyage have ceased.

SINCE A 338 IS PRESENT, SHOULD A GMD ALSO BE ADDED?

Since the 338 field as well as other bibliographic coding are now used for format identification in VuFind, the GMD no longer needs to be added to new RDA records. As seen in “Formats in Vufind”, the GMD continues to be used to identify format. Thus, VuFind will continue to function properly for existing RDA records that contain the GMD. 

Tag tables

Have the Voyager tag tables been updated for the new RDA fields?

Yes. Updated tag tables are available under the heading I-Share Consortial Tag Tables. If you will be updating your tag tables, we recommend updating all of them. Keep in mind, these files are consortial tag tables and will not include any local customizations.

For Windows 7 users, log in as a full Windows Administrator to upload these tag tables in order to avoid any login permissions problems. Once the tables are updated, open the Cataloging client once to “set” the changes, and then have the regular user log in and test the Cataloging client. 

Bulk imports

Is there a workaround for RDA records that cause bulk import errors?

Yes. For bulk imports from OCLC, which do not output in Unicode, the copyright symbol used in RDA records is one of several characters that can fail when Voyager attempts to convert the records to Unicode.

Update your bulk import rule’s expected character set mapping of imported records from OCLC (non-Unicode) to MARC21 MARC-8 (non-Unicode) to avoid this error. MARC21 MARC-8 will accept a greater number of diacritics and special characters, including the copyright symbol.