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

[Bug 35331] New: Add an ILL table actions plugin hook
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '24

21 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35331 Bug ID: 35331 Summary: Add an ILL table actions plugin hook Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: katrin.fischer(a)bsz-bw.de, magnus(a)libriotech.no, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 27682] New: Add a floating table header for Search engine configuration
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '24

21 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27682 Bug ID: 27682 Summary: Add a floating table header for Search engine configuration 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: severine.queune(a)bulac.fr The table header in Elastic search should be a floating bar, as the table could be veeeeery long. It's sometimes hard to remember what is the order of the different Yes/No dropdown menus and it can be the source of confusion or bad settings. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 20630] New: An attempt at multitenancy with Mojolicious
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '24

21 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20630 Bug ID: 20630 Summary: An attempt at multitenancy with Mojolicious Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 20582 There seems to be some concerns about the capability for Koha to be multitenant in a persistent environment, in particular with Mojolicious. This bug will try to address those concerns. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20582 [Bug 20582] Turn Koha into a Mojolicious application -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 29198] New: Inconsistencies in opac results display vs staff results display
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '24

21 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29198 Bug ID: 29198 Summary: Inconsistencies in opac results display vs staff results display 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 21260 brought about some changes to OPAC display which are great. However there are now some inconsistencies between the displays in OPAC results vs OPAC details. To recreate: 1. Create a NOT_LOAN value with a AV of 1. Give it both an description and OPAC desrciption. 2. Find something in the catalog with at least 2 items. 3. Mark at least 1 item with the new NOT_LOAN value. 4. Look at the OPAC results, which display in green and say 'Items available for reference:' 5. Look at the same record in the staff results display. The same item is considered 'Unavailable' These displays should be consistent. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 31123] New: Add a simple way to add 'Harmful content warnings' to catalogue records
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '24

20 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31123 Bug ID: 31123 Summary: Add a simple way to add 'Harmful content warnings' to catalogue records 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I propose adding a new 'quick add' button into the biblio toolbar that would trigger a modal where staff can enter a short content warning note to be added to a designated 59X field (MARC21). I would then modify the default XSLTs to display the note highlighted to draw the users attention. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 30353] New: Enhance BiblioItemtypeInfo so that item level itypes can be displayed in results
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '24

20 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30353 Bug ID: 30353 Summary: Enhance BiblioItemtypeInfo so that item level itypes can be displayed in results Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org In our libraries 942$c is usually not set, as it would be overwritten by the nightly imports from the union catalog. Therefore it would be great if you could display the item level itype (maybe the first, or all that appear on the record) in the result list with another option to BiblioItemtypeInfo system preference. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 34106] New: Patron search in member-search-box.inc always defaults to 'Starts with' search
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '24

20 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34106 Bug ID: 34106 Summary: Patron search in member-search-box.inc always defaults to 'Starts with' search 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. In the main search header switch to 'Search patrons'. Bring up the dropdown and look at 'Search type:'. 2. It defaults to 'Starts with'. 3. Go to '/cgi-bin/koha/members/members-home.pl' and look at the 'Search type:' on the left side. 4. It defaults to 'Contains' 5. Do a patron search from both these places, setting the 'Search type' to contains. 6. The search bar in the header always resets to 'Starts with' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 25228] New: Patron messaging preferences clearing if duplicate warning
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '24

20 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25228 Bug ID: 25228 Summary: Patron messaging preferences clearing if duplicate warning Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Patrons Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 18595 Same as bug 5161 for messaging preferences. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18595 [Bug 18595] Move C4::Members::Messaging to Koha namespace -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 33898] New: background_jobs_worker.pl may leave defunct children processes for extended periods of time
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '24

20 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33898 Bug ID: 33898 Summary: background_jobs_worker.pl may leave defunct children processes for extended periods of time Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It appears that the background jobs worker can leave defunct processes for periods of time. Though it is mostly harmless, it would be nice if that did not happen. Children are reaped automatically when start or wait_all_children are called. We only call start when a new job is found, and wait_all_children after exiting our while loop. The solution is to simply call reap_all_children after we sleep. This is a non-blocking call that will clean up those defunct processes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 32029] New: Automatic item modifications by age missing biblio table
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '24

20 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32029 Bug ID: 32029 Summary: Automatic item modifications by age missing biblio table 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In automatic item modifications by age missing, conditions can be on columns of tables items or biblioitems. Table biblio is missing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35