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

[Bug 14156] Add id tags to each MARC note in the display
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14156 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |35689 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35689 [Bug 35689] Add id and classes to each MARC note in OPAC bibliographic details -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35487] New: It would be nice to have a Selective dissemination of information module
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35487 Bug ID: 35487 Summary: It would be nice to have a Selective dissemination of information module Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Selective dissemination of information is a current awareness service in which libraries or information centers send new publications to users. It can be implemented in Koha through lists that have to be manually send to interested users, or through public lists to which users can subscribe through RSS. A real Selective dissemination of information module would need to be able to configure one or several search terms or search expressions, and a scheduler to trigger these searches regularly. The results of the search should only include records added after the last search and be send to users in a user list. The "send" function could be implemented through mail or OPAC access or both. Librarians should be able to control the lists sent to the users. That could be implemented for example with a delay in sending during which librarians could alter the list, or more simple through a access to sent lists where librarians can control which records has been sent. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 28966] New: Holds queue viewer too slow to load for large numbers of holds
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28966 Bug ID: 28966 Summary: Holds queue viewer too slow to load for large numbers of holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We have a partner processing thousands of holds per day, per branch. At this number of holds, the script loads very slow if it manages to load at all. The primary slowdown is the individual fetch of the patron for each hold to be displayed. If we prefetch those patrons, the entire script should load much faster. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 76

[Bug 25328] New: Date formatting from JS - Remove tz handling
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25328 Bug ID: 25328 Summary: Date formatting from JS - Remove tz handling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: agustinmoyano(a)theke.io Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)bugs.koha-community.org, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 24455, 24980 After some discussion, I now believe timezone handling in JS is redundant, and should be removed. Dates that comes from the API are already converted to the corresponding timezone with dt_from_string, so there is no need for a second conversion here. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24455 [Bug 24455] Date formatting from JS https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24980 [Bug 24980] Date formatting from JS - use timezone only with dates with offset -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 35682] New: Provide ability to specify color in DB upgrades
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35682 Bug ID: 35682 Summary: Provide ability to specify color in DB upgrades 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: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 9567] Favorite reports per user
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9567 --- Comment #8 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- If a table was kept for something like this, it could go much further than just favorite reports. For example, lets call this the 'follow_me' table. Maybe the 'follow_me' table has the following columns: borrowerid | tableid | function | object - The borrowerid would be straight forward: who this is for. - The tableid would reference the table this has the effect on. So, for example, the 'table_reports' - The function in this case would be 'favorites' - The object would be the 'report_id'. The same 'follow_me' table could also be used down the road to record other settings you want to remain consistent wherever you go. So maybe you want some columns on the check-out table to be different than the default. - The borrowerid again indicates who this is for. - The tableid would reference the 'issues-table'. - The function would be maybe 'hide' if you want a particular column always hidden, or 'show' if you always want it to show. - The object would be a reference to the particular column, such as price. I'm not sure how the current columns are identified with the current settings, but you would probably use whatever is used in the settings already for consistency. Maybe a cataloger only wants to see certain shelving locations, instead of seeing everything available. Or maybe the desk and register could be saved in this table as well. I hope that makes sense. I'm just trying to think of a way something of this nature could be more useful and practical down the road for more than one thing. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9567] Favorite reports per user
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9567 --- Comment #7 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- (In reply to Cab Vinton from comment #2) > Here's a temporary workaround -- Use MySQL's comment syntax & a unique > string within the body of the report to identify favorite reports (initials, > passphrase, etc.) > > For example: > > /* JTG */ > > /* JTG FMV */ > > /* rugbytuna */ One major reason this doesn't work well is that it requires either everyone to have editing capabilities to mark a report as their favorite, or some poor editor person has to be the schmuck to do it for them. This work around works for me, but not for everyone else. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35680] New: YAML system preferences cause error if syspref data is not YAML string
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35680 Bug ID: 35680 Summary: YAML system preferences cause error if syspref data is not YAML string 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: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org If a YAML preference has a string instead of the expected format, it'll cause an error - tested with RisExportAdditionalFields and ILLModuleDisclaimerByType but I'm sure others may cause this too. To reproduce: 1) Add 'string' to RisExportAdditionalFields sys pref 2) Visit RIS export link: /cgi-bin/koha/opac-export.pl?op=export&bib=262&format=ris 3) Notice the error Can't use string ("string") as a HASH ref while "strict refs" in use at /kohadevbox/koha/C4/Ris.pm line 132 Not critical, but ideally an error like this should not happen in the event that a system preference has wrong data in it. Adding bug 33431 as "See also" even though it's not the cause of the issue - as the test plans info there may also help here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 33640] New: Adding new item group from item additem.pl does nothing
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33640 Bug ID: 33640 Summary: Adding new item group from item additem.pl does nothing 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: 1 - Browse to details page for a record 2 - Create or ensure the record has item group(s) 3 - Click New->New item 4. At the bottom of the page in the under Add to item group click the 'Options:' dropdown and select 'Create new item group'. 5. Add a name and click add item. 6. No item group is created. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19616] New: Formatted Contents Note (Marc 21 505), subfield g isn' t visible in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19616 Bug ID: 19616 Summary: Formatted Contents Note (Marc 21 505), subfield g isn't visible in the OPAC Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org The 505 field in Marc 21, Formatted Contents Note, includes subfield g "Miscellaneous information". According to the Marc 21 format for bibliographic data, it is used to record "volume, part, page numbering or other extent information such as dates". If you use it in Koha, this information isn't visible in the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 35