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

[Bug 22712] New: Funds from inactive budgets appear on Item details if using MarcItemFieldstoOrder
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22712 Bug ID: 22712 Summary: Funds from inactive budgets appear on Item details if using MarcItemFieldstoOrder Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 88047 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=88047&action=ed… drop down Bug 14850 has been fixed and patched for 18.11. This removes the ability to see inactive funds when allocating orders to these funds from an inactive budget. However, if a library is using the system preference MarcItemFieldstoOrder, all the funds will appear in the drop-down menu for that item record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 27249] New: Using the calendar to 'close' a branch can create an infinite loop during renewals
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27249 Bug ID: 27249 Summary: Using the calendar to 'close' a branch can create an infinite loop during renewals Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com When calculating due date using holidays we don't account for the case where everyday is a holiday until the end of time To recreate: 1 - Set OverdueNoticeCalendar to 'Use calendar' and useDaysMode to 'Use the calendar to push' 2 - Browse to Tools->Calendar 3 - Set every day of the week to "Holiday repeated every same day of the week" 4 - Issue an item to a patron 5 - Check the box and select 'Renew selected items' 6 - Watch the spinner spin...and spin...and spin -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 26468] New: Item search should include a way to limit by damaged
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '23

11 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26468 Bug ID: 26468 Summary: Item search should include a way to limit by damaged Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On itemsearch.pl you can limit by LOST or WITHDRAWN statuses but not by DAMAGED status. It would be neat if that was added. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 25814] New: SIP: Add a message on successful checkin
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '23

11 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25814 Bug ID: 25814 Summary: SIP: Add a message on successful checkin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Currently, Koha does not return a message on successful SIP checkin. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 21330] New: Add xslt for authority normal view in OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21330 Bug ID: 21330 Summary: Add xslt for authority normal view in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, It would be fine to have a xslt stylesheet for authority normal view in OPAC (opac-authoritiesdetail.pl). Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes.

1 74

[Bug 27862] New: Add documentation for OpacBrowseSearch
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27862 Bug ID: 27862 Summary: Add documentation for OpacBrowseSearch Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org On manual for 20.11 release, there is no documentation about the new feature "Opac Browse Search". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 27793] New: Store Contents of FTX segment of EDI quotes for inclusion in orders
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27793 Bug ID: 27793 Summary: Store Contents of FTX segment of EDI quotes for inclusion in orders 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: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org A number of vendors send data in the FTX segment of EDI quotes, and expect this to be returned in the subsequent order. This may indicate the form of item to be supplied (electronic v physical book) or data entered to indicate that the order is the result of a special request. The standard is somewhat misleading on this as it encourages use of FTX for encoded delivery priority info. However this appears to be obsolete in practice and examination of numerous quotes show no suppliers using it this way, whereas some suppliers (e.g. proquest) are making the contents of this segment fundamental to their procedures ensure FTX content is saved (in vendornote) and that the saved note is included in an order sent as a result of the quote -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 23838] New: Add ability to view item renew history
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23838 Bug ID: 23838 Summary: Add ability to view item renew history 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.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It should be possible, when viewing a patron's circulation history, to view details of an item's renewals. Each renewal should be displayed as: Renewed on <renewal date> by <renewed by> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 119

[Bug 24609] New: Add routes for getting and setting checkout due date
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '23

07 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24609 Bug ID: 24609 Summary: Add routes for getting and setting checkout due date Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com To allow the work in bug 24608 to proceed, we need an API route to allow the setting of a checkout's due date. I will add a GET route also. The proposed endpoints are: Return a checkout's due date: Method: GET URL: /checkouts/{checkout_id}/date_due Set a checkout's due date: Method: POST URL: /checkouts/{checkout_id}/date_due Body: { date_due: '2020-02-07 10:49:08' } -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 18827] New: Elasticsearch mappings - not displayed or retrieved in saved order
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '23

07 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18827 Bug ID: 18827 Summary: Elasticsearch mappings - not displayed or retrieved in saved order Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The mappings listed under 'Biblios' and 'Authorities' are draggable - this allows ordering of fields. The ordering affects the id field in the search_marc_map table When retrieving for display or mapping we are not ordering by the this field. In general I am not sure if we are gaining anything with this ordering: https://www.elastic.co/guide/en/elasticsearch/guide/current/_sorting.html " When sorting on fields with more than one value, remember that the values do not have any intrinsic order; a multivalue field is just a bag of values. Which one do you choose to sort on?" I think we can switch to the idea that a single field per index should be chosen for ordering: author = 100 (only make this one sortable) author = 700 author = 245c or, in the case of authorities, we should expect a single field to populate the field for sorting (100, 110, 150 ... are alldefined as 'main-heading' - but each record should only have a single one of these field) -- You are receiving this mail because: You are watching all bug changes.

1 18