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

[Bug 34056] New: authorised-values API client file is missing -api-client suffix
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34056 Bug ID: 34056 Summary: authorised-values API client file is missing -api-client suffix Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 32983 Blocks: 34055 In koha-tmpl/intranet-tmpl/prog/js/vue/fetch all files have the -api-client suffix but authorised-values. For consistency we should add it. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32983 [Bug 32983] Use REST API route to retrieve authorised values https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34055 [Bug 34055] Add API client class to get items -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 33978] New: Adding authority from automatic linker closes imported record
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33978 Bug ID: 33978 Summary: Adding authority from automatic linker closes imported record Change sponsored?: --- Product: Koha Version: unspecified 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 152266 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=152266&action=e… 2 example records If you import a record, then create an authority record using the automatic linker, it closes the biblio record. The biblio record should stay open so you can continue to edit it. To recreate: 1. Import the example records 1.1. Download the example records 1.2. Go to Cataloging > Stage records for import 1.3. Choose the downloaded file 1.4. Click Upload file 1.5. Click Stage for import 1.6. Click View batch 1.7. Click Import this batch into the catalog 1.8. Click View detail of the enqueued job 1.9. Click Manage imported batch Correct behaviour: 2. In another tab, search for one of the records (for example, Fafounet) 3. Click Edit > Edit record 4. Click Link authorities automatically --> It should say 100 - No matching authority found. 5. Go to field 100 6. Click the plus sign next to 100$9 7. Fill out the mandatory fields by clinking in the text fields (000, 003, 005, 008, 040$a), field 100$a should already be filled 8. Click 'Save' --> Authority number is added in 100$9 and you get to stay in the record for more edits if needed Incorrect behaviour: 9. Go back to the imported batch tab 10. Click Edit next to the second title (the one by Paventi, Eza) 11. Redo steps 4 to 8 --> Record is closed!! :( The behaviour should be the same, stay in the bibliographic record until it is saved. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 33755] New: Profile used is not saved when importing records
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33755 Bug ID: 33755 Summary: Profile used is not saved when importing records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial 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 Before 22.11 if you selected a profile when staging marc records for import, when you went to see staged records it would show which profile was used both in the table and in the batch details. Post 22.11, if you select a profile, it saves the selections but doesn't save which profile was used. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 33140] New: Use facet label value in mouseover title attribute of facet removal link
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33140 Bug ID: 33140 Summary: Use facet label value in mouseover title attribute of facet removal link Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org The mouseover text for the remove link displays the link value of the facet rather than its label. (In koha-tmpl/intranet-tmpl/prog/en/includes/facets.inc and koha-tmpl/opac-tmpl/bootstrap/en/includes/opac-facets.inc b/koha-tmpl/opac-tmpl/bootstrap/en/includes/opac-facets.inc). Logically, it is always the label value that should be displayed to the user so this should also be used for the title attribute. For instance for a custom boolean valued facet one do not want to see the text "remove the facet true" when hovering on the link. (See bug 33139.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 31667] New: Merge 'tip' and 'hint' classes
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31667 Bug ID: 31667 Summary: Merge 'tip' and 'hint' classes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org 'tip' and 'hint' are classes for a CSS with grey color. Looks like 'hint' is way more used that 'tip' (mainly used for header search boxes). I think we should replace 'tip' with 'hint' to have only one class for this usage. And maybe add a coding guide line. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 34108] New: When items are added on receive, item selection gets lost on editing items
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34108 Bug ID: 34108 Summary: When items are added on receive, item selection gets lost on editing items Change sponsored?: --- Product: Koha Version: 22.11 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 Depends on: 8179 When items are added on receive, you can either set the checkboxes in the item form, or use the quantity received to set them. Then you can edit the selected items using the link in the items table. With the new multi-receive work, the checkboxes are lost between being sent to the item form and returning. If you are editing a bigger amount of items, this can be quite tedious and should not happen as sometimes it matters which items are picked (for a specific library, for a specific location etc. for partial deliveries) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8179 [Bug 8179] Receiving multiple order lines at once -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 33964] New: Use Email::Sender::Transport::SMTP::Persistent for sending email
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33964 Bug ID: 33964 Summary: Use Email::Sender::Transport::SMTP::Persistent for sending email 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 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38

[Bug 33286] New: 'Catalog record' should be 'Bibliographic record'
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33286 Bug ID: 33286 Summary: 'Catalog record' should be 'Bibliographic record' 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I noticed in the new 'report a concern' feature, we talk about 'catalog records'. This is not a term used anywhere in Koha. The feature doesn't seem to apply to authority records, so I think we should change it to 'bibliographic records'. To replicate: 1. Go to Administration > Global system preferences 2. Search for 'concern' --> The description for CatalogConcerns is "Allow/Don't allow staff to report concerns about catalog records." (should be "[...] about bibliographic records.") --> The description for OpacCatalogConcerns is "Allow/Don't allow OPAC users to report concerns about catalog records." (should be "[...] about bibliographic records." I didn't check elsewhere yet... Just getting into documenting this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 26543] New: Elasticsearch - Importing biblios with multiple items can cause incorrect index
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26543 Bug ID: 26543 Summary: Elasticsearch - Importing biblios with multiple items can cause incorrect index Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Similar to bug 25265 we see many request for indexing a single biblio with multiple items attached when importing and matching records Additionally, the current code repeatedly generates an indexer object, we can reuse the single object to avoid creating multiple connections -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 30822] New: BatchCommit does not deal with indexation correctly
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '23

18 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30822 Bug ID: 30822 Summary: BatchCommit does not deal with indexation correctly Change sponsored?: --- Product: Koha Version: unspecified 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: dcook(a)prosentient.com.au, fridolin.somers(a)biblibre.com, jonathan.druart+koha(a)gmail.com, julian.maurice(a)biblibre.com, kyle(a)bywatersolutions.com, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 27344 Blocks: 27341 AddBiblio must implement skip_index and we should update the search engine's index after all the biblio records have been imported. This also applies for bulkmarcimport. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27341 [Bug 27341] Performance 21.05 - Omnibus https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27344 [Bug 27344] Implement Elastic's update_index_background using Koha::BackgroundJob -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38