...
- Selectors have access to the “Harvest Voyager Records” tool for their own edification. They may or may not have access to other parts of LS Tools, depending upon their other work duties.
- Catalogers working with videos and microforms have access to the “CLAMSS Shelflist Tool.” They may or may not have access to other parts of LS Tools, depending upon their other work duties.
...
Basic Access Group
General Update
Voyager Harvest
CLAMMS
Advanced Access Group
Voyager Update Utilities
Voyager Reporting Utilities
Batch Processing/Heads/Expert-Level Access Group
ALL LS Tools Production
Administer LS Tools Itself
...
Basic Access Group
I. “General Update” Section of LS Tools
A. Move LTS or Law EDI File to Voyager Folder (CGI08 for LTS, CGI09 for Law*): For EDI invoices download and ftp placement in the Voyager\EDI\Incoming folder for the Acquisitions client to load. After selecting the button for either Law or LTS, the specific job selected will connect to the vendor’s ftp server’s invoice folder and allow automatic placement of the file into the production server. For all of the below, In LS Tools under "EDI Import (LTS or LAW)/[vendor name]."
...
j. Nardecchia (remote)
k. Yankee (remote)
B. Check for/Remove Carriage Returns (CGI19): Can check for or remove carriage returns in MARC, harvest jobs, modification jobs, or non-MARC output lists.
C. MARC Modification Job (CGI12): Add, modify, or delete fields in a set of MARC records. Certain common additions are available under the “Special” button.
D. ENACT Bulk Import (CGI15): Takes a MARC file that has been queued for bulk import and loads the file into Voyager.
E. Prepare a Vendor e-Book Load: Loads electronic record sets supplied by vendor. Modifies the records per script prior to the load.
...
d. Books 24x7 (Not in LS Tools): Vendor record load, run from a "mod job" in staff member's LS Tools folder. Records are retrieved via FTP.
e. DDA Proquest Ebooks (VEL09): Loads ebook records from vendor. Records are retrieved via FTP.
...
v. Westlaw Record Load (VEL07): Prepares a file of Westlaw e-resources. Job is similar to the HeinOnline load.
F. Prepare a Vendor Print Load: Acquisitions bulk import of vendor supplied MARC records with or without purchase order creation via embedded order data. Selection of this button in LS Tools gives a choice of various pre-scripted jobs connecting to a folder on the vendor’s website or locally on a server.
...
II. “Voyager Harvest” Section of LS Tools
A. MARC File Examination (CGI17): Can reorder MARC fields in a file based on rules from cataloging, display a MARC file in the browser, or convert a MARC file to MARCxml.
B. View Harvest Output (CGI18): Can examine a list of bib or holdings ids.
C. Develop a Harvest query to identify Voyager Records (CGI11): Develop queries for the extraction of bibs or holdings based on specific field criteria.
D. Extract MARC Records from Voyager (CGI13): Extracts MARC Records from Voyager using a list of BIB or MFHD id's.
...
III. “CLAMSS subsystem” (CGI28): Also known as the Automated Media Shelflisting System, 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.
Advanced Access Group
I. “Voyager Update Utilities” Section of LS Tools
A. Prepare a Miscellaneous MARC Input File: Specialized loads that require additional expertise on the part of the staff member to run.
...
n. Update Backlog Books (PR322): Finds “in process” records for desired storage code in Voyager, searches OCLC by ISBN for a better record, merges with Voyager record, and queues for loading into Voyager.
C. Queue BulkImport (CGI34): Allows selection of bulk import profile to load records into production or test version of Voyager.
D. Run a Voyager Utility Program Program (VOY01, VOY02, VOY03): Used after loading authority record files to perform global headings jobs 11 and 12, which index bib and authority headings in global headings queue for authority maintenance.
...
Location for scripts that create reports or extract records as part of routine database maintenance processes.
A. Execute a Report or Extract
a. MFHD Copy Number Clean-up (PR101): 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.
...
d. Report Duplicate Government Documents (PR110): Extracts a list of government document Voyager bibs where the OCLC number and 245 subfield a match.
B. Match BibIDs from external list: Bibs matching standard numbers (PR106)
C. Other reports/extracts, which are NOT in LS Tools
a. OCLC LHR Exception Reports (Not in LS Tools): 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.)
b. OCLC Unresolved Records (Not in LS Tools): 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.
Batch Processing/Heads/Expert-Level Access Group
I. “ALL LS Tools Production” Section of LS Tools
A. Business Analysis Web Displays
a. ITSO/POOF Analysis (CGI21): Analyzes the orders placed through POOF; looks at the number of instances of a rule's use.
...
d.Batch Business Analysis (CGI29)
B. Cron Jobs for Interaction with OCLC
a. OCLC System Number Mapping (CRN05): Better known as OCLC mapping job, as it adds the OCLC number to new cataloging from OCLC cross reference reports.
...
i. OCLC WorldShare Update (PR335): Takes WorldShare records from OCLC ftp, searches Voyager for matching records, merges where incoming record is fuller than existing.
C. Execute a Google Utility: 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.
...
h. Update oai.library.cornell.edu/ (GGL24)
D. Cron Jobs with General Access
a. Report of bibs with duplicate ISBNs (CRN03): Reports out bibs with duplicate ISBNs based on the previous days 005 date.
...
j. Daily Annex Flip and Location Report: Identifies bound-with's so they can be flipped, and empty item records are created. This cron job is part of Voyager Utilities and runs every weekday.
E. Cron Jobs with Privileged Access
a. EDI Export from Voyager Server (CRN13): Sends EDI orders to vendors.
...
II. “Administer LS Tools Itself” Section of LS Tools
A. Report/Clean Up Voyager MARC Record Errors
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.
...
d. Report on a local MARC file (CLN12): 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.
B. Configure LS Tools Tables & Directories
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.
...