Summary: | Checking out an item that to stats patron that is already checked out results in 2 entries in the stats table | ||
---|---|---|---|
Product: | Koha | Reporter: | Lucas Gass (lukeg) <lucas> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | andrew, bwsdonna, emily.lamancusa, esther.melander, gmcharlt, kyle.m.hall |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Lucas Gass (lukeg)
2024-01-22 18:43:43 UTC
To me, use of a statistical patron implies that one is fairly certain that a local use should be recorded, so we should record both a local use and a return if an item is scanned to a statistical patron while previously checked out to another patron. (In reply to Andrew Fuerste-Henry from comment #1) > To me, use of a statistical patron implies that one is fairly certain that a > local use should be recorded, so we should record both a local use and a > return if an item is scanned to a statistical patron while previously > checked out to another patron. Andrew, thanks! I think we can just call this one RESOLVED INVALID. |