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

[Bug 26363] New: Provide a systemd unit file for background_jobs_worker
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '22

04 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26363 Bug ID: 26363 Summary: Provide a systemd unit file for background_jobs_worker Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: dcook(a)prosentient.com.au Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 22417 We need a systemd service’s unit file to start/stop misc/background_jobs_worker.pl, like we do with the debian packages in debian/scripts/koha-worker Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 [Bug 22417] Add a task queue -- You are receiving this mail because: You are watching all bug changes.

1 62

[Bug 17841] New: Can't use indexname "acqdate, st-date-normalized" in keyword search
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17841 Bug ID: 17841 Summary: Can't use indexname "acqdate,st-date-normalized" in keyword search Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It is possible to search for acquisition date from the advanced search in staff. But if you try to use the index name for an 'expert search' in the keyword search field, no results will come up. Example: Advanced search > acquisition date: 2016-12* (or whatever works for you) This should give correct results. Enter acqdate,st-date-normalized: 2016-12* into the keyword search - no results will appear. Something seems to be missing in order to make it possible to construct the same search manually. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 28416] New: Email::Sender::Transport::SMTP is using 10Mo of RAM
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28416 Bug ID: 28416 Summary: Email::Sender::Transport::SMTP is using 10Mo of RAM Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 28410 Well ok, it's not that much over the ~130Mo the usual library stack, but maybe we should replace the use with a require to load in only when needed? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28410 [Bug 28410] Reduce memory footprint -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 26003] New: Could the holds queue be live rather than built via cron
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26003 Bug ID: 26003 Summary: Could the holds queue be live rather than built via cron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I get the feeling that the functionality of the holds queue could be achieved via triggers after various actions rather than require a regular full rebuild via a cron job. I'm thinking the action of placing a hold, the action of checking in items and checking out items... these are the main things that can affect the holds queue data and such actions should be able to trigger a small calculation to update the holds queue for the related item, branch etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 24415] New: UX enhancement - Improve access to tabs
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '22

31 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24415 Bug ID: 24415 Summary: UX enhancement - Improve access to tabs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 18846] New: Fund list on 'aquisitions statistics' page shows wrong values
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '22

30 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18846 Bug ID: 18846 Summary: Fund list on 'aquisitions statistics' page shows wrong values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 To test: - Create a budget with some funds - Duplicate the budget - You should now have 2 budgets with the same fund codes and descriptions for each - Check the fund list on the reports > aquisitions statistics page - Verify the list looks correct - you should see all funds once - Alter the description of one of your funds and save - Check the fund list again after reloading the page: The changed fund will appear "doubled up" with the same (old or new) description -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 23081] New: Item search : Filter for Items with Zero Checkouts Returns No Results
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '22

30 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23081 Bug ID: 23081 Summary: Item search : Filter for Items with Zero Checkouts Returns No Results Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: jyorio(a)esilibrary.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When conducting an item search, if I set the checkout count to = 0, I get "No data available in table" (and there are most definitely items without any checkouts). If I conduct a search that returns results (without filtering by checkout count), and then enter 0 into the box on the search results screen, I get results with 10 checkouts. I expected to get the items with 0 checkouts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38

[Bug 24875] New: Remvoe extra punctuation from tools home page
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '22

30 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24875 Bug ID: 24875 Summary: Remvoe extra punctuation from tools home page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: katrin.fischer(a)bsz-bw.de Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 26079] New: Use 008 positions 14-16 as authoritative authority entry type
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '22

30 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26079 Bug ID: 26079 Summary: Use 008 positions 14-16 as authoritative authority entry type Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Instead of using the auth_header.authtypecode as the authoritative authority entry type look at the 008 position 14-16. According to MARC standards ( https://www.loc.gov/marc/authority/ad008.html ): * 088 position 14 = 'a' means the authority record is a name authority * 008 position 15 = 'a' means the authority record is a subject authority * 008 position 16 = 'a' means the authority record is a series authority These three characters allow authority records to belong to multiple auth types. Koha only allows an authority record to have one auth type. Given a syspref is enabled load all authorities into the default authority type. Search/use/display them according to how they are coded in their 008 positions 14-16 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 22993] New: Messaging preferences not set for patrons imported through API
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '22

28 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22993 Bug ID: 22993 Summary: Messaging preferences not set for patrons imported through API Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hans.palsson(a)hkr.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- It appears that from 18.11.03 (maybe earlier), patrons that are created/imported through the API does not get messaging preferences set as specified in the system preferences ("Default messaging preferences for this patron category"). This should work in the same way that messaging preferences are set for patrons created in the GUI. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30