Summary: | Add a barcode queue to checkout / return | ||
---|---|---|---|
Product: | Koha | Reporter: | Viktor Sarge <viktor.sarge> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | gmcharlt, jonathan.druart, josef.moravec, katrin.fischer, kyle.m.hall, magnus |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10240 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11703 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11759 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Viktor Sarge
2013-03-19 13:56:04 UTC
According to Jared, this *might* be solved by his work on Bug 10240. Thanks for the input. I've read up on 10240 and while it is a good patch I feel that the two are a bit apart even if 10240 might be a useful start to work with the functionality described here. I guess it would go something like this: When issuing * circulation.pl lights up a static page. * scan a barcode. * barcode is stored in a cache (javascript or indexedDB) * barcode is lit up in the "barcode queue"-box. These steps can take place as many times as you like at the same time as the ones below. * the barcode that first arrived in the cache is sent to the server for processing. * when a response arrives form the server the corresponding barcode is removed from the cache and the visible "barcode queue"-box. * the correct response is displayed on circulation.pl. Multiple boxes requiring to be handled could be displayed. Before going much further with this it might be a good idea to just have a go with Plack and se if it makes the system more responsive. Not least since I have a bit of a hard time convincing people on IRC that "scan as fast as you like" is a good idea :) This bug was filed 'pre-Plack' for staff interface and before the performance improvements done since (2013). Is it still valid? (In reply to Katrin Fischer from comment #3) > This bug was filed 'pre-Plack' for staff interface and before the > performance improvements done since (2013). Is it still valid? I think it is still valid, although not as critical as before, sometimes a network lag or waiting to db lock when making backup could make circulation process a bit slower than it could be... |