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

[Bug 34992] New: Add language setting to vendors, so we can send translated order/claim emails
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34992 Bug ID: 34992 Summary: Add language setting to vendors, so we can send translated order/claim emails 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 Libraries often want notices and English and the local language as they are ordering both from local and international booksellers. It would be nice if we were able to send the acq notices in different languages. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 25800] New: Allow to define preferred language for vendors to be able to automatically sent translated order/claim emails
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25800 Bug ID: 25800 Summary: Allow to define preferred language for vendors to be able to automatically sent translated order/claim emails 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 At the moment the ACQORDER email can only be sent in the default language, even as the editor suggests that multiple languages can be configured (TranslateNotices system preferene). It would be nice if a preferred language for the vendor could be configured that is then used to sent the notice in the language chosen. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 21544] New: Self Check-in tool does not trigger holds
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21544 Bug ID: 21544 Summary: Self Check-in tool does not trigger holds Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 15492 Stand alone self Check-in Tool has been released into 18.05, however, if a book that has a hold on it gets returned through the stand alone self checkin tool, the hold does not trigger. There is no alert to the patron that this book needs to be brought to the circulation desk or prompt for any other direction. For libraries to use this self checkin tool, there needs to be some function/block that alerts the checkin with a hold to be different than a book with no hold. I tested, both bib level holds and item level holds were treated the same way, with no alert. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 21561] New: Check out restriction to category / branch
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21561 Bug ID: 21561 Summary: Check out restriction to category / branch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: joseanjos(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com As discussed here: http://koha.1045719.n5.nabble.com/Check-out-restriction-to-category-branch-… its not possible to restrict holds between one library to a group of libraries. With independentbraches it will restrict everything, including Patrons modification. IndependentBranchesPatronModifications should prevent that but doesn't do it. The pretended is this: 1 Main Library (City hall Library CHL) 20 School Libraries (on the same server) Assuming that if a Patron from a School wants to be patron of CHL it will be duplicated Shouldn't be possible checkout from CHL to any school Patron Shouldn't be possible checkout from school to any CHL Patron Should be possible to transfer from CHL to any school Patron and vice-versa School Staff category should be able to modify Patrons because: - Every student is created with is student Nº - On next year he can change from school - Librarian from school should be able to change Library from Student This last point is very important! Otherwise only super librarians can change it. That would be impossible to manage because hundreds of students change every year. The Librarian of each school MUST do that job. Something like Library transfer limits but Library Holds limits would be nice -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 21609] New: Store pre-rendered html in search engine (zebra or elastic).
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21609 Bug ID: 21609 Summary: Store pre-rendered html in search engine (zebra or elastic). 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org XSLT rendering is slow, I started to think about whether it would be possible to store pre-rendered HTML in zebra or elastic, so that we only have to run the marcxml to html xslt transformations at indexing time rather than per, search. It's a time vs. space optimization, and I don't know if the html generated by xslt ever gets cached; if it does, we might not see any benefit. Anyway, putting it out for discussion. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 21642] New: create patron card template in koha generate error not assign template id
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21642 Bug ID: 21642 Summary: create patron card template in koha generate error not assign template id Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: it.officer(a)ppsu.ac.in QA Contact: testopia(a)bugs.koha-community.org create patron card template in koha generate error not assign template id -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 21677] New: MARC detail view may show field header info erroneously
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21677 Bug ID: 21677 Summary: MARC detail view may show field header info erroneously Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org If the fields in the marcxml are not in order, and LabelMARCView is set to compact, the MARC detail view can show the field headers multiple times. To reproduce: 1) Turn on LabelMARCView 2) Turn on EnableAdvancedCatalogingEditor (Rancor allows entering fields in any order, unlike the old editor) 3) Catalogue a new record with the following fields in this order: 655 _ _ ‡afoo 100 _ _ ‡abar 655 _ _ ‡abaz 650 _ _ ‡aqwerty 655 _ _ ‡aqux 655 _ _ ‡aquux 4) Go to that record's MARC detail view. In the 6xx tab, you will see three separate entries for 655 fields: 655 $a foo 655 $a baz 655 $a qux $a quux How it should look: 655 $a foo $a baz $a qux $a quux -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 21707] New: Wrong CSRF token - adding a new patron with auto generated card number turned on
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21707 Bug ID: 21707 Summary: Wrong CSRF token - adding a new patron with auto generated card number turned on Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cfhong2000(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Trying to add a new patron by entering Surname and click Save. Card Number leave blank since it is using auto-generated. The following error was thrown. Software error: Wrong CSRF token at /usr/share/koha/intranet/cgi-bin/members/memberentry.pl line 307. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 21859] New: Fields to choose on Notice editor often contains non-applicable tables and fields
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21859 Bug ID: 21859 Summary: Fields to choose on Notice editor often contains non-applicable tables and fields Change sponsored?: --- Product: Koha Version: unspecified 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 The fields to insert section of the notices and slips editor (Home › Tools › Notices & slips › Modify notice) bases the fields to add on 'letter.module'. Unfortunately, this means that there are often tables shown that are not actually available on the notice in question. The most extreme example are DUEDGST and PREDUEDGST, which can only use <<branches.*>>, <<borrowers.*>>, <<items.content>> and <<count>>, but shows <<biblio.*>>, <<biblioitems.*>>, <<items.*>>, <<opac_news.*>> and <<issues.*>>, all of which are un-available. This is part of the Notice documentation rfc (https://wiki.koha-community.org/wiki/Notice_documentation_rfc) See also Bug 21858. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31100] New: Notice editor should only show relevant options
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31100 Bug ID: 31100 Summary: Notice editor should only show relevant options Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, when editing a notice, you can select from a long list of fields to insert into a notice template. However, in many cases (e.g. PREDUEDGST), only a sub-selection of these will ever actually work. We should control the list so that it only shows what you can use. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1