Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  •         WITHDRAWN (LOST), 8/21/00 abc
  •         WITHDRAWN (DESELECTED), 8/6/00 abc
  •         WITHDRAWN (REPLACED BY PRESERVATION PHOTOCOPY), 9/24/00 abc
  •         Vol. 3 WITHDRAWN (MISSING), 7/21/00 abc
  •         Suppl. WITHDRAWN (DESELECTED), 8/18/00 abc $z Lacks suppl.
  •         Vol. 8-15 WITHDRAWN (REPLACED BY PRES. PHOTOCOPY), 9/28/00 abc  


    Anchor
    B
    B
    B. Batch Single Volume Monographic Withdrawals

  • AS OF 9/10/21, THIS SECTION PENDING REVISION: Batch Withdrawal Process has not yet been developed for FOLIO.

     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.

    1. We import the text file or Excel spreadsheet into Microsoft Access.
    2. 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)
    3. Once verified that the data is as expected, we delete the item records using a Perl script or Gary Strawn's Location Changer.
    4. 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
    5. We used Gary Strawn's Record Reloader or a Perl script to replace the holdings with the revised versions.
    6. 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
    7. We use Voyager's bulk import function to replace the bib using the bulk import code BIBMAINT.
    8. If it is the last copy for CUL, then we suppress those bibs using the bulk import code BIBSUP.
    9. We then rerun the Access query to verify that holdings are suppressed and the items deleted.


...

  • Anchor
    C
    C
    C. Transfers
     
  • AS OF 9/10/21, THIS SECTION PENDING REVISION
  1. Transfer the item(s) online according to the instructions found in section "6. Disposition" of the " Selection Policy for Shelf Space Adjustment.  
  2. If the transfer involves a title for "rmc,anx" or one of the "ranx" sublocations, follow the Rare Annex (12a) instructions below.
  3. If the transfer involves superseded editions or volumes, see also Special Instructions below.
  4. If the title is a serial, check for and report an open purchase order. 
  5. If the title bears a "Pamphlet" call number, send it to the Library Annex.
  6. Process the physical piece(s) as follows (except for Rare Annex material)      
  • a. Single Part Item and Complete Multipart Item Transfers 
  • 1.  Display the holdings record that matches the old location and copy number of the title and edition in hand.
  • 2.  Verify that the record is not suppressed from public view. If it is suppressed, uncheck the Suppress from Discovery box.
  • 3.  Change the Permanent Location field to the new location   (Note: there is no need to change the MFHD Holdings location if you are transferring material to the Library Annex, where locations are flipped programmatically after the material is accessioned).
  • 4.  If needed, add a copy number in the Holdings record. 
  • 5.  Check the Oversize Chart for prefixes and/or suffixes appropriate for the new location.
  • 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.                                                                                                                               
  • 7.  Add an appropriate $x transfer note following the call number.
  • 8.  Save the record to the database.
  • Transfers to Annex do NOT require a transfer note
  • b. Partial Multipart Item Transfers  

...