Page History

...

*As of 9/1/21, this procedure is in the process of being updated for the FOLIO-based environment. 

...

Withdrawals
Batch Single Volume Monographic Withdrawals
Transfers
Reinstatements
Medium Rare Annex
Additional Steps : Special Cases 

...

•         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 For batch withdrawals of single volume monographs we receive either , a text file barcodes or an Excel spreadsheet of the single volume monographs of barcodes of records to be withdrawn . Basically we then follow the online work of withdrawal procedure as noted above using batch tools.
  are sent to the batch processing team, (currently Peter DelaCuadra). Batch processing will only perform the batch withdrawal process if the count is greater than 25. Less than 25 will be processed manually by DBQ staff.

  The batch withdrawal process is as follows:

  1. Text file or Excel spreadsheet is imported into DBeaver LDP.
  2. A query, (or queries), is performed
  3. We import the text file or Excel spreadsheet into Microsoft Access.
  4. 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 , any abnormalities are routed to DBQ for manual processing)
  5. Once verified that the data is verified as expected, we delete the item records using a Perl script or Gary Strawn's Location Changer.are deleted by means of a Perl or Python script. (as of this writing, 9|17|2021, script is in process of development)
  6. Holdings are then harvested from Folio. MARCEdit will be used to edit the previously harvested holdings We use Harvest to pull the MFHDs and use MARCEdit to follow the manual withdrawal steps for holdings described above. (Leader Change LDR position 5 changed to "d" and an 852 subfield x note add staff note in Holdings Note section "Withdrawn ([reason for withdrawal] date, net id)". For examapleexample: Withdrawn (lost/missing) 3/12/20, gcb2  –   pd36 or Withdrawn (dupe-deselected) 3/12/20, gcb2
     
  7. We used Gary Strawn's Record Reloader or a Perl script to replace the holdings with the revised versions.
  8. pd36.
  9. The corresponding bibliographic MARC bibs are harvested from Folio as well. A 948 batch withdrawal statistic is added into the MARC record. 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
  10. We use Voyager's bulk import function to replace the bib using the bulk import code BIBMAINT.
  11. If it is the last copy for CUL, then we suppress those bibs using the bulk import code BIBSUP.
  12. The MARC bibliographic records are re-imported back into Folio using Data Import with the correct import profile. (as of this writing, 9|17|2021, an import profile has not been written yet).
      
  13. If the holdings being withdrawn is the last CUL copy, the MARC bibliographic record will need to be suppressed.
  14. The corrected holdings records are also re-imported back into Folio using Data Import with the correct import profile. (as of this writing, 9|17|2021, an import profile has not been written yet).
  15. Develop and run query in Dbeaver to verify bibliographic records of last CUL copy are suppressed and that all withdrawn 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

...