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

[Bug 13749] On loading holds in patron account 'processing' is not translatable
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13749 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs(a)lists.koha-commun |oleonard(a)myacpl.org |ity.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 14570] Make it possible to add multiple guarantors to a record
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14570 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |23778 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23778 [Bug 23778] Regression: Guarantor entry section no longer has a unique id -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15161] Sorting by Title does not include volume/part information from $p and $n
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15161 --- Comment #1 from John Sterbenz <jsterben(a)umich.edu> --- I do not view this request as an enhancement--I view this as an error in the software requiring correction. Perhaps the customizable abilities of ElasticSearch corrects this? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15161] Sorting by Title does not include volume/part information from $p and $n
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15161 John Sterbenz <jsterben(a)umich.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsterben(a)umich.edu -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21701] New: Have PayPal return to originating OPAC url rather than OPACBaseURL
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21701 Bug ID: 21701 Summary: Have PayPal return to originating OPAC url rather than OPACBaseURL Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: techservspec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We are part of a multi-library consortium that shares a single Koha server. Each of the member libraries has its own unique OPAC URL. When a patron pays a charge online, they are directed to PayPal. When the transaction is completed (or if the patron cancels the payment) they are redirected to the value of OPACBaseURL, not the URL from which the patron was using. This ends up with the ending up on a screen displaying a combination of all our OPACs together. We would like to have the ability to have the URL of the OPAC the patron is using be sent as the return url sent to PayPal. This could also be set up as a global option to use either the OPACBaseURL or the OPAC's individual's domain (for systems that would prefer to still use the current method). -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 13937] Add an Elasticsearch-compatible Z39.50/SRU daemon that can inject item status MARC subfields
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937 --- Comment #187 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Martin Renvoize from comment #185) > You mean a few years isn't sufficient? I've spent hours QAing this on a > couple of occasions and spend a fair chunk of time discussing it with Nick > and other ES experts at the Hackfest.. it has my full backing at this point > and I also have assurances from ES users that we will get quick followups > should there be issues. Ok ok -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13937] Add an Elasticsearch-compatible Z39.50/SRU daemon that can inject item status MARC subfields
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Manual -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13937] Add an Elasticsearch-compatible Z39.50/SRU daemon that can inject item status MARC subfields
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937 --- Comment #186 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- Nice work! Pushed to master for 19.11.00 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13937] Add an Elasticsearch-compatible Z39.50/SRU daemon that can inject item status MARC subfields
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to master Version(s)| |19.11.00 released in| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13937] Add an Elasticsearch-compatible Z39.50/SRU daemon that can inject item status MARC subfields
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937 --- Comment #185 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- (In reply to Marcel de Rooy from comment #181) > A patch set of this size surely needs a sufficient amount of QA time. Hope > you are not too fast? You mean a few years isn't sufficient? I've spent hours QAing this on a couple of occasions and spend a fair chunk of time discussing it with Nick and other ES experts at the Hackfest.. it has my full backing at this point and I also have assurances from ES users that we will get quick followups should there be issues. (In reply to David Cook from comment #183) >At a glance, it does look pretty standalone. However, could a more normative example/documentation be provided? Agreed, I have requested such documentation and should Ere not get a chance to get to it quickly I will be asking Bywater for some assistance too. So.. In short.. lets get this baby pushed :) -- You are receiving this mail because: You are watching all bug changes.

1 0