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

[Bug 32928] New: Filters missing in SQL builder on Orders::filter_by_active
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '24

04 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32928 Bug ID: 32928 Summary: Filters missing in SQL builder on Orders::filter_by_active Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Since version 21.xx.xx there has been a change in the way to retrieve the data of the orders to receive. The table is built from a call to the API and then the data can be filtered. Bug_20212 has integrated this change. This is a good thing but two filters are missing on the query construction in the Koha::Acquisition::Orders::filter_by_active function Here is the query in version 20.11 : <pre> SELECT aqbasket.basketno, borrowers.surname, borrowers.firstname, biblio.*, biblioitems.isbn, biblioitems.biblioitemnumber, biblioitems.publishercode, biblioitems.publicationyear, aqbasket.authorisedby, aqbasket.booksellerid, aqbasket.closedate, aqbasket.creationdate, aqbasket.basketname, aqbasketgroups.id as basketgroupid, aqbasketgroups.name as basketgroupname, aqorders.* FROM aqorders LEFT JOIN aqbasket ON aqorders.basketno = aqbasket.basketno LEFT JOIN aqbasketgroups ON aqbasket.basketgroupid = aqbasketgroups.id LEFT JOIN borrowers ON aqbasket.authorisedby=borrowers.borrowernumber LEFT JOIN biblio ON aqorders.biblionumber=biblio.biblionumber LEFT JOIN biblioitems ON biblioitems.biblionumber=biblio.biblionumber WHERE (datecancellationprinted is NULL) AND ( ( aqbasket.is_standing AND aqorders.orderstatus IN ( "new", "ordered", "partial" ) ) OR ( ( quantity > quantityreceived OR quantityreceived is NULL ) AND aqorders.orderstatus IN ( "ordered", "partial" ) ) ) AND aqbasket.booksellerid = ? ORDER BY aqbasket.basketno'; </pre> The condition "datecancellationprinted is NULL" is missing as well as the quantity control to display the results only if there are still quantities to receive. And so the result on the same database between the different versions can be very different! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 21114] New: Select multiple item rows with Ctrl+click and Shift+click
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '24

04 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21114 Bug ID: 21114 Summary: Select multiple item rows with Ctrl+click and Shift+click Change sponsored?: --- Product: Koha Version: unspecified Hardware: PC OS: Windows Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dimantonak(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, if you want to select multiple items in "Edit items in batch" you have to click (check) per item. It would be great and time saving to add the ability to multiple select the items using Ctrl+click and Shift+click using some javascript code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 26392] New: Wrap all translatable strings in opac-main.tt
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '24

04 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26392 Bug ID: 26392 Summary: Wrap all translatable strings in opac-main.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Blocks: 20988 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20988 [Bug 20988] Internationalization: wrap all translatable text inside t() calls -- You are receiving this mail because: You are watching all bug changes.

1 55

[Bug 20988] New: Internationalization: wrap all translatable text inside t() calls
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '24

04 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20988 Bug ID: 20988 Summary: Internationalization: wrap all translatable text inside t() calls Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 15395 Bug 15395's Koha::I18n is working well, but it is basically useless until we wrap all the translatable strings inside __*() calls (or t*() calls inside templates). This bug aims to do that. I wrote a little tool to automatically find and replace translatable text by the corresponding call. It can be found here : https://github.com/jajm/koha-i18n. This bug will hold a few patches that will make koha-i18n work better and I'll try to attach all the changes it does. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15395 [Bug 15395] Internationalization: plural forms, context, and more -- You are receiving this mail because: You are watching all bug changes.

1 81

[Bug 38209] New: Add a vendor language field
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '24

04 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38209 Bug ID: 38209 Summary: Add a vendor language field Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be useful to be able to identify the primary language used by a vendor -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 34113] New: OMNIBUS: Replace the use of jQueryUI autocomplete
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '24

04 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34113 Bug ID: 34113 Summary: OMNIBUS: Replace the use of jQueryUI autocomplete Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 29222 As discussed in Bug 29222, jQueryUI autocomplete should be replaced. The last time I checked it was used in these places: - Checkout and patron header searches - Article request patron search - Course reserve instructor search - Holds patron search - UNIMARC 210c plugin - UNIMARC 225a plugin Possible replacement candidate: https://tarekraafat.github.io/autoComplete.js/. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29222 [Bug 29222] OMNIBUS: Replace the use of jQueryUI -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 35109] New: Inconsistencies when a task is added to background jobs
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '24

03 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35109 Bug ID: 35109 Summary: Inconsistencies when a task is added to background jobs Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 The way the interface informs the user that what they just did was added to a background job is inconsistent throughout Koha. I wrote how to get to each type of job and what it does below, but here are the highlights: - The message is almost always on a new page, except when creating local titles in ERM or cancelling holds - The message is always "The job has been enqueued! It will be processed as soon as possible." except when creating local titles in ERM module - The link to the job is always "View details of enqueued job" except when creating local titles in ERM module - There is sometimes a link to do a new batch or return to where we were before in the blue message box, sometimes it is underneath the box, sometimes it is a button instead of a link (and sometimes all three at the same time) - There is never a progress bar except when staging records - There is almost never a redirection to job details when the job is done except when importing records or reverting an import Proposed changes (open to discussion): - Put the message on a new page when importing eHolding titles, with a link/button to go back - Put the message on a new page when canceling holds, with a link/button to go back - Put the message on a new page when cancelling holds, with a link/button to go back - Change message when importing eHolding titles to "The job has been enqueued! It will be processed as soon as possible." - Change the link when importing eHolding titles to "View details of enqueued job" - Choose either a link in the message box, a link under the message box or a button to return to where we were or make a new batch, but not all three, and make it consistent - If possible add a link to go back where there is none - Choose either to have a progress bar or not (I prefer the progress bar personally) and make it consistent - Choose to redirect automatically or not (I prefer redirection, fewer clicks) and make it consistent, although this might depend on the workflow - Place 'View batch' link next to the view detail link when staging records I can also make separate bug reports if needed, but I thought it interesting to have them all in one to compare and see the differences. ----- Batch bibliographic record modification - Message on new page - Message: The job has been enqueued! It will be processed as soon as possible. - Link to View details of enqueued job - Link to New batch record modification (next to the view detail link) - No progress bar - No redirection after the job is finished To recreate: 1. Create a MARC modification template (if you already have one, you can skip this step) 1.1. Go to Cataloging > MARC modification templates 1.2. Click New template 1.3. Give a name to the template 1.4. Click Submit 1.5. Click New action 1.6. Create a simple action, for example, Add new field(s) 500 a with value TEST 1.7. Click Add action 2. Batch modify a record 2.1. Search the catalog for a record 2.2. If necessary, click the title to access the detailed record 2.3. Click Edit > Modifiy record using template 2.4. Select the template created previously 2.5. Click Modify selected records 3. Wait a bit, if necessary, open the job details in another tab to verify the job is complete ----- Batch bibliographic record deletion - Message on new page - Message: The job has been enqueued! It will be processed as soon as possible. - Link to View details of enqueued job - Link to New batch record deletion (next to the view detail link) - No progress bar - No redirection after the job is finished To recreate: 1. Go to Cataloging > Batch record deletion 2. Fill out the form - Record type: Bibliographic - Tab: Enter a list of record numbers - IDs: enter one or two biblionumbers (I used 1 and 2) 3. Click Continue 4. Click Delete selected records 5. Wait a bit, if necessary, open the job details in another tab to verify the job is complete ----- Batch authority record modification - Message on new page - Message: The job has been enqueued! It will be processed as soon as possible. - Link to View details of enqueued job - Link to New batch record modification (next to the view detail link) - No progress bar - No redirection after the job is finished To recreate: 1. Create a MARC modification template (if you already have one, you can skip this step) 1.1. Go to Cataloging > MARC modification templates 1.2. Click New template 1.3. Give a name to the template 1.4. Click Submit 1.5. Click New action 1.6. Create a simple action, for example, Add new field(s) 667 a with value TEST 1.7. Click Add action 2. Batch modify a record 2.1. Go to Cataloging > Batch record modification 2.2. Fill out the form - Record type: Authority records - Tab: Enter a list of record numbers - IDs: enter one or two auth_id (I used 1 and 2) - Template: select the template created previously 2.3. Click Continue 2.4. Click Modify selected records 3. Wait a bit, if necessary, open the job details in another tab to verify the job is complete ----- Batch authority record deletion - Message on new page - Message: The job has been enqueued! It will be processed as soon as possible. - Link to View details of enqueued job - Link to New batch record deletion (next to the view details link) - No progress bar - No redirection after the job is finished To recreate: 1. Go to Cataloging > Batch record deletion 2. Fill out the form - Record type: Authorities - Tab: Enter a list of record numbers - IDs: enter one or two biblionumbers (I used 3 and 4) 3. Click Continue 4. Click Delete selected records 5. Wait a bit, if necessary, open the job details in another tab to verify the job is complete ----- Batch item record modification - Message on new page - Message: The job has been enqueued! It will be processed as soon as possible. - Link to View detail of the enqueued job - Link to New batch item modification (next to the view details link) - If done from the tool, Link to Return to batch item modification under the box (redundant with link to New batch item modification inside the message box) - If done from the tool, Button to Return to batch item modification under the box (redundant with link) - If done from a single record, Link to return to the record under the box (redundant with button) - If done from a single record, Button to return to the record under the box (redundant with link) - No progress bar - No redirection after the job is finished To recreate (from tool): 1. Create a report to get a couple of itemnumbers 1.1. Go to Reports > Create from SQL 1.2. Enter a report name (e.g. items) 1.3. In the SQL box, enter a query that will return a couple of itemnumbers, for example select itemnumber from items limit 3 1.4. Click Save report 1.5. Click Run report 2. Click Batch operations with X visible records > Batch item modification 3. Change something in the record form (for example, change Withdrawn status to Withdrawn) 4. Click Save 5. Wait a bit, if necessary, open the job details in another tab to verify the job is complete To recreate (single record): 1. Search the catalog for a record 2. If necessary, click the title to access the detailed record 3. Check the box next to one or more items 4. Click Modify selected items 5. Change something in the record form (for example, change Withdrawn status to Withdrawn) 6. Click Save 7. Wait a bit, if necessary, open the job details in another tab to verify the job is complete ----- Batch item record deletion - Message on new page - Message: The job has been enqueued! It will be processed as soon as possible. - Link to View detail of the enqueued job - Link to New batch item deletion (next to the view detail link) - If done from the tool, Link to Return to batch item deletion under the box (redundant with link in the message box) - If done from a single record, Link to return to the record under the box - No progress bar - No redirection after the job is finished To recreate (from tool): 1. Create a report to get a couple of itemnumbers (skip if already done) 1.1. Go to Reports > Create from SQL 1.2. Enter a report name (e.g. items) 1.3. In the SQL box, enter a query that will return a couple of itemnumbers, for example select itemnumber from items limit 3 1.4. Click Save report 1.5. Click Run report 2. Click Batch operations with X visible records > Batch item deletion 3. Click Delete selected items 5. Wait a bit, if necessary, open the job details in another tab to verify the job is complete To recreate (single record): 1. Search the catalog for a record 2. If necessary, click the title to access the detailed record 3. Check the box next to one or more items 4. Click Delete selected items 5. Click Delete selected items 7. Wait a bit, if necessary, open the job details in another tab to verify the job is complete ----- Batch hold cancellation - Message on the holds page - Message: The job has been enqueued! It will be processed as soon as possible. - Link to View detail of the enqueued job - No progress bar - No redirection after the job is finished To recreate: 1. Place a hold on a title 1.1. Search the catalog for a record 1.2. If necessary, click the title to access the detailed record 1.3. Click Holds 1.4. Find a patron (either enter a name, cardnumber or click a letter) and click on their name 1.5. Click Place hold 2. 'Batch' cancel the hold 2.1. Check the box next to the hold 2.2. Click Cancel selected 3. Wait a bit, if necessary, open the job details in another tab to verify the job is complete ----- Create eHolding titles - Message on import page - Message: Import in progress - Link to see job #XX - No progress bar - No redirection after the job is finished To recreate: 1. Enable ERMModule 2. Create a list 2.1. Go to Lists 2.2. Click New list 2.3. Enter a name for the list 2.4. Click Save 3. Add titles to the list 3.1. Search the catalog 3.2. Select one or more records by checking the boxes next to them 3.3. Click Add to list and choose the list name 3.4. Click Save 4. Create a local package 4.1. Go to E-resource management > Local > Packages 4.2. Click New package 4.3. Enter a package name 4.4. Click Submit 5. Import the list of titles in ERM 5.1. Go to E-resource management > Local > Titles 5.2. Click Import from list 5.3. Click Import next to the list 6. Wait a bit, if necessary, open the job details in another tab to verify the job is complete ----- Update Elasticsearch index I don't think there is anything in the staff interface that the user can see for this one. ----- Holds queue update I don't think there is anything in the staff interface that the user can see for this one. ----- Staged MARC records for import - Message on new page - Message: The job has been enqueued! It will be processed as soon as possible. - Progress bar - Link to View detail of the enqueued job - Link to View batch (under the view detail link) - No redirection after the job is finished To recreate: 1. Go to Cataloging > Stage record for import 2. Click Choose file (or Browse) and choose a MARC file (if you don't have any, you can download on first from the catalog by going to the detailed record and click Save > MARC (Unicode/UTF-8)) 3. Click Upload file 4. Click Stage for import 5. Wait a bit, if necessary, open the job details in another tab to verify the job is complete ----- Import MARC records - Message on new page - Message: The job has been enqueued! It will be processed as soon as possible. - Link to View detail of the enqueued job - No progress bar - Redirection to job details when the job is finished To recreate: 1. Stage records (see steps above) 2. Click View batch, or go to Cataloging > Manage staged records and click on the file name) 3. Click Import this batch into the catalog 4. Wait a bit, you should be redirected ----- Revert import MARC records - Message on new page - Message: The job has been enqueued! It will be processed as soon as possible. - Link to View detail of the enqueued job - No progress bar - Redirection to job details (before it is even finished?) To recreate: 1. Stage and import records (see steps above) 2. Click Manage imported batch, or go to Cataloging > Manage staged records and click on the file name) 3. Click Undo import into catalog 4. Confirm -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 36905] New: Terminology: home locations / home collections
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '24

03 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36905 Bug ID: 36905 Summary: Terminology: home locations / home collections Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Show more home collections Show more home locations Show more home languages I think they should not have the home included? Same for the "Show fewer" koha-tmpl/opac-tmpl/bootstrap/en/includes/opac-facets.inc:124 -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 37672] New: V1/RecordSources.pm should use more helpers
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '24

03 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37672 Bug ID: 37672 Summary: V1/RecordSources.pm should use more helpers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 36495 was introduced and merged and bug 35919 didn't get adapted to it before getting merged. This is a minor thing but should be fixed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 28806] New: Labels exported as PDF create zero sized PDF files.
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '24

01 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28806 Bug ID: 28806 Summary: Labels exported as PDF create zero sized PDF files. Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org In my first tries to create biblio labels, I see that export to PDF creates zero sized PDF files, in both individual/single and batch modes. Coult it be due to non-latin characters (Greek) appearing in the label contents? Export to CSV does produce files with the expected number of rows, albeit with non-usable characters. -- You are receiving this mail because: You are watching all bug changes.

1 33