Page History

...

•         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 Withdrawals: Single Monographic Volume or Complete Serial collections
  
• Batch Withdrawal Process has been updated for FOLIO.
  

  
  

  For batch withdrawals of single volume monographs, a text file or Excel spreadsheet of barcodes of records to be withdrawn are sent to the batch processing team. 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 and a separate table of the barcodes is created.
  2. A query, (or queries), is performed on the newly created table of barcodes. This is to acquire specific data needed to perform the batch withdrawal process. Data The primary data necessary to complete a batch withdrawal are the instance UUIDs, holdings UUIDs and the item UUIDs.
  3. Once item UUIDs are acquired, item records are deleted by means of a Perl or Python script.
  4. Utilizing the holdings UUIDs and a Perl or Python script involving the the Folio API, all holding work will be completed. This would include adding the withdrawal note in the holdings note, the transaction data note and the suppression of the holdings. Examples of withdrawal notes: Withdrawn (lost/missing) 3/12/20, netid or Withdrawn (dupe-deselected) 3/12/20, netid.
  5. If the holdings being withdrawn is the last CUL copy, the MARC bibliographic record will need to be suppressed.
  6. The corresponding instance UUIDs for the bibliographic MARC bibs will be used when implementing a Perl or Python script utilizing the Folio API to suppress the instance, if there are no other holdings attached with circulating material. The instance will not be suppressed if there is a valid holdings attached with circulating material.
  7. Spot check a few records in Blacklight to see if modifications have taken affect.
  8. Develop and run query in Dbeaver to verify bibliographic records of last CUL copy are suppressed and that all withdrawn holdings are suppressed and the items deleted.

  Note: As of the writing, (05|16|2022), all scripts necessary to perform the aforementioned tasks in the Folio API are currently in development.
  

...