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

[Bug 11083] Authority search result display in staff interface should be XSLT driven
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11083 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|Needs documenting |RESOLVED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11083] Authority search result display in staff interface should be XSLT driven
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11083 --- Comment #19 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Fridolin Somers from comment #18) > Ah but the koha-manual merge requests is closed And you are correct :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 34197] New: UI enhancement in vendor form
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34197 Bug ID: 34197 Summary: UI enhancement in vendor form Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When adding a vendor, you can add contacts for this vendor. In the contact form, there is a list of checkboxes where some are about acquisitions and some are about serials, mixed together. I wonder if it would be possible to change this into either two columns or two sub-sections, separating the acquisitions and serial options? Acquisitions options: - Primary acquisitions contact - Contact when ordering? - Contact about late orders? Serials options: - Primary serials contact - Contact about late issues? I always find it weird to explain in training, this one is for acquisitions and this one is for serials and this one is for acquisitions, etc. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 34509] New: Cannot create baskets of too many vendors
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34509 Bug ID: 34509 Summary: Cannot create baskets of too many vendors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When creating a new basket, we load every existing vendor into a dropdown and allow the user to choose which library the basket is for. On systems with too many vendors, this can be problematic. We should either remove this, as you generally create a basket from preselected vendor, or use the api to load vendor options as needed -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[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 12133] Guarantor requirements when registering a patron
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12133 --- Comment #57 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- Pushed to master for 23.11. Nice work everyone, thanks! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12133] Guarantor requirements when registering a patron
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12133 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)| |23.11.00 released in| | Status|Passed QA |Pushed to master -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35311] New: Add ability to map content of EDI FTX segment into various fields
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35311 Bug ID: 35311 Summary: Add ability to map content of EDI FTX segment into various fields 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 27793 The FTX segment allow for various free text instructions to be added to an EDI message.. these are at the Basket level effectively in Koha. Many institutions use this field for arbitrary additional functionality in their setups and would like the option to map the content into various fields of their chosing rather than have it appear only in the Vendor note. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27793 [Bug 27793] Store Contents of FTX segment of EDI quotes for inclusion in orders -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[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