*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
Directly export a MARC file of Voyager records to OCLC for processing.
...
IV. Google Utilities
Various scripts for Google and HathiTrust Voyager extracts. Some are run by LTS staff; some by the project manager for the Google Project and who also serves as liaison to HathiTrust.
a. Build Google Extract List for a Location: Sends a list of candidates to Google for selection.
b. Build MARC XML File for GOOGLE Based on List of Barcodes: Used when Google metadata is missing or needs replacing.
c. Build MARC XML File for HATHI Based on List of Barcodes: Used when HathiTrust metadata is missing or otherwise not useable.
d. Build MARC XML File of KIRTAS Barcodes Not Found by
...
Google: Used when Kirtas metadata is missing or needs replacing.
e. Google Metadata Shipment: Takes barcode to get BIB, transforms BIBS to MARC XML for shipment to Google. Used to correct previously sent data.
f. Hathi Metadata Shipment: Takes barcode to get BIB, transforms BIBS to MARC XML for shipment to Hathi. Used to correct previously sent data.
g. HathiTrust MultiVol Monograph Extract: Reports status of currently held/withdrawn/lost multi-vol items to Hathi (at item level).
h. HathiTrust Serials Title Extract: Reports currently held serials to Hathi (at title level).
i. HathiTrust Single Monograph Extract: Reports status of currently held/withdrawn/lost single mono items to Hathi (at item level).
j. MARC and MARC XML Files for Google Shipment and Hathi: Creates a Voyager Bib file with 903 field with Google shipment date, to reload into Voyager. Creates MARC XML files for Google and Hathi.
k. Test a File of Item Barcodes for Valid Checksum: Makes sure barcodes are valid.
l. Update list of materials Cornell will not supply to Google
...
: Manually transfers a file for pick-up by either Hathi or Google.
...
V. Reports and Extracts
Location for scripts that create reports or extract records as part of routine database maintenance processes.
a. General Withdrawals Report: Generates a count by library of items withdrawn over a given time period, typically the prior month.
b. Inconsistent Item Location Report: Creates a serial and non-serial list of MFHDs and items where their location codes do not match.
c. ISBN Extract: Extracts ISBNs from a MARC record file. Staff member can then batch search OCLC using these ISBNs.
d. Less than Full Level Order recordsrecords: Looks for preliminary “on order” bib records.
e. Lost/Missing Reports: Generates a list of titles for books withdrawn due to the item being lost or missing.
f. Mfhd Copy Number Clean-Up: Compare the copy number in the MFHD 852 subfield t with the copy number in the item record. Output contains some routine fixes which are extracted for manual correction.
g. OCLC LHR Exception Reports: Receive email announcements of our local holdings exports. The Exception Reports can be examined on the OCLC Produce Services website. Any holding that was not added will have our Institutional Record Number, i.e., our holdings ID along with a reason why it was not loaded. Staff member must correct each holding in Voyager as appropriate so that the holding will be resent to OCLC. (This is not an LS Tools script.)
h. OCLC Unresolved Records: Receive email announcements of our daily cataloging export results. Any coded as unresolved appear in a MARC file which is downloaded from OCLC Product Services website. Our holdings for these records were not added to WorldCat due to MARC errors. Staff member must manually examine each record in Connexion to correct error(s) and add our holdings to OCLC. (This is not an LS Tools script.)
i. Report Duplicate Government Documents: Extracts a list of government document Voyager bibs where the OCLC number and 245 subfield a match.
j. Suppressed Mfhds with Unsuppressed Bibs: Looks in Voyager for bibs without at least one active (unsuppressed) MFHD.
...
Administrative Group
I.Clean Up Voyager
This section of LS Tools contains a set of tools that are currently in development. Each of them contains a menu of fields/issues that can be chosen to be either reported upon or corrected. The "Clean Up" tools offer the options of checking the length of the 006 and correcting its length if necessary, checking that the pub date matches the 008 date and correcting it, dropping leading zeros or extra text from 035 OCoLC fields, removing 995 Hivolm fields, and/or correcting malformed 948 fields. The "Report" tools offer the options of reporting out bibs that contain 880 fields but no corresponding 066 fields, reporting out malformed 948 fields, and/or reporting invalid subfields within a bib record.
a. Clean Up a Local MARC File: This job can take a .mrc file from a staff member’s LS Tools/Marc folder and clean up whatever issues are chosen from the set menu of common problems.
b. Clean Up Voyager BIB Data: This job can take a set of Voyager BIB records and clean up whatever issues are chosen from the set menu of common problems.
c. Report on a Local MARC File: Creates a report of any and all of three specific errors found in a .mrc file from a staff member’s LS Tools/Marc folder.
d. Report Voyager BIB Data: Creates a report of any and all of three specific errors found in a set of Voyager BIB records.
II. LS Tools Configuration
The jobs in this section are used by administrators to edit existing LS Tools jobs’ defaults, add new users, edit permission levels for various jobs, etc.
...
g. LS Tools Usage Analysis
...
CLAMSS Shelf List Tool
This tool allows catalogers to determine the proper accession number for videos and microforms. Access is given only to those individual catalogers who need to use it.
...