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

[Bug 7533] Add template_cache_dir to the koha-conf.xml file
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '17

17 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7533 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #58476|0 |1 is obsolete| | --- Comment #10 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 59091 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=59091&action=ed… Bug 7533: Add the template_cache_dir entry to koha-conf.xml And comment it, as we don't know what are the sysop's preferences Signed-off-by: Magnus Enger <magnus(a)libriotech.no> Signed-off-by: Nick Clemens <nick(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7533] Add template_cache_dir to the koha-conf.xml file
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '17

17 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7533 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12063] Change date calculation for reserve expiration to skip all holidays
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '17

17 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12063 --- Comment #30 from Koha Team Lyon 3 <koha(a)univ-lyon3.fr> --- Hurrah! We have an agreement ;-) Is it difficult to add this verification to the patch ? We can re-test it and it can pursue his way toward the "Pushed to master" status... [in aparte, I'm not totally sure that it's really understandable for a user.. a borrower who said that he doesn't need his hold after friday 20th January (for exemple), and this item is available the thursday 19th january with a pickup delay of 3 days (rules of the library. In our Library, this what we send in hold notice). The item will return in stacks the 20th January instead of monday the 23th. We would see after this patch how our users react and we could open a new ticket if necessary] -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 17910] New: can not search Some word in all branch library
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '17

17 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17910 Bug ID: 17910 Summary: can not search Some word in all branch library Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: reza0770(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In iquc.org we can not search in all library branch Some word were find in search And some word did not find in all branch, We have some excell data and converted to marc21 and import in koha, If you search the some word in all library, you only find in one library not in all library -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 8361] Issuing rule if no rule is defined
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '17

17 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8361 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #59086|0 |1 is obsolete| | --- Comment #15 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 59087 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=59087&action=ed… Bug 8361 (QA Followup) Add warnings - Added message to circulation.tt to warn if rule undefined for patron/itemtype combination To test: 1 - Remove all circ rules 2 - Add one rule 3 - Checkout to patron an itemtype that is outside of rule defined above 4 - Note explanation that no rule is defined -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8361] Issuing rule if no rule is defined
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '17

17 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8361 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #58967|0 |1 is obsolete| | --- Comment #14 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 59086 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=59086&action=ed… Bug 8361 (QA Followup) Add warnings - Added message to circulation.tt to warn if rule undefined for patron/itemtype combination To test: 1 - Remove all circ rules 2 - Add one rule 3 - Checkout to patron an itemtype that is outside of rule defined above 4 - Note explanation that no rule is defined -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8361] Issuing rule if no rule is defined
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '17

17 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8361 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12063] Change date calculation for reserve expiration to skip all holidays
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '17

17 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12063 --- Comment #29 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Alex Arnaud from comment #28) > > Hello Sonia, > > I'm not comfortable with having two expirationdate fields. And i think we > can spare ourselves from adding a new field by doing what Marcel suggests > previously: > override the expiration date only if the one requested by the patron is > before the calculated one. > > My two cents Yeah, sounds better :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12063] Change date calculation for reserve expiration to skip all holidays
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '17

17 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12063 --- Comment #28 from Alex Arnaud <alex.arnaud(a)biblibre.com> --- (In reply to Koha Team Lyon 3 from comment #27) > Hello, > I'm afraid that we are mired in a never ending discussion. > For me, as I have already sayd, there's no reason to keep expirationday > after the hold is available and waiting to be picked up, as this date is > meaning for users "I don't need this hold if it isn't available for me after > this date". > > But, I can see that it bothers Marcel so I propose that we try to find new > solutions to help this feature to be pushed in Koha (because it's really > important for many libraries). > > So, I don't know if it's valuable but it seems to me that it could at least > be simple, what do you think about creating a new field where we can stock a > "pickupexpirationdate" or something like that ? > > Marcel, Alex ? Is it possible ? Hello Sonia, I'm not comfortable with having two expirationdate fields. And i think we can spare ourselves from adding a new field by doing what Marcel suggests previously: override the expiration date only if the one requested by the patron is before the calculated one. My two cents -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12063] Change date calculation for reserve expiration to skip all holidays
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '17

17 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12063 --- Comment #27 from Koha Team Lyon 3 <koha(a)univ-lyon3.fr> --- Hello, I'm afraid that we are mired in a never ending discussion. For me, as I have already sayd, there's no reason to keep expirationday after the hold is available and waiting to be picked up, as this date is meaning for users "I don't need this hold if it isn't available for me after this date". But, I can see that it bothers Marcel so I propose that we try to find new solutions to help this feature to be pushed in Koha (because it's really important for many libraries). So, I don't know if it's valuable but it seems to me that it could at least be simple, what do you think about creating a new field where we can stock a "pickupexpirationdate" or something like that ? Marcel, Alex ? Is it possible ? -- You are receiving this mail because: You are watching all bug changes.

1 0