Skip to main content
  • Subscribe by RSS
  • ExLibris Dev

    UB: Counter Reset puts bad dat in the *_UB fields of stubs

    • Article Type: General
    • Product: Voyager
    • Product Version: 7.2.5

    Bug Report Form for Issue 16384-17666

    Module(s): Universal Borrowing, Circulations
    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.1

    Expected results: Editing one patron’s counters should not affect the counters of any other patron; the UB counters should never be non-zero in a stub record.

    Actual results: If you edit the counters of a non-stub patron and that patron has a non-zero value in one of the UB counters, when you edit a stub’s counters immediately afterward, the original patrons’ UB counter values are written to the stub’s UB counters.

    Workflow implications: Some patrons may be invalidly blocked because of incorrect counters.

    Replication steps:
    In db A, find a non-stub patron.
    Click on the Counters icon and set all of their UB Counters (items borrowed, claims returned, lost items, self-shelved, and items requests) to non-zero values and hit OK.
    Go to Patron>Search for Patron and search for a stub patron in db A.
    When the patron record comes up, click on the Counters icon and hit OK without editing any data.
    Go to the Counters tab for the stub patron
    – you’ll see that the stub’s UB Counters have all been set to the values that were in the original patron record you viewed.

    Workaround: Find or create a non-stub patron that has UB counters all set to 0, then repeat the steps above – the UB counters on the stub will be reset to 0.


    • Article last edited: 10/8/2013
    // feedback widged