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

[Bug 24674] New: Uncertain years for publicationyear/copyrightdate -- corrected
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24674 Bug ID: 24674 Summary: Uncertain years for publicationyear/copyrightdate -- corrected Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl According to n. 4.3.8 od ISBD Consolidated Edition of 2011, valid for date description are also string like [1960-], [17-]. Currently strings like these are not interpreted correctly by C4::Biblio::_adjust_pubyear. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 43

[Bug 17314] New: REST API: Add API route to create, list and delete a purchase suggestion
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17314 Bug ID: 17314 Summary: REST API: Add API route to create, list and delete a purchase suggestion Change sponsored?: --- Product: Koha Version: unspecified 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 It would be nice to have an API for creating a purchase suggestion. It would be used for instance in VuFind. Proposed implementation: To create: POST /suggestions/{borrowernumber} Incoming data: { title (required) author copyrightdate isbn publishercode collectiontitle place itemtype patronreason note negcap } Outcoming data: 200 OK / 403 Forbidden / 409 Conflict (when already exists the proposal) { error status } To list: GET /suggestions/{borrowernumber} Outcoming data: list of suggestions To delete: DELETE /suggestions/{borrowernumber}/{suggestion_id} Outcoming data: 204 No Content (successful deletion) / 403 Forbidden / 404 Not Found -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 135

[Bug 24183] New: Introduce `before_send_messages` hook
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24183 Bug ID: 24183 Summary: Introduce `before_send_messages` hook Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be beneficial to have a hook inside process_message_queue.pl to allow plugins the option of taking pre-processing actions on the messages in the message queue before they are sent. An example of where this would be beneficial is the Recalls plugin, where currently one has take serverside actions to configure additional cronjobs as part of setting the plugin up. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 16467] New: Discharge requests pending count should appear on patrons home page
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '21

10 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16467 Bug ID: 16467 Summary: Discharge requests pending count should appear on patrons home page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently the "Discharge requests pending" count appears only on the staff client home page. Like the count of patrons requesting modification, the discharge request count should also appear on the patrons home page (members-home.pl). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 24382] New: Wrong information showing on detail pages for fines/fees and payments
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '21

10 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24382 Bug ID: 24382 Summary: Wrong information showing on detail pages for fines/fees and payments Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment, the _first_ table in a payment details page reads: Details of payment Date Description of charges Barcode Due date Return date Note Amount Outstanding This makes no sense - these are the columns for a fine or fee, but they don't apply well to a payment. When you compare to the table shown for a fine/fee, I think the table should actually display with these lines: Date created Date updated Amount Amount outstanding Type Note Transacting librarian Date/time of change Amount of change Type of change -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20310] New: Article requests: Can we redirect article records without items to host record?
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '21

09 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20310 Bug ID: 20310 Summary: Article requests: Can we redirect article records without items to host record? 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org If I have a biblio record (without items) for article XXX in serial Y and I included a MARC21 773 host record that includes title, page info and host record number, it would be very helpful if the OPAC form would redirect me to the serial Y host record and I could select the correct item over there. (Can we prefill the page info or even preselect the item?) Probably we should assume here that the ART records have the 'Record only' rule and the SER records have 'Item only' rule, and the record number is referring to the local catalogue (check the marc org code?). -- You are receiving this mail because: You are watching all bug changes.

1 95

[Bug 24885] New: Remove guided reports
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '21

09 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24885 Bug ID: 24885 Summary: Remove guided reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org The guided reports feature was never fully developed and isn't useful. SQL reports are clearly the focus of development moving forward and should be the center of the reports module instead. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 24512] New: Should be able to have 'hidden'/'administrative' branches
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '21

08 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24512 Bug ID: 24512 Summary: Should be able to have 'hidden'/'administrative' branches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some libraries have branches that are not for the public, or are used for statistics etc. It would be nice to be able to define a branch as 'hidden' in administration and make sure it is not shown in opac dropdowns for search etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 25883] New: Show transfer on checkin screen
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '21

05 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25883 Bug ID: 25883 Summary: Show transfer on checkin screen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When an item generates an automatic transfer at checkin, there's nothing on the checkin screen to indicate that the transfer has generated. Following bug 23129, the holding branch shows the library where the item was checked in, rather than the library the item is going to. That's a good an accurate change, but means we don't have any way to see the transfer. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 24370] New: Editing Purchase Suggestion changes the Acquisition Library
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '21

05 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24370 Bug ID: 24370 Summary: Editing Purchase Suggestion changes the Acquisition Library Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Editing a suggestion changes the Acquisition Library to be the user's logged in branch. As a multi-branch system, we'd like to be able to edit and keep that information. This helps us track requests and spending from different branches. The branch is only changed on edit, not when batch changing statuses. Lisette -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43