Skip to main content
more options

CATALOGING PROCEDURES FOR NETWORKED ELECTRONIC RESOURCES, pt. 5

(LTS Procedure #96)


 

 

PARTS OF THIS SECTION ARE OBSOLETE.  Instructions regarding Voyager records are generally up to date. Anything referring to ENCompass is obsolete; maintenance of records for Find It! databases or e-journals is done within the Electronic Resource Management System (ERMS). Documentation is forthcoming.


5. DATABASE MAINTENANCE OF VOYAGER RECORDS

5.1 General considerations. Most database maintenance for electronic resources involves straightforward updates and/or changes to URLs, holdings and coverage, or description fields. This work, along with tasks such as PURL creation and the deactivation and withdrawal of resources and interfaces, is normally done by LTS staff, though in certain cases staff in other processing units may do some or all of the maintenance work. More complex updates, such as title changes, are performed by catalogers.

Be sure to update both Voyager and Find Databases records when making changes, except when the changes involve data that appears only in the Voyager record. As of February 1, 2003, when a resource is available through multiple interfaces, a separate Voyager record is made for each interface. In ENCompass also, additional interfaces require separate records for each interface and the titles require qualification. See Section 2.7 of this document for further details.

5.2 Changes and updates. Each time you update a record in Voyager and/or Find Databases, check the following fields for consistency:

  • Voyager BIB ID -- should appear in the Find Databases record.
  • 506 / Restrictions -- MARC data should not include Cornell-specific language.
  • 520 / Description -- should not include information about the interface, only the contents of the resource.
  • 653 / Subject Captions -- Follow list in Appendix B of this document.
  • 856 / URL & PURL -- verify that URLs or PURLs for all multiple interfaces are recorded in separate Voyager records and that each URL or PURL appears on its corresponding Find Databases record; verify that the PURL (or URL, if there is no PURL) appears in $u. In ENCompass, make sure the object link is made to the correct URL.
  • 899 / Local Series -- JSTOR and other "gathering" terms should appear in the Voyager 899 field. In Find Databases, the 899 term should be in a "subject" field.

Title changes. Title changes should be referred to a cataloger in the appropriate processing center. For more information, see Section 2.11.

For online serials and integrating resouces, follow CONSER guidelines and AACR2 12.1B8 etc. for creating new Voyager records or updating existing ones.r

For Find Databases resources, the number of records in ENCompass should be the same as the number of records in Voyager. In other words, if the Voyager record is updated because the resource has changed title and the old title is no longer available, the Find Databases record should be updated similarly. If a title change in Voyager results in two records, there should be two records in ENCompass also. It is important to make sure, if a record is being updated in Voyager and Find Databases, that the earlier title(s) are added in Find Databases as "alternate" fields.

520 / Description. If the proposed change seems significant enough to affect subject headings, contents fields, etc., this work should be referred to a cataloger in the appropriate processing center.

In Voyager, insert, edit, or delete text as necessary. In Find Databases, rekey or copy/paste text from the updated Voyager 520 field.

856 / URL. If a PURL has been assigned to a given resource, make changes to URLs in the PURL record. Do not update the Voyager or Find Databases record. If a PURL has not been assigned, update both the Voyager and the Find Databases records with the new URL.

To update the URL in Find Databases, first change the "URI" field. Then copy the new URL and replace the old URL in the "object" tab. Save the record and check the link to make sure it goes to the right resource.

Holdings. In Voyager, follow CUL guidelines. Since holdings are not given in Find Databases, no holdings updates are recorded in the ENCompass records.

Withdrawals. In Voyager, follow CUL guidelines. In Find Databases, do the following to unlink and withdraw resources.

  • Call up record to be withdrawn, by title. If multiple hits appear, choose the correct record by matching up the Voyager ID.
  • In metadata record, click the Relationships tab. Unlink the object record from the top container by single clicking on it, clicking "Record" menu, selecting "UnLink" and clicking "Selected Parents". The container, or parent, in the Relationships window disappears.
  • Use the same steps to unlink the object record from all remaining containers listed in the Relationships window, one by one. The object record is now orphaned.
  • In top toolbar, click the Relationship button to open the "Relationship Manager". In Repositories column, click "+" next to "Find Databases Repository". Scroll down to the end of the alphabet, and below "Y-Z" sits the orphaned record.
  • Right-click on orphaned record. On pop-up menu click "Copy". Then find the "Withdrawn" container just above in the same column. Right-click on it, then click "Paste as Child".
  • The "Withdrawn" container opens, showing all withdrawn records including the one you have just added. Double-click on your title to open the record.
  • Click the Relationships tab. The Relationships window that opens should show your record linked only to the "Withdrawn" collection. If so, all is well and you can close the record. If any other collection appears, unlink from that collection using the second step above.