Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Knowledge Articles
    4. Suppressed bibs on expired course reserve lists extracted when set to Off Reserve

    Suppressed bibs on expired course reserve lists extracted when set to Off Reserve

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Symptoms
    2. Defect Status
    3. Replication Steps
    4. Workaround
    • Product: Voyager
    • Product Version: 9.2.1, 10.0.0
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

    Symptoms

    Course Reserve list expired and item still appearing in Primo

    Defect Status

    Issue VYG-7259 is currently in Development

    Replication Steps

    1. Find or create a reserve list with suppressed items set to On Reserve and an End Date in the past.
    2. Set one of the suppressed items to Off Reserve. The item should be extracted with "deleted" in the header to remove it from reserves in Primo.
    3. The item is extracted but "deleted" is not included in the header status, so it updates or adds the item in Primo.

    Workaround

    Items are deleted from Primo as expected when the list expires. If item is set to Off Reserve after this happens, it's extracted again without the deleted header status and ends up back in Primo. To work around this:

     

    Option 1: Set the item to Off Reserve one day prior to the expiration of the reserve list. The reserve list expiration will extract the items for deletion from Primo.

    Option 2: Temporarily unsuppress bibs, run Primo extract, then suppress bibs and run extract again to trigger deleted header status. (or, see How to delete a specific record from Primo?)

    For a large set of records, Option 2 can be executed using Global Data Change: GDC: Suppress / Unsuppress Records

    1. Create record set with list of bib_ids to be deleted from Primo.
    2. Create Data Change Rule Set with Unsuppress consequence.
    3. Add Data Change Rule Set to Data Change Rule Set Group.
    4. Run Data Change Job to unsuppress records.
    5. Run Primo Extract.
    6. Change consequence to Suppress, or duplicate the rule and set the new rule to Suppress consequence.
    7. Run Data Change Job to suppress records again.
    8. Next run of Primo Extract will extract records with "deleted" header status.

    • Article last edited: 09-Oct-2017
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Suppress heading type from browse results
      • Suppressed MFHDs unsuppressed when Holdings Location changed by Pick and Scan
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      1. voy-unresolved
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved