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

[Bug 18217] New: SMS alert number should be grouped with other borrower contact information.
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '22

22 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18217 Bug ID: 18217 Summary: SMS alert number should be grouped with other borrower contact information. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com SMS alert number is currently grouped with borrower messing preferences. This is inconsistent with the rest of the borrower contact information. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 15996] New: Bibliographic records diffing tool
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '22

21 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15996 Bug ID: 15996 Summary: Bibliographic records diffing tool Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently there is no tool to diff differences or changes between biblios or their different versions. This is most useful for logging who changed and what. This feature introduces a biblio diffing module, which takes an arbitrary amount of MARC::Records and produces a complex data structure about all the identified changes. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 17003] New: REST API: add route to get checkout's renewability
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '22

17 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17003 Bug ID: 17003 Summary: REST API: add route to get checkout's renewability Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: mail(a)jkozlovsky.cz QA Contact: testopia(a)bugs.koha-community.org Depends on: 13895 Add API route for checking renewability of an checkedout item. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13895 [Bug 13895] Add API routes for checkouts retrieval and renewal -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56

[Bug 16258] New: Add a preference to turn EDIFACT off
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '22

09 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16258 Bug ID: 16258 Summary: Add a preference to turn EDIFACT off Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Acq is a complicated module and the new EDIFACT related options and features add another layer of complexity. It would be good if the feature could be turned off for libraries not interested in the functionality to help simplify working with acq a bit again. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 76

[Bug 18283] New: Display improvements on report results - hide code and change wording
by bugzilla-daemon＠bugs.koha-community.org 31 May '22

31 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18283 Bug ID: 18283 Summary: Display improvements on report results - hide code and change wording Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 20608] New: Elasticsearch - relevancy weights proposition for unimarc in mappings.yaml
by bugzilla-daemon＠bugs.koha-community.org 25 May '22

25 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20608 Bug ID: 20608 Summary: Elasticsearch - relevancy weights proposition for unimarc in mappings.yaml Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: claire.hernandez(a)biblibre.com This is the mappings updated in mappings.yaml see bug 18316 for the code evolution. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 18316] New: Add weighting/relevancy options to ElasticSearch
by bugzilla-daemon＠bugs.koha-community.org 25 May '22

25 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18316 Bug ID: 18316 Summary: Add weighting/relevancy options to ElasticSearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 167

[Bug 20144] New: Test suite is failing with new default SQL modes
by bugzilla-daemon＠bugs.koha-community.org 19 May '22

19 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20144 Bug ID: 20144 Summary: Test suite is failing with new default SQL modes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 17258 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17258 [Bug 17258] [OMNIBUS] MySQL 5.7 -- You are receiving this mail because: You are watching all bug changes.

1 90

[Bug 20103] New: Remove Readonly::XS
by bugzilla-daemon＠bugs.koha-community.org 12 May '22

12 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20103 Bug ID: 20103 Summary: Remove Readonly::XS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com >From the Readonly CPAN page: "Install this module, but do not use it. ... Programs that you write do not need to know whether Readonly::XS is installed or not. They should just "use Readonly" and let Readonly worry about whether or not it can use XS. If the Readonly::XS is present, Readonly will be faster. If not, it won't. Either way, it will still work, and your code will not have to change." This removes the Readonly::XS from the PerlDependencies. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 16116] New: Change of issue publication date doesn't reflect on the next issue generated
by bugzilla-daemon＠bugs.koha-community.org 12 May '22

12 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16116 Bug ID: 16116 Summary: Change of issue publication date doesn't reflect on the next issue generated Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: francois.charbonnier(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com I noticed in 3.20, but also in master, that you can't change the next issue publication date when editing a serial subscription anymore. And, that we lost a feature I liked when receiving a new issue. Before 3.20, when receiving a new issue, you could change the "Published on" date and Koha will adjust the subscription's next issue publication date for all the new issues to be received. Test plan : 1. In Cataloging > New with Z39.50, look for issn = 1536-6596 (National Geographic) into the LCC z39.60 server. Add the record. 2. Add a new subscription for National Geographic. Fill-in the form. - use the default values of the first page - for the second page : First issue publication date = 10/01/2016 Frequency = 1/month Subscription lenght = 12 issues Subscription start date = 01/01/2016 Numbering pattern = Number Begins with = 1 - Save 3. Receive the first issue. Change the status to "received". Note that the "Published on" date = 10/01/2016. This date goes to the "Date published" column in the serial collection page. 4. The second issue is generated. Edit serial to receive the issue. 5. Change the "Published on" date to 11/02/2016. Change the status to "received". Save. 6. "Date published" for the next issue generated is : 10/03/2016. Before 3.20, it would have been "11/03/2016". It was a shortcut to change the Next issue publication date from the subscription. 7. Edit the subscription. Change the "Next issue publication date" to : 11/03/2016. 8. Go back to the serial collection page. Date published for the last expected issue = 11/03/2016 9. Receive the issue. Change the status to "received". Save 10. The next issue generated is 10/04/2016. It should have been 11/04/2016. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18