September 2016 - Koha-bugs - lists.koha-community.org

[Bug 14695] Add ability to place multiple item holds on a given record per patron
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '16

21 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14695 --- Comment #228 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- This also breaks the option to enforce item holds! Example: - on shelf holds allowed - holds allowed 5 - holds on same record allowed 5 - FORCE item level holds On a record with only one item, you can only place a record level hold in OPAC now - which is against your circulation conditions. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14695] Add ability to place multiple item holds on a given record per patron
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '16

21 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14695 --- Comment #227 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- If this is an intended behaviour change - I am not in favor of it and it's unusual to push things in like this without discussion. I think we should not force staff to do a record level hold if they really want to do an item level hold. For the OPAC, this might be debatable. Also: I didn't have any other hold on that record when encountering this. One scenario I can imagine for staff: Put a hold on the damaged item, that is still out to the user, while waiting for the already ordered new item (assuming th library is using AcqCreateItem with 'on receive' or 'cataloguing') -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14764] Add OPAC News branch selector
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '16

21 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14764 --- Comment #21 from Liz Rea <liz(a)catalyst.net.nz> --- Slight typo in the test plan - there is no "change library" button, it submits on change when you select a library. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14764] Add OPAC News branch selector
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '16

21 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14764 Liz Rea <liz(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #55682|0 |1 is obsolete| | --- Comment #20 from Liz Rea <liz(a)catalyst.net.nz> --- Created attachment 55726 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=55726&action=ed… Bug 14764: OPAC news selector - Template tags Test plan: 1) Add more than one library, at least two in total is needed. Make note of which is your current user's home branch. 2) Go to Tools -> News and add one global ("All") news item and one specific for each branch. 3) Apply the patches. 4) Perform database upgrades when you log in. 5) Go to OPAC main, it should work as before: Showing global news as well as the news for your home branch once logged in. 6) Go to System Preferences -> OPAC and set 'OPACNewsBranchSelect' to yes. 7) Go to OPAC main, you should see the global news item plus any items for your home branch for the current user if logged in. 8) Above the news, you will see a dropdown that lists the branches. Select one, and click "Change library." 9) You should now see global news and the news for the selected branch, regardless of whether logged in or not. Sponsored-By: Halland County Library -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14764] Add OPAC News branch selector
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '16

21 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14764 Liz Rea <liz(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #55681|0 |1 is obsolete| | --- Comment #19 from Liz Rea <liz(a)catalyst.net.nz> --- Created attachment 55725 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=55725&action=ed… Bug 14764: OPAC news selector - Atomic update SQL Adds an SQL file to perform the database upgrade. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14764] Add OPAC News branch selector
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '16

21 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14764 Liz Rea <liz(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #55680|0 |1 is obsolete| | --- Comment #18 from Liz Rea <liz(a)catalyst.net.nz> --- Created attachment 55724 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=55724&action=ed… Bug 14764: OPAC news selector - Add syspref Adds the new system preference to the pref and SQL files. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9188] Remove 'debug' information from patron statistics
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '16

20 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9188 Andreas Roussos <arouss1980(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |In Discussion --- Comment #5 from Andreas Roussos <arouss1980(a)gmail.com> --- (In reply to Katrin Fischer from comment #4) > Checking the other statistical reports I notice that they all show a > 'Filtered on' - maybe instead of hiding this totally, we should try to clean > up the bits that are not easy to understand? Or should we try and clean up > the other reports too? > > What do you think? Well, the "Query =" bits are probably the ones that can confuse a non-tech savvy user the most and IMHO should not be displayed at all. As for the "Filtered on:" info, I think it clutters the display i.e. you have asked for a report, so you should get a report (and just that), not a repeat of what filters you chose when designing the report. Besides, when outputting to a file, you never get to see this "debug" info which (again, IMHO) is yet another reason to not display it at all unless a flag is set. Perhaps we've missed something, though. Usually when more people express their views a better decision can be made, so I was wondering if this bug is worth adding to the agenda of the next dev meeting on 28/09? May I also suggest changing the bug title to "Remove 'debug' information from report results" or something similar to reflect its wider scope? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14695] Add ability to place multiple item holds on a given record per patron
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '16

20 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14695 --- Comment #226 from Benjamin Daeuber <bdaeuber(a)cityoffargo.com> --- (In reply to Katrin Fischer from comment #222) > It's impossible for me to place an item level hold on a record with one item > in staff. The message shown is: Hold must be record level > The max holds per record is set to 1. This is just after updating to latest > master without any changes to configuration. Item level holds are allowed. Just brainstorming on this, but we wouldn't want to be in a position where a user accidentally placed an item level hold and a new copy comes in that goes on the shelf instead of to the user. If there is one item on a record chances are it's a hold that should be filled at the record level. But it's not guaranteed. I think the best way to fix this problem is to eventually allow item level holds to be filled by identical items (say we get a second issue of a serial or another set of dvds) rather than forcing a record level hold. Still, I'm happy with this as a first step. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14695] Add ability to place multiple item holds on a given record per patron
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '16

20 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14695 --- Comment #225 from Benjamin Rokseth <benjamin.rokseth(a)kul.oslo.kommune.no> --- Seems the behaviour is intentional: method forced_hold_level is implemented in Koha/Holds.pm and used in reserve/request.pl by this patch set, and is also commented: Koha/Holds.pm: >If a patron has multiple holds for a single record, >those holds must be either all record level holds, >or they must all be item level holds. > >This method should be used with Hold sets where all >Hold objects share the same patron and record. > >This method will return 'item' if the patron has >at least one item level hold. It will return 'record' >if the patron has holds but none are item level, >Finally, if the patron has no holds, it will return >undef which indicateds the patron may select either >record or item level holds, barring any other rules >that would prevent one or the other. but I'm not sure of the implementation since it seems to favour 'record' in any other case than existing item level hold? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14544] Move the list related code to Koha::Virtualshelves
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '16

20 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14544 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |17316 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17316 [Bug 17316] Possible to see name of lists you don't own -- You are receiving this mail because: You are watching all bug changes.

1 0