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

[Bug 17787] New: Suppressed items seems so still be included in number of search results
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '23

28 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17787 Bug ID: 17787 Summary: Suppressed items seems so still be included in number of search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: viktor.sarge(a)regionhalland.se QA Contact: testopia(a)bugs.koha-community.org We have a use case where like 99% of the collection is hidden and only a few selected items are displayed in the opac (by showing their covers up front on the main page). When going to the detail page and clicking the link for an author that has a long list of records (but only one visible in the opac) I might get indication of 63 hits in the search results and a the links to pages 1,2,3 etc for search results. Only problem is that there is actually only one result since the rest are suppressed. My guess is that the code calculating the number of hits and creating links to the pages of search results is not talking to the suppression system. I could not find any open bugs about this. Perhaps because our use of suppression is a bit of a edge case(?) I ended up "solving" the problem by removing the links on author etc. since we don't use search anyhow. I'll likely not research the issue further, but I felt I should at least report it and keep an eye out. All input is welcome. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 31248] New: Make checkout history table responsive for mobile
by bugzilla-daemon＠bugs.koha-community.org 27 Jul '23

27 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31248 Bug ID: 31248 Summary: Make checkout history table responsive for mobile Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 138180 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=138180&action=e… Screenshot of checkout history in mobile view on Firefox The checkout history table on mobile is large and there doesn't seem to be a way to scroll right. When on mobile, the current checkouts are not in a table, maybe the same could be done with the checkout history? To test: 1) Make sure you have checkouts in your account 2) Log into the OPAC --> In 'Your summary' current checkouts are in a table 3) Go to 'You checkout history' --> Current and previous checkouts are in a table 4) Switch to mobile view (in Firefox, Ctrl + Shift + M) --> Checkout history is still in a table and the last column is not entirely visible (depending on the content of the columns, I suppose) 5) Go to 'Your summary' --> Current checkouts are presented in list form instead of a table -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 19192] New: Update default DUEDGST and PREDUEDGST notices
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19192 Bug ID: 19192 Summary: Update default DUEDGST and PREDUEDGST notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The current default digest notices are DUEDGST You have <<count>> items due PREDUEDGST You have <<count>> items due soon These are not terribly useful defaults -- the whole reason for having digest notices is to display item detail for items which are due or coming due. I suggest the following instead: DUEDGST Dear <<borrowers.firstname>> <<borrowers.surname>>, You have <<count>> items due: <<items.content>> PREDUEDGST Dear <<borrowers.firstname>> <<borrowers.surname>>, You have <<count>> items due soon: <<items.content>> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 29248] New: Manual 21.05 - 'position' missing in syspref UNIMARCAuthorityField100
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29248 Bug ID: 29248 Summary: Manual 21.05 - 'position' missing in syspref UNIMARCAuthorityField100 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: e.betemps(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, Translating syspref in this manual, I think some positions are missing Emplacements : ../../source/authoritiespreferences.rst:189 Asks: Use the following text for the contents of UNIMARC authority field 100 position ??? (fixed length data elements). have a nice day, Manu. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26228] New: Update gulpfile to work with Node.js v12
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26228 Bug ID: 26228 Summary: Update gulpfile to work with Node.js v12 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 Node.js v8 has gone EOL on december 2019. We need to shift the required version to v12, but we rely on old gulp and friends that need to be updated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 31442] New: Node.js v12 is EOL
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31442 Bug ID: 31442 Summary: Node.js v12 is EOL 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The currently maintained LTS release is v16. We could start using v18 which will be the new LTS in october and would be current until 2025. https://nodejs.org/en/about/releases/ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 29489] New: <<branches.branchname>> in RENEWAL notice subject field
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29489 Bug ID: 29489 Summary: <<branches.branchname>> in RENEWAL notice subject field Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org Using <<branches.branchname>> returns the library name when used in the subject field for a notice template with one apparent exception. If an item is renewed from the OPAC the RENEWAL notice is sent with the subject "<<branches.branchname>>" We are set up so that an item renewal via the OPAC should get recorded statistically as a renewal by the branch the item was checked out at. It would be nice if <<branches.branchname>> filled in the branch name of the library where the item was checked out rather than "branches.branchcode" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28315] New: PopupMARCFieldDoc is defined twice in addbiblio.tt
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28315 Bug ID: 28315 Summary: PopupMARCFieldDoc is defined twice in addbiblio.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The `PopupMARCFieldDoc` JS function is defined twice in addbiblio.tt.. probably a merge error at some point.. should be easily resolved. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 31604] New: Add the ability to batch add a manual fee to a list of patrons
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '23

21 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31604 Bug ID: 31604 Summary: Add the ability to batch add a manual fee to a list of patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: jheltibridle(a)rcplib.org QA Contact: testopia(a)bugs.koha-community.org It would be very helpful to have the ability to add a manual fee to a list of patrons. An example of using this feature would be to add a collections fee to a list of patrons who are being submitted to a collection agency at the same time. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 31405] New: Set focus for cursor to setSpec input when adding a new OAI set
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '23

21 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31405 Bug ID: 31405 Summary: Set focus for cursor to setSpec input when adding a new OAI set 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When adding a new OAI set from administration, the focus/cursor should be in the first field of the entry form: setSpec -- You are receiving this mail because: You are watching all bug changes.

1 24