[Koha-bugs] [Bug 9717] Local use recorded for holds/transfers

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9717

--- Comment #20 from Christopher Brannon <cbrannon at cdalibrary.org> ---
Because there is no way to know, when scanning an item, if it is being scanned
solely for a local use or 'browse', it makes it difficult to separate a
specific 'browse' count from other things it is doing.

In other ILS systems, I've seen a completely separate task button for counting
browses.

The problem with an all in one scan is, how does it know when something is only
to be scanned as a browse, how does it know it is completing something else, or
how does it know it should do both?

If we had a preference to provide an isolated scan for browses, we could allow
libraries to continue what they do with regular scanning elsewhere.  Localuse
would function just as it always does.  But having the 'browse' feature on, it
could provide another function on the top scan bar, and scanning items there
could increment a totally new 'browse' counter - a new field in the item
record.  And it would do everything else that Koha already does if needed -
process a return, trigger holds or transfers, mark items found, record a local
use, etc.  But the needed and specific 'browse' would be counted only if using
that tab on the top input bar.  It would be a purposeful scan to indicate
something specific about that item, and not just an arbitrary count that could
have been for any number of things other than a browsed item.

Thoughts?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.