January 2022 - Koha-bugs - lists.koha-community.org

[Bug 27188] New: Show current class in plugins home
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27188 Bug ID: 27188 Summary: Show current class in plugins home Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In plugins home, when searching on a specific class, you see the table but no reminder which class is displayed. Only when there are no results you see it in message. I propose to show it in H1 title and remove it from no results message. Sort of what is asked in Bug 16391. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 25426] New: Return policy by item type following All Libraries rule when conflicting branch-specific rule exists
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '23

20 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25426 Bug ID: 25426 Summary: Return policy by item type following All Libraries rule when conflicting branch-specific rule exists 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In 19.11 and Master, Koha is not giving precedence to branch-specific return policy rules. To recreate: 1: set default return policy by item type for itype BOOK for all libraries to Item Floats 2: set return policy by item type for itype BOOK for Branch A to Item Returns to Issuing Library 3: set CircControl to "the library you're logged in at" 4: set library to Branch B 5: find a BOOK item currrently at Branch B, check it out to a Branch B patron 6: set library to Branch A 7: check item in 8: no transfer is generated, item remains at branch A In 19.05, the same process results in a transfer back to Branch B. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 29338] New: Reprinting holds slip with updated expiration date
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '23

20 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29338 Bug ID: 29338 Summary: Reprinting holds slip with updated expiration date Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When staff change a waiting hold expiration date to a date further in the future, there is no way to print a new hold slip with the updated date. For example, holds are set to expire in 5 days. I change the expiration date to 10 days. Typically I would check the item in to trigger a new hold slip, but when I do, the expiration date is reset to 5 days. It would be really helpful to have a print hold slip button on the holds table, not just for this scenario, but for other situations too, such as when a staff member checks an item in to generate a new slip, the waiting date is changed. Having this print button would alleviate this. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 23024] New: Limit quantity of items in staff items
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '23

20 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23024 Bug ID: 23024 Summary: Limit quantity of items in staff items Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: b.pastern4k(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Is there a patch or a setting that can limit amount of items shown in bibliorecord? In OPAC there is something of that kind - "This record has many physical items (xxx). Click here to view them all." The issue here is that if a record has more than a couple hundred items, it takes too much time to generate template on server and user has to wait few minutes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 24221] New: Convert OPACMySummaryNote system preference to news block
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '23

19 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24221 Bug ID: 24221 Summary: Convert OPACMySummaryNote system preference to news block 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 22880 Building on 22318, the OPACMySummaryNote system preference should be converted to a Koha news block. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22880 [Bug 22880] Convert opacheader system preference to news block -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 28685] New: Should AutoControlNumber also overwrite 003 field ?
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '23

19 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28685 Bug ID: 28685 Summary: Should AutoControlNumber also overwrite 003 field ? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Discussion from bug 27981 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 26788] New: Circulation rule note field too small.
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '23

17 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26788 Bug ID: 26788 Summary: Circulation rule note field too small. 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The note field does not allow enough room for notes. Should be much bigger and allow for multiline entry, similar to circulation note in patron account. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 21762] New: ES: Is it possible to differentiate between any and anywhere?
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '23

17 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21762 Bug ID: 21762 Summary: ES: Is it possible to differentiate between any and anywhere? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl See also bug 8962 about differentiating any from anywhere in Zebra. Any would be the sum of all user defined indexes, and anywhere would really be all data. Is this possible in Elastic Search ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 25590] New: B_streetnumber is missing from opac-memberentry.pl
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25590 Bug ID: 25590 Summary: B_streetnumber is missing from opac-memberentry.pl 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: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org If a patron adds an alternate address to their patron record in the OPAC, there is no option to enter a street number. This field is available in the staff client. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 18280] New: Item barcodes should be locked when record is created
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '23

16 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18280 Bug ID: 18280 Summary: Item barcodes should be locked when record is created Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When several cataloguers are cataloguing simultaneously and the autoBarcode system preference is set to generate the barcodes in 1, 2, 3 form, it is possible that the same item barcode will be assigned to two different items at the same time which prevents the record from being saved. Koha should lock the barcode in some way once it has been allocated, even if the item record is not yet saved. -- You are receiving this mail because: You are watching all bug changes.

1 6