I am attempting to map holding information for serials into their parent
bibliographic records. The system we are using provides for a function that
will map the information as a process (to run nightly) where changes have
been made - and then out to OCLC for updating via S/FTP. The mapping table
was created by our system vendor and has defined targets of the 852 tag
field with subfields a, b, and c. This confuses me because the extent of
our holdings is reported in 866 tag fields. Isn't that the information I
would want mapped to the bib record if we are trying to reveal holdings to
the item level? A problem I can foresee is records where multiple 866 tag
fields have copious information (done many years ago), which would render
the bib record ...crazy long.... (?)

Any input (even if you tell me we shouldn't have all of those 866 fields!)
is appreciated.

Best regards,
Jennifer

Jennifer Sauer
Electronic Resources Management Librarian
Fort Hays State University
Forsyth Library
600 Park
Hays, KS 67601

Voice: (785)628-5262
Fax:(785)628-5415

***********************************************
* You are subscribed to the SERIALST listserv (Serials in Libraries discussion forum)
* To post a message to the list address: SERIALST@LIST.UVM.EDU
* For additional information, see  the SERIALST Scope, Purpose and Usage Guidelines <http://www.uvm.edu/~bmaclenn/serialst.html>
***********************************************