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

[Bug 13871] OverDrive message when user authentication fails
by bugzilla-daemon＠bugs.koha-community.org 11 May '16

11 May '16

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

1 0

[Bug 13871] OverDrive message when user authentication fails
by bugzilla-daemon＠bugs.koha-community.org 11 May '16

11 May '16

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

1 0

[Bug 13871] OverDrive message when user authentication fails
by bugzilla-daemon＠bugs.koha-community.org 11 May '16

11 May '16

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

1 0

[Bug 13871] OverDrive message when user authentication fails
by bugzilla-daemon＠bugs.koha-community.org 11 May '16

11 May '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13871 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to Stable |ASSIGNED --- Comment #61 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #59) > The problem I see here is that it's already in a stable release. So a revert > is not as easy as just getting it out of master. It is a trivial fix. So why talk revert? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13871] OverDrive message when user authentication fails
by bugzilla-daemon＠bugs.koha-community.org 11 May '16

11 May '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13871 --- Comment #60 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- Created attachment 51421 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=51421&action=ed… Bug 13871: [QA Follow-up] Fix small regression on AF with branchcode in Patron Info request If you enable send_patron_home_library_in_af in your sip account, you want a separate AF field for the home branch. Test plan: Send a 63 (Patron Info) and verify that you have an extra AF. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13871] OverDrive message when user authentication fails
by bugzilla-daemon＠bugs.koha-community.org 11 May '16

11 May '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13871 --- Comment #59 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- The problem I see here is that it's already in a stable release. So a revert is not as easy as just getting it out of master. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13871] OverDrive message when user authentication fails
by bugzilla-daemon＠bugs.koha-community.org 11 May '16

11 May '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13871 --- Comment #58 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Kyle M Hall from comment #56) > This is > definitely a regression and needs to be fixed or we may have to revert this > bug in master before the release. Note that I have seen more serious regressions than this where the word "revert" is not used rightaway. Just saying. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13871] OverDrive message when user authentication fails
by bugzilla-daemon＠bugs.koha-community.org 11 May '16

11 May '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13871 --- Comment #57 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Kyle M Hall from comment #56) > Yes, SIP2 can have multiple AF fields. In that case that is the best route. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13871] OverDrive message when user authentication fails
by bugzilla-daemon＠bugs.koha-community.org 11 May '16

11 May '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13871 --- Comment #56 from Kyle M Hall <kyle(a)bywatersolutions.com> --- > Hi Nick, > Your problem should not be that hard to resolve. > I think we should not rely on the fact that AF only includes the patron > branch code. It is just a screen message field. And I am not sure if SIP2 > officially supports multiple AF fields btw. > Could you use field AO that only contains the institution id? But not usable > for another branch. > Or - as workaround - add a prefix to the AF home branch part and capture > only that part with a simple regex or so? Yes, SIP2 can have multiple AF fields. The branchcode in AF field feature was requested specifically by Overdrive to be able to track use by home library. The AO does not transmit the patron home branch, it transmits the branch of the user used to authenticate as for using SIP. It is not practical or correct to send the patron branch on the AO field. This is definitely a regression and needs to be fixed or we may have to revert this bug in master before the release. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11144] Fix sequence of cronjobs: automatic renewal - fines - overdue notices
by bugzilla-daemon＠bugs.koha-community.org 11 May '16

11 May '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11144 --- Comment #29 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I'd rather fix the first and have correct overdues sent, then having to sent another batch of emails to "correct" - but that's probably a problem mostly for libraries charging fines. Please note: This whole discussion is about the file for non-package setups. I think the behaviour for packages is different anyway. As we are using packages I am fine with any solution. We use debian/koha-common.cron.daily as changed in this patch for several versions now. -- You are receiving this mail because: You are watching all bug changes.

1 0