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. Demerits and suspensions are not showing correctly

    Demerits and suspensions are not showing correctly

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Voyager
    • Product Version: 8.1.2

    Description:
    Bug Report Form for Issue 16384-16161

    Module(s): Web services
    Server platform(s) affected: Solaris/all
    PC OS (if applicable): n/a
    Browser & version (if applicable): n/a
    Release(s): reported in 7.2.5, replicated in 8.0

    Expected results: Suspensions should be sent with their correct total.

    Actual results: Suspensions are sent with an amount of ‘Demerits: null’.

    Workflow implications: Patrons see incorrect demerit displays.

    Replication steps:
    Verify that in SysAdmin>Circ>Miscellaneous Use Demerits and Display Demerits are both checked.
    Verify that in SysAdmin>Circ>Policy Definitions>Matrix for the patron group/item type you’re working with has Demerits set to a non-zero value
    Verify that in SysAdmin>Circ>Patron Groups your patron group has Demerits Apply checked off, and Max Demerits and Suspension Days are set to non-zero values
    Go to Circulation and charge an item of the item type above to your patron of the patron group above.
    In the charge screen, right click on the row for the charge and select Modify Due Date
    Select a day before today (such that the item will be immediately overdue)
    Discharge the item – you’ll see that you now have demerits on your patron record.
    Run circjob 31
    Go back to your patron record – you’ll see that the system has listed a posting of Suspension, and subtracted the Max Demerits value from your total (potentially multiple times, if your initial Demerit level was high enough that you were suspended for multiple periods).
    If you look at the xml the services send, you’ll see something like this:

    <response>
    <reply-text>ok</reply-text>
    <reply-code>0</reply-code>
    ?
    <resource>
    ?
    <fine>
    <fineId>305</fineId>
    <fineDate>2011-09-14</fineDate>
    <itemTitle>500 hats of Bartholomew Cubbins / by Dr. Seuss.</itemTitle>
    <fineType>Demerit</fineType>
    <amount>Demerits: 50.00</amount>
    <dbKey>MAST20001DB20020910104124</dbKey>
    <dbName>Voyager Library Training Database</dbName>
    <instName>Local Database</instName>
    </fine>
    ?
    <fine>
    <fineId>305</fineId>
    <fineDate>2011-09-14</fineDate>
    <itemTitle/>
    <fineType>Suspension</fineType>
    <amount>Demerits: null</amount>
    <dbKey>MAST20001DB20020910104124</dbKey>
    <dbName>Voyager Library Training Database</dbName>
    <instName>Local Database</instName>
    </fine>
    </resource>
    </response>

    Note that while the Demerit is sent correctly, the Suspension is sent with an amount of ‘Demerits: null’.

    Resolution:
    Fixed in Voyager 8.1.2.


    • Article last edited: 3/5/2015
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Deleting item records in Voyager
      • Description and list of enhancements for new version?
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      1. 8.1.2
      2. voy-resolved-8
    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