March 2017 - Koha-bugs - lists.koha-community.org

[Bug 14608] HEA : add possibility of sharing usage statistics in Administration page and Web installer
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '17

27 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14608 --- Comment #58 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Katrin Fischer from comment #57) > This won't get ported back to 16.11.x as it is an enhancement. That will need to be backported into stable releases, otherwise we will have to wait too long to get enough people using it. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14399] "missingitem" code from inventory.pl doesn't work properly
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '17

27 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14399 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12913] wrong inventory results when notforloan filter is not used
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '17

27 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12913 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '17

27 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 Johan Larsson <johan.larsson(a)ub.gu.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johan.larsson(a)ub.gu.se --- Comment #53 from Johan Larsson <johan.larsson(a)ub.gu.se> --- corrected spelling error in commit message. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '17

27 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 Johan Larsson <johan.larsson(a)ub.gu.se> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #61065|0 |1 is obsolete| | --- Comment #52 from Johan Larsson <johan.larsson(a)ub.gu.se> --- Created attachment 61641 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=61641&action=ed… Bug 14957 - Rule based permission for MARC fields Add a rule based permission system for MARC field modifications. Test plan: 1. Apply this patch 2. Run updatedatabase.pl 3. Log in to staff client 4. Enable new syspref MARCPermissions 5. You should see a new link "MARC field permissions" in the "Catalog" section under "Koha administration". 6. Go to the "MARC field permissions" page 7. Next to the page heading ("Manage MARC field permissions") there is a button with a question mark, click this for more information about the rule system. 8. Add desired rules to the rule table, press the +-button to add. 9. Clicking the pen-icon (edit) should allow you to edit corresponding rule. 10. Clicking the x-icon should remove corresponding rule after confirmation. 11. Selecting one or more rules followed by clicking the trash-icon should remove all selected rules after confirmation. 12. To test your rules, import or in other way modify a record. 13. Check that the record was modified as defined by your rules. Sponsored-by: Halland County Library -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15690] New: Unconstrained CardnumberLength preference conflicts with table column limit of 16
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '17

27 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15690 Bug ID: 15690 Summary: Unconstrained CardnumberLength preference conflicts with table column limit of 16 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org We offer the ability to define any minimum or maximum card number length, but the table column is limited to 16. At the very least the preference should be constrained to 16, but I think a better solution would be to increase the limit on borrowers.cardnumber /and/ require that the CardnumberLength preference respect it. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 12021] SIP2 checkin should alert on transfer and use CT for return branch
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '17

27 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12021 Benjamin Rokseth <benjamin.rokseth(a)kul.oslo.kommune.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #61200|0 |1 is obsolete| | --- Comment #16 from Benjamin Rokseth <benjamin.rokseth(a)kul.oslo.kommune.no> --- Created attachment 61640 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=61640&action=ed… Bug 12021 - SIP2 checkin should alert on transfer and use CT for return branch This small patch corrects the SIP2 checkin response if branch transfer is needed. It depends on bug 7981 and also removes an obsolete alert check in SIP2. Test plan: - apply bug 7981 - make sure syspref AutomaticItemReturn is false - check 'Return policy' in 'Default checkout, hold and return policy' - make a SIP2 checkout and checkin from a branch different than item's home branch. - verify that SIP2 response gives alert CV04 (=send to different branch) - also verify that response field CT gives correct branch according to 'Return policy' Signed-off-by: Kyle M Hall <kyle(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11889] Disown a list
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '17

27 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11889 --- Comment #36 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- +1 for moving shared lists and transfer to another bug report. We could use the Anonymous patron - not sure if that would make sense. Otherwise for me that sounds fine - my only worries are only about the shared ones. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11889] Disown a list
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '17

27 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11889 --- Comment #35 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #34) > For the public/shared with public, I think the idea of > having a general inheriting user is fine. If we would have consensus about that, we could perhaps apply the following algorithm to public lists now ? Would this provide sufficient flexibility? When deleting a public list, if pref GeneralPublicListOwner[?] is a specific userid then move ownership to that user elsif pref == current user then move to current staff member else delete list endif And open another report to handle shared lists. And another one for transferring ownership? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11889] Disown a list
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '17

27 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11889 --- Comment #34 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think there is a different understanding in shared and shared with public - shared means shared with selected other users by invitation. For those privacy applies. For the public/shared with public, I think the idea of having a general inheriting user is fine. -- You are receiving this mail because: You are watching all bug changes.

1 0