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

[Bug 18157] New: Forex rates for India based on GOC rates need support in the ACQ module
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '22

20 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18157 Bug ID: 18157 Summary: Forex rates for India based on GOC rates need support in the ACQ module 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: indradg(a)l2c2.co.in QA Contact: testopia(a)bugs.koha-community.org Procurement of books in India where price is in a currency other than INR is typically governed by GOC (Good offices committee) rates. See http://fpbai.org/goc-rates/ This rate is not necessarily as per the prevailing (short term) FOREX rates. Further it is required to maintain a history of the GOC rates for disbursal and payment of invoices. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 16155] New: Composite keys in TestBuilder and more
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16155 Bug ID: 16155 Summary: Composite keys in TestBuilder and more Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 15774] New: Additional fields for baskets
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '22

07 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15774 Bug ID: 15774 Summary: Additional fields for baskets Change sponsored?: 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: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: nicole(a)bywatersolutions.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 197

[Bug 17805] New: Add new authority type EVENT_TERM
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '22

28 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17805 Bug ID: 17805 Summary: Add new authority type EVENT_TERM Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org The Update No. 23 from November 2016 adds new fields, subfields and a new authority type: "Named Event". Koha should add a new authority type, for example EVENT_TERM, and add the new fields (see http://www.loc.gov/marc/authority/adapndxf.html) to Authorities. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 16520] New: Per-virtualhost SetEnvs don't work with Plack
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '22

24 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16520 Bug ID: 16520 Summary: Per-virtualhost SetEnvs don't work with Plack Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jweaver(a)bywatersolutions.com Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The various SetEnvs that can be used in Koha to configure memcached, change search limits, override sysprefs and add custom stylesheets don't work in Plack. It is likely impossible to fix this with the current HTTP proxy setup, so we need a workaround. -- You are receiving this mail because: You are watching all bug changes.

1 46

[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 08 Jun '22

08 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 16116] New: Change of issue publication date doesn't reflect on the next issue generated
by bugzilla-daemon＠bugs.koha-community.org 11 May '22

11 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

[Bug 17724] New: Callnumber not copied into serial issue, when callnumber subfield is linked to a plugin
by bugzilla-daemon＠bugs.koha-community.org 06 May '22

06 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17724 Bug ID: 17724 Summary: Callnumber not copied into serial issue, when callnumber subfield is linked to a plugin Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com To test: - Make sure your 952$o (callnumber) is linked to a plugin such as cn_browser.pl in your frameworks - Create a subscription with "create item on receive" and a callnumber - Receive an issue - Verify that the callnumber is not copied into the item on receive - Remove the plugin from the framework - Verify that the callnumber now is copied into the item on receive -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2