If your institution's holdings have not been fully maintained in WorldCat, you may have no easy way of identifying the records for which you need to cancel or set holdings. When this occurs, you can order a reclamation project. For a reclamation project: • You send all the records from your local system to OCLC to set your library’s holdings in WorldCat. • As your institution’s holdings are set, the date of this batchload transaction is “stamped” on each record. • After batch processing is complete, a Scan/Delete is performed that removes your holdings from records with a date stamp earlier than the date of the batchload transaction (typically the date when you extracted your records for submittal to OCLC). • Any holdings set after the date of the Scan/Delete are retained in WorldCat. Therefore, you can continue online cataloging while your records are processed. OCLC recommends, however, that you stop deleting holdings until the reclamation project is complete. By default, Scan/Deletes are processed to skip any holding set on a record that has a local holdings record (LHR) attached. The LHR itself will remain, and the holding will remain set on the record, regardless of date stamp. However, you can request to remove the LHR and the related holding. When you order a reclamation project, you can also request to add your records to WorldCat that do not match existing WorldCat records. A Retrospective project is a one-time load without a Scan/Delete. This type of load might for a new OCLC member that has no holdings in WorldCat, for libraries that catalog online with OCLC but never added holdings for items acquired prior to joining OCLC , or if you need to simple fill gaps in your WorldCat holdings or gaps in OCLC numbers in your local system (e.g., special collections). Ongoing batchload: Once your holdings are in sync with WorldCat, you may want to order ongoing batchload to keep them up-to-date. Use ongoing batch processing to continue setting or canceling holdings as your library collection changes. Receive OCLC control numbers in the same format as you requested for the Retro/Reclmn.
There are three options to obtain OCLC control numbers from the batch process: (click)Cross Reference (or XREF) Report (click)Your library’s records returned with the OCLC number in them (click)Full OCLC-MARC recordsI’ll explain the content of each of these in the next several slides. (click)
By default, batch processing generates a two-column text file that lists the matching OCLC numbers (without prefix and without padded zeros) across from the numbers in the 001 fields of the batchload files processed. If your local Unique Record ID is not originally in the 001 field, batch pre-processing routinely moves it to field 001 so it will be listed across from the appropriate matching OCLC number in the XREF report. We require you indicate where in the bib record you Local System control number is located, so we can map it to the 001.(The theory behind the XREF report is to use your Unique Record ID to find the appropriate record in your local system, then merge in the associated OCLC Control number. Many institutions have used the XREF successfully but some do not have the technical staff to utilize this text report. If you do not have the expertise locally you may need to work with your ILS vendor, OCLC cannot provide this level of support.The XREF report is posted for pick-up on the OCLC Product Service Web or by logging into your EDX account. You can request they be emailed if desired.
You can request we return a copy of the records submitted for batch processing, with the OCLC Control Number merged into those records.By default, the OCLC number is merged into 035 $a with the OCoLC prefix, no other changes are made to your record; If you need to have the OCLC number merged into the 001 field, with or without the ocm/ocn prefix, you can indicate this on the order form. Your file or files of records containing the merged OCLC number are available for pick-up as soon as each one completes batch processing.
A third option is getting a file of the matching OCLC MARC Records. When institution request OCLC MARC record batch services typically merges local data form the incoming record into the copy of the OCLC MARC master record returned, especially the library’s Unique Record ID needed for loading back into the local system. Other fields can also be transferred to the records, such as local notes, local call numbers and critical 9XX fields. By default, full OCLC MARC Records returned contain the OCLC control number in both the 001 and the 035. 001 prefixed by ocm or ocn035 $a prefixed by (OCoLC)Custom post-processing is available if these default locations of the OCLC number do not suite your needs. For example, an institution may prefer their unique system control numbers to be in the 001 field of the OCLC MARC record returned. Post-processing can replace the OCLC numbers in the 001 with your local system control numbers. (click)Note that, unlike the other two output options, there may be extra costs involved to produce full OCLC-MARC Records. Consult your Regional Service Provider or OCLC Library Services Representative for more information.
Use 20100225 bl webinar revised
Batch Processing OverviewFor audio please call :1-866-699-3239 Event number: 719 119 553<br />14 June 2010<br />Defining Process and Selecting Projects & Output<br />
Agenda<br />OCLC “basics”<br />Review Types of Batchload Projects (bibs)<br />Explore Options for OCLC control number return<br />Ordering Options<br />Process Workflow <br />Questions<br />
Objectives<br />Understand OCLC Holdings and Control Numbers<br />Identify the project type(s) appropriate for my library<br />Identify the best output option(s) for my library<br />Follow the basic OCLC Batchload process<br />Submit an online Batchload Order Form to OCLC<br />Access Batch Processing documentation<br />
Some OCLC “basic”<br />Holdings<br />OCLC Institution Symbol<br />OCLC Holding Library Codes (branch)<br />OCLC Control Numbers <br />
Some OCLC “basics”<br />OCLC Control Number<br />Accession Number<br />
Cross Reference Report<br /><ul><li>Two-column text file
Matches OCLC numbers to numbers in 001 of incoming files</li></ul> OCLC XREF REPORT <br /> OCLC Submitted <br /> Control # 001 Field <br /> 13385800 .b12306162 <br /> 4150423 .b12722509 <br /> 35676221 .b18265662 <br /> 472459423 .b1961309x <br /> 472459432 .b27839473 <br /> 31771726 .b29816646 <br />
Your Records w/ OCLC Numbers<br /><ul><li>OCLC number merged into 035 $a with “(OCoLC)” prefix*</li></ul>Example:<br />
Full OCLC-MARC Records*<br />* Unlike the first two output options, there may be costs associated with producing full OCLC-MARC records. <br /><ul><li>Merged local fields into copies of OCLC-MARC records
Step 1: Ordering <br />Initiate a Batchload project & obtain a Project ID, complete an order form. <br />Online Service Center (OSC)<br />or<br />“Old” (non-standard) Batchload Order form<br />
Step 1: Ordering from OSC<br />Criteria for OSC form:<br />Setting holdings single (1) OCLC institution symbol<br />Bibliographic data is MARC21 (MARC8 or UTF8 encoded)<br />Options for OCLC # in Own Record Return work for you<br />Do NOT need OCLC-MARC record return<br />
Automated workflow<br />Automated messaging: Project ID <br />Standard setup created based on order criteria<br />Project Active upon file receipt <br />Standard output options are acceptable <br />http://www.oclc.org/servicecenter<br /> http://www.oclc.org/us/en/support/documentation/batchprocessing/using/checklistfororderingBib.pdf<br />
Step 1: Ordering via “old” Batchload Order form<br />Criteria for “old” Batchload Order form:<br />Group batchload (setting multiple OCLC Institution Symbols based on library identifier within record)<br />OCLC MARC Records return <br />OCLC # format in Own Record Return not on OSC form<br />Non-MARC input data<br />
Manual Workflow<br />Project logged manually, Project ID e-mailed<br />Queued for Database Specialist Evaluation<br />Translation Table work (group)<br />OCLC MARC output: local data mapping requirements<br />Non-standard OCLC # format in Own Record Return<br />If Non-MARC, script to convert to MARC<br />https://www3.oclc.org/app/batchload/<br />
Step 2: Submitting Files to OCLC <br />Electronic Data Exchange (EDX)<br />Account created for Institution Symbol<br />Distinct User Name & Password<br />FTP <br />Larger files (up to 90,000 records each)<br />OCLC Product Services web (PS Web) <br />Web application<br />Log on with OCLC autho/password (Connexion, FirstSearch, ILL)<br />Upload in browser <br />Smaller files (fewer than 40,000 records each)<br />
Step 2: File submittal<br />DATA file (contains MARC records)<br />DATA.D091101<br />LABEL file (plain text file about the DATA file)<br />LABEL.D091101<br />DAT 20091101000000.0<br />RBF 85950<br />DSN DATA.D091101<br />ORS XYZ<br />FDI P012472<br />
File names <br />Multiple files<br />DATA.D100225.FILE1<br />DATA.D100225.FILE2<br />DATA.D100225.LAST<br />LABEL.D100225.FILE1<br />LABEL.D100225.FILE2<br />LABEL.D100225.LAST<br />One file only for a one-time project, use .LAST<br />DATA.D100303.LAST<br />LABEL.D100303.LAST<br />
Step 3: Record Matching <br />Separate matching categories: <br />(1) OCLC Number matching <br />(2 ) “Other” Unique Key matching <br />(3) Extended Matching <br />Qualifiers available for each category: <br />(1) Language of Cataloging (040 $b)<br />(2 ) Date of Publication (from Fixed Field)<br />(3) Derived Title Key (from 245, 246 & 247)<br />(4) Material Type (Book, Electronic Resource, VHS, Score, etc)<br />
Step 4: Reports and/or Records<br />Batchload Processing Summary<br />Cross Reference Report <br />MARC Record Output <br />Own Records with OCLC# merged<br />OCLC MARC Records with local fields merged<br />Other MARC record files including,<br />UNRES<br />DUPS<br />DESL<br />
Vendor Records <br />Do you have rights to redistribute?<br />If not, have you asked for permission?<br />http://www.oclc.org/us/en/worldcatlocal/support/vendor.htm<br />WCLVendorRecords@oclc.org<br />
Other processes<br />Symbol Flips<br />Branch Level Scoping (full WorldCat Local only)<br />Local Holdings Records Updating service (LHRUS)<br />Create LHRs from Bib Data (BHR processing)<br />