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

[Bug 26071] New: Allow to configure fields not to be copied when using "Edit as new (duplicate)" in cataloging
by bugzilla-daemon＠bugs.koha-community.org 15 Jan '24

15 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26071 Bug ID: 26071 Summary: Allow to configure fields not to be copied when using "Edit as new (duplicate)" in cataloging 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When duplicating a record for example for cataloging a newer edition an exact duplicate of the record is created. In some cases it would be nice if you could define fields that should be emptied out when duplicating, similar to what we can do when duplicating subscriptions (SubscriptionDuplicateDroppedInput). The use case here would be to drop 001 when copying, so no duplicate IDs are added to the catalog. The field is marked mandatory so then the cataloger will be reminded to fill it in. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 18207] New: smart-rules.pl should validate that all branches / patron categories / item types are covered by circ rules.
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '24

12 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18207 Bug ID: 18207 Summary: smart-rules.pl should validate that all branches / patron categories / item types are covered by circ rules. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com At present, It's possible to have combinations of branch / category / item type that are not covered by circulation rules. This may cause issues with circulation, holds and fines; we should require that all are covered. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 18054] New: Refreshing the screen for a confirmed checkout can cause odd results ( item checked out and waiting on hold)
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '24

11 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18054 Bug ID: 18054 Summary: Refreshing the screen for a confirmed checkout can cause odd results (item checked out and waiting on hold) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1 - Place a hold and confirm it to mark waiting 2 - Checkout that item to another patron and override the hold 3 - Leave that window open 4 - In a new tab checkin the item and confirm the hold as waiting 5 - Refresh the tab from #3 - the item checksout but waiting hold does not revert -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 24738] New: Online registration
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24738 Bug ID: 24738 Summary: Online registration 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I think it would be good, if online registration noted that an account with the e-mail address a patron is registering with is already in use. I also think, that registration should send a code to the e-mail address before registration is complete. If the address already exists, it will send an e-mail to the address saying that someone is trying to register with that e-mail address. If it is not you, contact your library. If it is, and you are registering an account for another family member, use this code to complete the process. This will serve to make people aware that already have a card that they are trying to register an already existing account, but also allow those who use the same e-mail address for more than one family member to proceed. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 16440] New: Update report parameters
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16440 Bug ID: 16440 Summary: Update report parameters Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 51217 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=51217&action=ed… Placement of report parameters on report results. Let's say you have a report that asks you for parameters. You run the report, get the results, and then you want to run the report again with different parameters. Or maybe you made a mistake and need to change it. Yes, you could back up and change things and run it again. But what if the parameters were showing over on the left of the report under the "Useful resources" section? You could see what you set, and change whatever you needed and then click update. Perhaps the row setting and update button could also be on the left of the report. Just a thought. I was able to change a parameter up in the URL, and hit update, and it worked. It was nice because I set the report to show more than 20 records, and I didn't have to repeat that step after updating. Christopher -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 24797] New: xx-XX-messages.po line numbers are not correct
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24797 Bug ID: 24797 Summary: xx-XX-messages.po line numbers are not correct Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Running ./translate update xx-XX, then looking at po/xx-XX-message.po that contains the i18n.inc t(), tx(), tnx() etc translatable strings, the line numbers in the files where the message appears in are not correct: #: koha-tmpl/intranet-tmpl/prog/en/modules/suggestion/suggestion.tt:1 #: koha-tmpl/intranet-tmpl/prog/en/modules/suggestion/suggestion.tt:2 msgctxt "purchase suggestion created by" msgid "Created by:" msgstr "" The comments say that message appears on line 1 and on line 2, but this is not correct. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25885] New: Koha takes you straight into detail.pl when there is only one result - bad for OverDrive link
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25885 Bug ID: 25885 Summary: Koha takes you straight into detail.pl when there is only one result - bad for OverDrive link Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I would like to suggest, if you have OverDrive (or other 3rd party databases) enabled on Koha, that Koha NOT push you straight into a record (detail.pl) if there is only one "Koha" result. You end up not being able to see OverDrive results, or switch over to OverDrive when it does that. Makes the connectivity useless for those with pin-point searching skills. When you enable one of these databases, that should be all you need to disable the default Koha behavior. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 24383] New: koha-create doesn't restart / empty memcached causing installer fail
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24383 Bug ID: 24383 Summary: koha-create doesn't restart / empty memcached causing installer fail Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org If in /etc/koha/koha-sites.conf I have defined USE_MEMCACHED="yes" and then I run "koha-create --create-db kvkoha" and after that "koha-remove kvkoha" and then again "koha-create --create-db kvkoha" then when I try to access the web installer page I get the following error: > DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: Access denied for user 'koha_kvkoha'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1520. at /usr/share/koha/lib/Koha/Database.pm line 107 This seems to happen because the memcached instance still holds the database credentials from the first time koha-create was run. The solution is to clear the memcached cache: > $ systemctl restart memcached After this the web installer loads correctly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 23660] New: Add system preference to remove message body from sent notices after notice status switches to sent.
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '24

08 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23660 Bug ID: 23660 Summary: Add system preference to remove message body from sent notices after notice status switches to sent. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: brendon.ford(a)manhattan.edu QA Contact: testopia(a)bugs.koha-community.org Currently the "Sent notices" list on a borrower's record retains the body of all sent notices. It may be useful for patron privacy to have the option to have message body removed after the notice has been sent. Ideally this would be done immediately after the notice has been processed, but having this scheduled could also be an option. Currently we can have the ability to remove the entire notice, but we would like to keep a record that a notice was sent and just remove what was in the notice. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24731] New: Privacy concerns in Notices
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '24

08 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24731 Bug ID: 24731 Summary: Privacy concerns in 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: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org A library has mentioned possible privacy concerns due to item information being listed in notices sent to the patron. Staff has the ability to read the notices and see what the patron has requested/checked out. They would like the ability to see that they have notified a patron about an overdue and on what date, but not necessarily see what item it was for. They are interested in exploring if these notices can be 'redacted' for privacy. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7