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

[Bug 35018] New: Welcome notice is no HTML
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35018 Bug ID: 35018 Summary: Welcome notice is no HTML Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org As it is marked as HTML, the resulting email is a glue of text. We could also check if there is an cardnumber instead of Your cardnumber is (followed by nothing) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 31029] New: ILL request ID in ILL history table should link to the ILL request if permissions allow for it
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31029 Bug ID: 31029 Summary: ILL request ID in ILL history table should link to the ILL request if permissions allow for it Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de When a patron has placed ILL requests, they are shown in the patron account in a new tab "ILL request history". >From this table, there is no way to get to the ILL request in the ILL module. We should link the request ID if the user has permissions to access the module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 13325] Add logs for budgets and funds
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13325 --- Comment #17 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to mathieu saby from comment #16) > Well, our vendor (Biblibre) told us not to activate the logs in general, but > we did not ask specifically if logging acquisition activities could impact > performances... > > Anyway, my colleagues asked recently for a way to *easily* track changes to > their funds by the acquisition coordinator (quite often at the end of the > year). We will give a try to the logging system, maybe it could suit our > needs, but I doubt that. It doesn't work right now. There is no logging implemented for fund changes, but only other acq activities. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 13325] Add logs for budgets and funds
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13325 --- Comment #16 from mathieu saby <mathsabypro(a)gmail.com> --- Well, our vendor (Biblibre) told us not to activate the logs in general, but we did not ask specifically if logging acquisition activities could impact performances... Anyway, my colleagues asked recently for a way to *easily* track changes to their funds by the acquisition coordinator (quite often at the end of the year). We will give a try to the logging system, maybe it could suit our needs, but I doubt that. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 32479] New: Replace sort: ~ by sort: 0 in mappings.yaml file
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32479 Bug ID: 32479 Summary: Replace sort: ~ by sort: 0 in mappings.yaml file Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com Bug 27316 removed the ability to have "Undef" as a sorting option. It is now either yes (1) or no (0). The default mappings.yaml file still contains a lot of sort: ~, which I assume is "Undef". I propose to change the ~ to 0 so that the mappings file is clean. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=34473 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 34504] New: Elasticsearch error when updating mappings
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34504 Bug ID: 34504 Summary: Elasticsearch error when updating mappings 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: michaela.sieber(a)kit.edu Since 23.05 it is not possible to add MARC fields to search fields in the Mapping table in staff interface. To recreate: Administration > Search engine configuration (Elasticsearch) Tab Bibliographic records: Add a new line , (e.g. abstract > 942v). See that in drop down for 'Sortable' you can select "1", "0", or "Undef" instead of "Yes" or "No". Click the "Add" Button - the line appears (last entry) Save. Error Message: " You attempted to delete all mappings for a required index, you must leave at least one mapping An error occurred when updating mappings: . " -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 7827] After creating a new biblio to be used in a subscription, the subscription entry form should be populated with the biblionumber
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7827 --- Comment #3 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I just tested this and the biblionumber was not sent back to the form when closing the window. 1) Add new subscription 2) Create record link 3) Downloaded a record from Z39.50 4) Fixed errors 5) Saved 6) Went to item form, instead of closing 7) Closing window manually - biblionumber remains empty. If this is not supposed to work, maybe we should open the cataloguing form in a new tab instead. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32699] New: Patron browse 'forgets' how many entries to show
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32699 Bug ID: 32699 Summary: Patron browse 'forgets' how many entries to show Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dch(a)interleaf.ie QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you change the number of entries to show in member.pl, then select one entry to view, when you return to the list it reverts to just showing the default 20 entries. It should show the number of entries you had previously selected -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 34606] New: Advanced editor doesn't populate framework defaults when creating a new record
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '23

29 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34606 Bug ID: 34606 Summary: Advanced editor doesn't populate framework defaults when creating a new record Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you have most recently used the advanced editor and on the cataloging home screen select "New Record" and a framework, the framework becomes default in the advanced editor and none of the defaults fill. I'm not sure if the better fix for users would be: 1. Have the framework fill those fields 2. Always open those framework links in the basic editor 3. Something else entirely. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1