Versions Compared

Key

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

...

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

...

A. Withdrawals

I. Instance 

  1. Display Instance record. Verify that record matches book. If the title is marked "lost" or "missing", see special instructions below. 
  2. If the title is a serial, check for and report an open purchase order or ongoing subscription.
  3. For single-part monographs Click Actions→Edit Instance, and make the following changes in the Administrative Data section:
    • Check the "Suppress from Discovery" box
    • Check the "Staff Suppress" box
    • Add an Administrative note with the proper coding for the withdrawal, using the format date:yyyymmdd ttype:w userid:[netid] ploc:lts    The macro for this is ,,w.
      • For multipart items, record the number of pieces withdrawn by adding "pcs: " to the end of the note, followed by the number of pieces withdrawn (see example below)
      • If you are NOT withdrawing ALL of the pieces of a particular multi-volume, DO NOT suppress the instance record, or the remaining volumes will not be discoverable.

Examples (single-part and complete multivolume sets): 

(For single-part monographs):

(For withdrawing 3 volumes of a multivol:

II. Holdings record

 1. Display the appropriate Holdings record for the piece in hand:

    • For single-part monographs being withdrawn, check the box to SUPPRESS FROM DISCOVERY.  For Multi-part monographs and serials, see instructions below, suppress ONLY if withdrawing all of the pieces in a given Holdings.

2.  In the Holdings Notes, with Note Type: Note, enter "WITHDRAWN", and a short parenthetical note stating the reason, if available (e.g. lost, damaged, deselected, etc.), plus the date and your netID:

...

  •   When withdrawing only certain parts of a multipart monograph or serial, add specific information in the "WITHDRAWN" Holdings note on which parts are being withdrawn, and why.
    • Example: "v.2 and v.6 withdrawn (damaged) 01/02/03 abc"

Make sure NOT to suppress the Instance and Holdings records if any of the other volumes are still left in the collectionassociated with this Holdings.

3. If the part(s) being withdrawn are accompanying material that is included in the bibliographic description for the title (such as supplements or maps in a pocket), add a note specifying that the supplement/map/etc. has been withdrawn –   

    • Example:  "Vol. 3 and accompanying maps WITHDRAWN (MISSING) 9/3/21"

4.  If you are withdrawing only certain parts or supplements from the Holdings, Edit the appropriate Holdings Statement(s) to reflect ONLY those holdings that are retained.  If you are withdrawing all parts of a multipart monograph or serial, however, retain the Holdings Statement information as is. 

...

  1. Display relevant item record(s):
    • For single-part monographs, delete the Item record by clicking Actions→Delete.  If the Item cannot be deleted because of dependencies or certain Item Statuses in FOLIO, bring the piece to the DBQ, Inputting, or Monographs Workflow supervisor or other appropriate staff to Check-in the piece before withdrawaland remove the dependencies as applicable.

    • For multipart monographs and serials, note item Enum/Chron information for the withdrawal note, make sure the Item status lack any dependencies, and delete the Item records as described above.

...

  • Place print serials in the recycle bin.
  • Send all items that with a "Federal Publications" sticker, or "Depository" stamp, or have a "D" penciled on the cover, title page, or other preliminary pages, to the LTS Documents supervisor.
  • Place all other items on the "Withdrawn Items" items cart in 110, to be sent to the Annex for donation.      

  • Anchor
    B
    B
    B. Batch Withdrawals: Single Monographic Volume or Complete Serial collections


    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. 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.

    AnchorCC


...

C. Transfers 

I. Initial Conditions

If the transfer involves a title for "rmc,anx" or one of the "ranx" sublocations, follow the Rare Annex (12a) instructions below.

...

  1.  Display the Instance Record and enter an Administrative note for Postcataloging maintenance Transfers (,,mct). 
  2.  Display the Holdings record that matches the old location and copy number of the title and edition in hand.
  3.  Verify that the record is NOT suppressed from public view. If it is suppressed, uncheck the Suppress from Discovery box.
  4.  Change  Change the Permanent Location field to the new location.  
  5.  If needed, add a copy number in the Holdings record and Item records.
  6.  Check the Oversize Chart for prefixes and/or suffixes appropriate for the new location.
  7. In the Holdings Record, add a note (Note type: Note) showing which collection the piece originally came from, and when it was transferred.  Make sure the "Staff only" box is checked:

Image Removed

Image Added

Exception: Transfers to the Annex do NOT require a transfer note, as large transfer projects and book-moves make it cumbersome to add notes to every Holdings record, but LTS staff are still encouraged to add transfer notes for single, manual transfers whenever possible.Exception: Transfers to Annex do NOT require a transfer note

7.  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 in the Holdings and on the piece in hand, or work letter only if call number already contains a date. 

Make sure to re-mark and re-label the piece if you make these modifications modifications.

8.  Save and close the Holdings record.

...

  • Display Holdings record.
  • If the Holdings record in suppressed, make sure to un-check the Suppress From Discovery box so that it displays in the public catalog. In the Holdings Notes section, remove the "WITHDRAWN [date/initials]" note, if present.
  • Add "REINSTATED [date]" to the Holdings Notes field (Note type: Note) adding a netID is optional:

Image RemovedImage Added 

  • **Make sure the call number on the label matches the call number written in the book, and that BOTH of them match the Holdings FOLIO call number: Reinstatements are most often the result of there being a mis-match in the call number, resulting in the item having been "withdrawn/lost" because it was misplaced in the stacks.

Save the Holdings record.

Display item record[s]. If no item record is found, create item record[s] and barcode book[s].

...