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

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 Rebecca Coert <rcoert(a)arlingtonva.us> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rcoert(a)arlingtonva.us -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9150] Add id and relevance as sort options for authorities search
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9150 Esther Melander <esther.melander(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |esther.melander@bywatersolu | |tions.com --- Comment #2 from Esther Melander <esther.melander(a)bywatersolutions.com> --- It would also be nice to be able to sort by authority type when doing a default search. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35181] New: Can no longer edit sample records with advanced cataloguing editor
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35181 Bug ID: 35181 Summary: Can no longer edit sample records with advanced cataloguing editor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I wonder if this is a side effect on the recent work on 'invalid metadata'. * Activate * Make sure you open any record with the advanced editor * Try to open: Perl best practices / Damian Conway. * You get stuck in loading * Javascript error shows "Invalid-metadata" on top of the MARC record, causing a syntax error -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 35443] New: Persistent encoding error message in Advanced Editor
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35443 Bug ID: 35443 Summary: Persistent encoding error message in Advanced Editor Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 159376 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=159376&action=e… Record with encoding errors? Related to bugs 34014 and 351814 Recreating this bug requires having a record with some kind of encoding error. Usual errors included bad characters or record separator characters such as blank spaces. My understanding of the bug fixes above are that the fix should automatically strip out the errors. The encoding error notification should only appear one time. 1. Find record with errors (example record attached that has a persistent error message). 2. Open record in the advanced editor. 3. See the encoding error notification. Click on it to make it go away. 4. Edit the record in some way. 5. Save the record and close the advanced editor. 6. Reopen the record in the Advanced editor and see the encoding warning box again. No encoding error message appears when opening the record in the Basic Editor. Also if we tell the user to check the logs, there should be a convenient way to access them - which perhaps is a separate issue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 Dani Elder <danielle.elder(a)law.utexas.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |danielle.elder(a)law.utexas.e | |du --- Comment #7 from Dani Elder <danielle.elder(a)law.utexas.edu> --- Yes a transfer to bib based on multiple selected items would be great feature for serials, splitting bibs, etc. as previously mentioned. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 8292] clicking ignore on hold cancels transfer
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8292 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 31579] New: Improve reserve/request.pl to avoid mistakes with pick up locations
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31579 Bug ID: 31579 Summary: Improve reserve/request.pl to avoid mistakes with pick up locations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the place hold page reserve/request.pl, there are two sections. One is the "Hold details" section which allow for record hold. The other is "Place a hold on a specific item" which speaks for itself. The pick-up location by default is the signed-in user (the employee). But it is different from the "Allowed pick-up location" for the item which defaults to the homebranch. The wording should be "Pick-up location", btw, the "Allowed" states there's a list, not that the user should select it. A common tread is that the user comes in, select the pick up location in the record section, select an item *and doesn't modify the last column*, which overrule the pickup location in the notice. We propose a patch where a modification of the first drop down in the record modifies all the items dropdown to the same value by default. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 29700] New: Koha performs a second cashup in error when changing registers immediately after cashup
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '24

13 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29700 Bug ID: 29700 Summary: Koha performs a second cashup in error when changing registers immediately after cashup Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com To recreate: - perform a cashup for library A, register A - after cashup, koha takes you do /cgi-bin/koha/pos/register.pl?op=cashup - from that url, click to Set Library - Change yourself to library B and register B - koha takes you back to /cgi-bin/koha/pos/register.pl?op=cashup, this time for your new register, and performs a second cashup -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28406] New: Point of sale don't register a sale when total amount is 0
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '24

13 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28406 Bug ID: 28406 Summary: Point of sale don't register a sale when total amount is 0 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Is that a valid use case? Likely. - For free stuff where it's useful to track the "sales" like for stock management or just to know the sold quantity as a stat. - Some real use: http://irc.koha-community.org/koha/2021-05-19#i_2353796 ==Test plan== 1. Try to sell with debit type item with price 0.00 2. Submit 3. page refreshes but no sign of a transaction 4. Register details show nothing either -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 37566] New: When using a search term to limit the transaction history in the POS module the amount for total income should be recalculated
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '24

13 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37566 Bug ID: 37566 Summary: When using a search term to limit the transaction history in the POS module the amount for total income should be recalculated Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com When using a search term to limit the transaction history in the Point of Sale module it would be helpful if the amount listed as total income would recalculate based on the limit that was used. As it is, the total income listed is actually for all transactions within the date range used for the search. Applying a limit does not recalculate the amount which is confusing and actually inaccurate based on the display of actual transactions listed on the screen. My use case would be if someone asked me for a list of all the transactions for a specific debit type (such as copies) within a date range I could easily get that information from the transaction history by limiting to that debit type. If I printed that information out and handed it off to someone else they would expect for the total to be accurate for the transactions listed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2