...
- Place print serials in the recycle bin at your workstation.
- Send duplicate Asia serial issues to Echols, South Asia, or Wason, as appropriate.
- Place all other items on the withdrawn monograph book truck in LTS Rm.107E.
Examples: Anchor A1 A1
852 00 ... $x WITHDRAWN (LOST), 8/21/00 abc
B. Batch Single Volume Monographic Withdrawals
852 01 ... $x WITHDRAWN (DESELECTED), 8/6/00 abc
852 00 ... $x WITHDRAWN (REPLACED BY PRES. PHOTOCOPY), 9/24/00 abc
852 01 ... $x Vol. 3 WITHDRAWN (MISSING), 7/21/00 abc
852 01 ... $x Suppl. WITHDRAWN (DESELECTED), 8/18/00 abc $z Lacks suppl.
852 01 ... $x Vol. 8-15 WITHDRAWN (REPLACED BY PRES. PHOTOCOPY), 9/28/00 abc
| Anchor | ||||
|---|---|---|---|---|
|
For batch withdrawals of single volume monographs we receive either a text file barcodes or an Excel spreadsheet of the single volume monographs to be withdrawn. Basically we then follow the online work of withdrawal procedure as noted above using batch tools.
- We import the text file or Excel spreadsheet into Microsoft Access.
- We perform a query or queries to verify that the data is as expected. (Looking for things such as unexpected multi-volume monographs, serials, items checked out, etc. We usually route those items to DBQ for manual processing)
- Once verified that the data is as expected, we delete the item records using a Perl script or Gary Strawn's Location Changer.
- We use Harvest to pull the MFHDs and use MARCEdit to follow the manual withdrawal steps for holdings described above. (Leader position 5 changed to "d" and an 852 subfield x note "Withdrawn ([reason for withdrawal] date, net id)". For examaple: Withdrawn (lost/missing) 3/12/20, gcb2 – Withdrawn (deselected) 3/12/20, gcb2
- We used Gary Strawn's Record Reloader or a Perl script to replace the holdings with the revised versions.
- We use Harvest to pull copies of the bibs and add a 948 batch withdrawal statistics.
For example: 948 2_ $a 20151212 $b w $d batch $e lts
- We use Voyager's bulk import function to replace the bib using the bulk import code BIBMAINT.
- If it is the last copy for CUL, then we suppress those bibs using the bulk import code BIBSUP.
- We then rerun the Access query to verify that holdings are suppressed and the items deleted.
...
6. Search the database to verify that the old call number is not already in use for the new location. If it is, add publication date and work letter to the call number already in use, or work letter only if call number already contains a date.
...
- Display the holdings record that matches the old location and copy number of the title and edition in hand.
- Delete the volumes and/or numbers to be transferred from the 866, 867, and/or 868 fields.
- Display the holdings record that matches the new location and copy number. If there is no holdings record for the new location, skip to "h8" below.
- Click on the system tab to verify that the record is not suppressed from the OPAC. If it is, uncheck the Suppress from OPAC box and change the record status value to 'c' in the leader area.
- Add an appropriate $x transfer note following the call number.
- Add the volumes and/or numbers to be transferred to the 866, 867, and/or 868 fields.
- Save the record to the database.
- If there is no holdings record for the new location and copy number (including ANX locations, if you are transferring items to the Library Annex), create and edit one. Be sure to:
- Check the Oversize Chart for prefixes and/or suffixes appropriate for the new location.
- Search the database to verify that the old call number is not already in use for the new location. If it is already in use, add a w suffix to the last cutter in the call number.
- Add an appropriate $x transfer note following the call number.
- Include 866, 867, and/or 868 fields
- Code for Type of Record (use v or y), Encoding Level (use 4), Receipt Status (use 0) and Completeness (use 1, 2, or 3) in the fixed fields .
- Check the Oversize Chart for prefixes and/or suffixes appropriate for the new location.
...