May 2015 - Koha-bugs - lists.koha-community.org

[Bug 11708] New: Display all basketgroups on one page, and new column aqbasketgroups.closeddate
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '15

03 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11708 Bug ID: 11708 Summary: Display all basketgroups on one page, and new column aqbasketgroups.closeddate Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 137

[Bug 13666] New: Allow SIP2 checkin/checkout to get branch from institution_id field AO
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '15

03 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13666 Bug ID: 13666 Summary: Allow SIP2 checkin/checkout to get branch from institution_id field AO Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: benjamin.rokseth(a)kul.oslo.kommune.no QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Although SIP2 specifies the required AO field to be institution_id and it doesn't neccessarily map to a branch in Koha, this is probably the case for most. Allowing for AO to set the C4::Context->userenv->{branch} transaction-time would open up for a more flexible transaction scenario: - SIP2 connections could fetch from a pool of connections, so e.g. ten SIP2 workers could easily serve hundreds of clients - SIPConfig.xml would not need reconfiguration each time a new client is added Please advise if this is in collision with other SIP2 logic in Koha -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 10554] New: Add more options to 'AllowSelfCheckReturns' syspref
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '15

03 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10554 Bug ID: 10554 Summary: Add more options to 'AllowSelfCheckReturns' syspref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com This patch modifies the options of AllowSelfCheckReturns syspref from a 2 option selection - 'allow patrons', dont allow patrons' to a 3 option selection - 'allow all patrons', 'allow non-blocked patrons' , allow no patrons' currently, a problem with the syspref behavior in Koha is that enabling the 'AllowSelfCheckReturns' syspref does *not* allow patrons with a 'block' to return items via the SCO. (this is apparently by design, and not a bug) however, some libraries do want to allow patrons to return items via the SCO even if they have a 'block' this patch adds this additional behavior, by adding a new option to the syspref, but also retaining the existing syspref behavior after the patch, there are 2 allow options - 'Allow all' allows all patrons to return items (including blocked patrons) - 'Allow non-blocked' allows only non-blocked patrons to return items (note: this is the current 'allow' behavior) the patch correctly 'upgrades' existing 'allow' selection to the new 'Allow non-blocked' value. so, any existing 'allow' selection works as before -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 12404] New: CSV profiles improvements
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '15

03 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12404 Bug ID: 12404 Summary: CSV profiles improvements Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The goal of this development is to provide a better flexibility on creating a CSV profile. Currently it is not possible to: - Concatenate specific subfields into a csv column - Display a field/subfield using a condition - Extract a substring of a subfield value and a lot of other actions. -- You are receiving this mail because: You are watching all bug changes.

1 89

[Bug 12824] New: Create a general purpose koha-config script?
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '15

02 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12824 Bug ID: 12824 Summary: Create a general purpose koha-config script? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)enger.priv.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The discussion over on bug 12805 (and specifically bug 12805, comment 5 from Viktor) got me thinking... Could we create a general purpose config editing script, at least for the <config> part of koha-conf.xml, instead of having specific scripts for lots of different config settings? If we added a (e.g.) YAML file with some metadata about the different setttings (a description, what kind of data it should contain), we could perhaps have a friendly tool that could - toggle settings off/on ("backup_db_via_tools is currently off, are you sure you want to enable it?") - offer options from a list (e.g. "dom" or "grs1" for the indexing modes) - validate the contents of fields (e.g. check that "port" gets a numeric value, or check that settings that take a path get a path that actually exists) Sample usage: Display all current settings: sudo koha-config -l <instancename> Display a specific setting: sudo koha-config <instancename> opacdir Change a specific setting: sudo koha-config <instancename> backup_db_via_tools=on (If backup_db_via_tools was already enabled, the script could say so and exit, if it was not enabled, it could verify that the user wants to change it, and make sure the value of the setting gets a 1. It could accept different input like "on", "1", "enable" etc) There could even be an interactive mode (sudo koha-config -i <instancename>) which would display something like a numbered list of current settings, let the user choose one and prompt for input, validate the input, display the changed setting etc. Of course, some config changes need more work than just changing the setting. If the user tries to e.g. enable plugins by changing the "enable_plugins" setting, the script could give a friendly warning that the user should instead use the koha-enable-plugins script. The script could perhaps take a --configfile parameter, so it could be used to edit configs for non-package-setups too. Would this just be a lot of work for little gain, or could it be a nice addition for making the threshold lower for inexperienced admins? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 9844] New: Add a barcode queue to checkout / return
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '15

02 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9844 Bug ID: 9844 Summary: Add a barcode queue to checkout / return Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: viktor.sarge(a)regionhalland.se CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Background: Some testing on a 70Mbit+ connection to a remote Koha install indicates that the system is a bottleneck when it comes to issuing checkouts or returning items. If a staff user scan barcodes to fast for the system to keep up then barcodes are lost and books will not have been checked out or returned. Plack for the staff interface might solve a part of this problem, but adding a queue would be great. Suggestion: Add a queue-box with high visibility of items that are not yet processed when checking out or returning items. If a user scans items quicker than than the system can process items the box will fill up. The system should process the barcodes in the queue-box using AJAX-code so that the whole page will not have to reload for every barcode. Ending the session (by printing receipt for checkout etc.) should not be possible until the queue is empty. Messages that today appear once per page (like holds on a title for example) will have to be duplicated since a librarian could scan multiple codes until an item has been processed by the system. Implications on existing code: I think this might require us to rewrite some of circulation.pl and returns.pl to use Ajax, insert the queue-box and to display multiple messages at once. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 11387] New: "Hold waiting too long" is untranslatable
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '15

02 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11387 Bug ID: 11387 Summary: "Hold waiting too long" is untranslatable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr In the patron's account, the Fines-tab has a table that lists all charges. In the description of charges -column, a text "Hold waiting too long" can appear. This text cannot be translated - the description is hard-coded in C4/Reserves.pm -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 11668] New: Untranslatable "Total" in borrowers stats report
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '15

02 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11668 Bug ID: 11668 Summary: Untranslatable "Total" in borrowers stats report Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr When saving borrowers_stats output into CSV, there will be hard-coded, untranslatable, "Total" and "TOTAL" texts. reports/borrowers_stats.pl: print "Total\n"; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 10627] New: history of reports run/results
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '15

02 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10627 Bug ID: 10627 Summary: history of reports run/results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org >From a library: We would like to see a list of "Finished" results of running a report (i.e., generating a list of records) or using a tool (to make changes to records or settings)? In each instance, it would be possible to go back to a list of "Finished reports", to view both the results as well as the parameters that were set to generate the list or make whatever desired change... -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 8080] New: login and password is pre-filled by the browser when creating a new patron
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '15

02 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8080 Priority: P5 - low Change sponsored?: --- Bug ID: 8080 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: login and password is pre-filled by the browser when creating a new patron Severity: enhancement Classification: Unclassified OS: All Reporter: gaetan.boisson(a)biblibre.com Hardware: All Status: NEW Version: master Component: Patrons Product: Koha When creating a new patron, if you have chosen to let your browser remember your login and password for you, the login and password fields will be pre-filled with them, leading to a systematic error "the passwords entered do not match" since the second password field was not filled. These fields should be blank. -- You are receiving this mail because: You are watching all bug changes.

1 10