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

[Bug 37527] New: Fix grammar in UpdateNotForLoanStatusOnCheckin example
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37527 Bug ID: 37527 Summary: Fix grammar in UpdateNotForLoanStatusOnCheckin example Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In Administration > System preferences, UpdateNotForLoanStatusOnCheckin currently has an example with the following explanation: "When an item is checked in, if it's item type matches CR then when the value on the left (1) matches the items' not for loan value it will be updated to the value on the right." It should be corrected to say: "When an item is checked in, if its item type matches CR and its not for loan value matches the value on the left (1), then the item's not for loan value will be updated to the value on the right." -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37170] New: Elasticsearch is functioning correctly with indices being rebuilt and searchable, but the "About Koha" page incorrectly shows Elasticsearch as "not running."
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37170 Bug ID: 37170 Summary: Elasticsearch is functioning correctly with indices being rebuilt and searchable, but the "About Koha" page incorrectly shows Elasticsearch as "not running." Change sponsored?: --- Product: Koha Version: 24.05 Hardware: Macintosh OS: Other Status: NEW Severity: critical Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aungmo(a)gmail.com I am experiencing an issue with the Koha "About Koha" page. Although Elasticsearch is functioning correctly (indices are being rebuilt, and records are searchable), the "About Koha" page displays Elasticsearch status as "not running." Steps to Reproduce: Set up Koha with Elasticsearch as the search engine. Successfully rebuild Elasticsearch indices using the command: docker exec -it koha koha-elasticsearch --rebuild --verbose -d mylibrary [436] Checking state of biblios index [436] Dropping and recreating biblios index [436] Checking state of authorities index [436] Dropping and recreating authorities index [436] Indexing biblios [436] Committing final records... [436] Total 1 records indexed [436] Indexing authorities [436] Committing final records... [436] Total 1 records indexed Perform searches in both OPAC and Staff interfaces, confirming that records are searchable. Navigate to the "About Koha" page. Expected Behavior: The "About Koha" page should display the Elasticsearch version, number of nodes, and status as running. Actual Behavior: The "About Koha" page displays: Elasticsearch: Version: | Nodes: | Status: not running System Information Koha version: 24.05.01.000 OS version: Linux 96b981d24116 6.6.31-linuxkit (running on macOS) Perl version: 5.036000 MySQL version: 10.6.18-MariaDB-ubu2004 Apache version: 2.4.59 (Debian) Elasticsearch version: 8.13.0 (single-node cluster) Deployment method: Docker Base image: debian Elasticsearch Configuration in koha-conf.xml: <elasticsearch> <server>elasticsearch:9200</server>  <index_name>koha_mylibrary</index_name>   <cxn_pool>Static</cxn_pool>   </elasticsearch> docker exec -it koha curl -X GET "http://elasticsearch:9200/_cluster/health?pretty" { "cluster_name" : "docker-cluster", "status" : "yellow", "timed_out" : false, "number_of_nodes" : 1, "number_of_data_nodes" : 1, "active_primary_shards" : 10, "active_shards" : 10, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 10, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 0, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 0, "active_shards_percent_as_number" : 50.0 } -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 37521] New: KOHA ERM REPORT CANNOT BE AUTOMATED
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37521 Bug ID: 37521 Summary: KOHA ERM REPORT CANNOT BE AUTOMATED Change sponsored?: --- Product: Koha Version: 23.11 Hardware: HP OS: Windows Status: NEW Severity: major Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: belal.ahmadi(a)uwl.ac.uk 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 Hi, I wanted to automate koha ERM reports which are different from the normal custom reports that extract data from the tables. The reports on ERM can neither be automated nor the query for the report can be accessed. If the developers could add a feature to automate ERM eUsage reports, that would be ideal and very much appreciated. Best regards -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 37520] New: [DOCS] Review and update record overlay rules
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37520 Bug ID: 37520 Summary: [DOCS] Review and update record overlay rules Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de The record overlay rules section (https://koha-community.org/manual/latest/en/html/administration.html#record…) needs reviewing and updating to make sure it is current (I find it a difficult topic to get my head around). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 35155] New: MARCOverlayRules syspref not in manual
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35155 Bug ID: 35155 Summary: MARCOverlayRules syspref not in manual Change sponsored?: --- Product: Koha Version: unspecified Hardware: All URL: https://gitlab.com/gnucifer/koha-manual/-/commit/593c5 da008dbc4b074cac9dee167cce9a6dfc250#c5e2c75dc923f21c5b 95185b2f350df00fec661f OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 14957 MARCOverlayRules system pref and functionality introduced in 21.11 never made it into Koha manual. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 [Bug 14957] Write protecting MARC fields based on source of import -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |37520 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37520 [Bug 37520] [DOCS] Review and update record overlay rules -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25610] New: Inconsistent display of 856$3 in OPAC between brief result and full record
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25610 Bug ID: 25610 Summary: Inconsistent display of 856$3 in OPAC between brief result and full record 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, if a record has an 856$3, this will show in the brief results and not in the full results. It should be consistent between the two views. And what is the opinion that the $3 should show or should not? For decisions like these, it would be nice for the library to decide what is displayed and allow for changes to be made through the staff client vs XSLT stylesheets. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 36194] New: CSRF - svc
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36194 Bug ID: 36194 Summary: CSRF - svc Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This bug is for tracking follow-ups missed in the initial review. Please see the "svc" section on the framapad here: https://annuel.framapad.org/p/koha_34478_remaining Additional entries can be added there, and should be crossed out when completed Patches should be attached here This bug can be closed when that section of the pad is empty see bug 36084 commits for new method using fetch/api-client.js is retrieved (and adjusted) from the Vue work wiki/coding guideline to follow -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 36956] New: ERM eUsage reports : only the first 20 data providers are listed when creating a new report
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36956 Bug ID: 36956 Summary: ERM eUsage reports : only the first 20 data providers are listed when creating a new report Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: michaela.sieber(a)kit.edu 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 to reproduce: 1.) Go to ERM module and make sure you have more than 21 data providers stored in your database. 2.) Go to eUsage / reports and create new report (cgi-bin/koha/erm/eusage/reports) 3.) Check that only the first 20 data providers are displayed in the drop down -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 35942] OPAC user can enroll several times to the same club
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '24

29 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35942 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Text to go in the| |This fixes patron club release notes| |enrollment to prevent | |patrons from enrolling | |multiple times in the same | |club. There was no visible | |option in a patron's OPAC | |account to do this (Summary | |> Clubs), but it could be | |achieved by directly | |accessing the URL | |(/cgi-bin/koha/svc/club/enr | |oll?id={clubid}). CC| |david(a)davidnind.com --- Comment #23 from David Nind <david(a)davidnind.com> --- This fixes patron club enrolment from their account in the OPAC. They can now only enroll in a club once. -- You are receiving this mail because: You are watching all bug changes.

1 0