Batch Updating of Local Data Records

1
Batch Updating of Local Data Records

• FEDLINK OCLC Users Group Meeting
• November 1, 2002

2
Batch Updating of Local Data Records (formerly
LDRUS)

• Batchload process for serials holdings data which
• is compliant with the MARC 21 Format for Holdings
  Data (MFHD)
• OR
• is not MFHD-compliant, but does meet OCLC
  requirements for patterned data

3
Batch Updating of Local Data Records (formerly
LDRUS)

• Examples of patterned data
• Labeled data field descriptions immediately
  precede their content (e.g. LOCATION Main) or
  labeled columns of data in a spreadsheet
• Delimited data fields and records are separated
  by a unique identifiable character or series of
  characters (e.g. tab-delimited files)
• Positional data field descriptions and their
  content are related by record position (e.g.
  fixed- length formatted records)

4
Batch Updating of Local Data Records (formerly
LDRUS)

• All holdings records, regardless of format, must
  include the OCLC control number of the
  bibliographic record to which they are attached.
  
• The institution must be able to supply all
  holdings records associated with a specific
  bibliographic record.
• There must be only one holdings record per copy.
• The institution must participate in an OCLC Union
  List or Group Access/Union List group.

5
Batch Updating of Local Data Records (formerly
LDRUS)

• The requirement that holdings be set on the title
  prior to LDR batchload processing was eliminated
  in Sept 2002.
• Holdings are now set automatically during batch
  updating of LDRs just as in online manual union
  list data entry.

6
Batch Updating of Local Data Records Product
Codes/Pricing

• Batchload Evaluation Fee
• Fee waived through June 2003 for data compliant
  with MFHD requirements
• Fee charged for evaluating non-MFHD files and any
  necessary custom programming

7
Batch Updating of LDRs How to order submit
data

• To sign up for Batch Updating of LDRs, a library
  submits a Batchload Order Form https//www3.oclc.o
  rg/app/batchload_order/index.pl
• and an initial file of data.
• Data can be submitted via EDX, tape, or diskette.
  
• Libraries should complete an EDX Assessment Form
  https//www3.oclc.org/app/edx_assessment/
• if they plan to submit files electronically and
  do not already have an OCLC EDX account.

8
Web Links LDR Batch Updating

• Batch Updating of Local Data Records
• http//www.oclc.org/batchprocessing/localdatarecor
  ds/
• General Guidelines
• http//www.oclc.org/batchprocessing/localdatarecor
  ds/guidelines.shtm
• Specifications
• http//www.oclc.org/batchprocessing/localdatarecor
  ds/specifications.shtm
• Planning Guide
• http//www.oclc.org/oclc/union/ldrus.pdf

9
Union Listing Enhanced Visibility

• Interlibrary Loan Lender LDR
• Local Data Record information will be added to
  ILL pending requests in the Call Number field
  (for monographs and serials)
• Allows lenders to quickly identify requests that
  can be immediately declined
• Expect to install this enhancement before the end
  of 2002

10
(No Transcript)
11
(No Transcript)
12
Union Listing Enhanced Visibility

• Interlibrary Loan Lender LDR
• When the request is forwarded to the next lender
  in the string, the holdings shown will be that
  lenders LDR
• LDR info for each lender will be added to the
  Request History
• If the lender does not have LDR info available,
  the field will be left blank

13
Questions?