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

[Bug 34962] New: Add a system messages feature to Koha to report issues and failures in a more visible way
by bugzilla-daemon＠bugs.koha-community.org 15 Dec '24

15 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34962 Bug ID: 34962 Summary: Add a system messages feature to Koha to report issues and failures in a more visible way 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Many web projects have a "system messages" area to report cron failures and things like that. These messages are often dismissable. I think it would be great to have a "system messages" table that we could insert things into to make staff aware that something has failed. What I'm imagining is something like wrapping cronjob code in a try/catch and reporting cronjob failures. This would dovetail with action logs. Action logs lot you got searching for issues. This would put the issue right in front of you and would be trigger by actual failures. It could be used to report records with malformed MARC. It could be used to report items that are missing a required field that Koha assumes exists to function, and so on. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 29731] New: UNIMARC 100$a 17-19 Target Audience Code
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '24

14 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29731 Bug ID: 29731 Summary: UNIMARC 100$a 17-19 Target Audience Code Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org Problem UNIMARC 100 $a/17-19 Target Audience Code It is not possible to use the "#" symbol. Unused positions are filled with space characters "#". For example, when you need to use "x##". https://cdn.ifla.org/wp-content/uploads/files/assets/uca/unimarc_updates/BI… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 30547] New: Plugin for coded data 123p UNIMARC
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '24

14 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30547 Bug ID: 30547 Summary: Plugin for coded data 123p UNIMARC 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: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org Please, add plugin for coded data 123p UNIMARC $p Planet (Mandatory for planets other than Earth, Not repeatable) $p/0-1 Planet ea Earth ju Jupiter ma Mars me Mercury ne Neptune pl Pluto sa Saturn ur Uranus ve Venus zz Other $p/2 Satellite s The body whose co-ordinates are recorded in subfields $d-$g is a satellite of the planet coded on pos. 0-1. y Not applicable: the body whose co-ordinates are recorded in subfields $d-$g is the planet itself, as coded on pos. 0-1. https://archive.ifla.org/VI/8/unimarc-concise-bibliographic-format-2008.pdf -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 35409] New: patrons.pref#MaxFine#
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '24

14 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35409 Bug ID: 35409 Summary: patrons.pref#MaxFine# Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: translate.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org Does it make sense to translate such phrases? patrons.pref#MaxFine# [% local_currency %]. Maybe it makes sense not to add this to the translation? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 37719] New: Add to item group only displays on additem.pl if there is already a group
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37719 Bug ID: 37719 Summary: Add to item group only displays on additem.pl if there is already a group Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: 1 - Enable item groups 2 - Find a record with no group 3 - Add an item - no group options 4 - Add a group to the record 5 - Add an item - cna now add to existing group or new group It should be possible to create a new group when adding an item if none exist -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37416] New: Holdings table 500 errors in the staff interface - how to identify cause and possible solution
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37416 Bug ID: 37416 Summary: Holdings table 500 errors in the staff interface - how to identify cause and possible solution Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Bug 33568 (Use the REST API to display items on the biblio detail view) changed the way the holdings table for a record in the staff interface is generated. There are reports in Chat and on the mailing list about getting 500 errors after an upgrade to 24.05. I think it would be useful to: - Provide some information to help libraries troubleshoot what is causing the error - Identify possible solutions to fix the cause of the issue, including where it is item data issues - Identify any bugs -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38

[Bug 38128] New: Agreement/License user selection not limited to users with erm permissions
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38128 Bug ID: 38128 Summary: Agreement/License user selection not limited to users with erm permissions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com The manual says that the user selection in ERM agreements and licences are limited to patrons with erm permissions. This is no longer true. I don't know if it is intentional, or a simple omission (possibly from Bug 35329). It made sense to limit the patron search this way, I think. To get there: 1. Enable ERMModule 2. Go to E-resource management > Agreement > New agreement 3. Click 'Add new user' 4. Click 'Select user' 5. Search for alford (for example) --> Jordan Alford is in the results, even if they don't have erm permissions 6. Go to Licences > New licence 7. Repeat steps 3-5 --> Jordan Alford is in the results, even if they don't have erm permissions I tried on a local 23.05 installation and Jordan Alford is not in the results, because they don't have erm permissions. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 26314] New: "Volumes: show volumes" showing regardless of whether there are volumes linked to the record
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26314 Bug ID: 26314 Summary: "Volumes: show volumes" showing regardless of whether there are volumes linked to the record 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 15851 When cataloguing multi part records with sets and volumes, we currently show a link to "Show volumes" on the set record. The link is always shown on a set record, even if there are no linked volumes. Bug 15851 solves the same issue for analytics. volumes would be a great next step. At the moment Show volumes is only shown on monographs, but we could add the feature for serial records as well. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15851 [Bug 15851] "Analytics: Show analytics" showing regardless of whether they have analytics -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 98

[Bug 35099] New: Cannot load records with invalid marcxml
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35099 Bug ID: 35099 Summary: Cannot load records with invalid marcxml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org After bug 26314 we cannot load records with marcxml issues - the get_volumes_query calls Koha::Biblio->metadata->record and does not catch the exception -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 35330] New: Split rcn index to allow for more specific searches
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35330 Bug ID: 35330 Summary: Split rcn index to allow for more specific searches 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 26314 At the moment the index on Record control-number (7xx$w, 8xx$w) includes the $w subfields of multiple linking fields. This means that we can't specify a search that only find a specific type of link. Example: * Finding all volumes linked to a set record, will also find records that are also linked as another physical form (776) or a preceding entry (780) It would be nice to have the general, but also more specific indexes limited to the relevant $w only. As features like bug 26314 use the indexes in internal functions to do searches in the background, we cannot easily solve this with local changes to indexing and XSLT. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26314 [Bug 26314] "Volumes: show volumes" showing regardless of whether there are volumes linked to the record -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1