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

[Bug 29633] New: Unecessary GetMarcBiblio call in Koha::UI::Form::Builder::Item (?)
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29633 Bug ID: 29633 Summary: Unecessary GetMarcBiblio call in Koha::UI::Form::Builder::Item (?) 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 Andrew contacted me to raise a potential problem coming from bug 27526: commit 7a8357f7099d0863a322d1e91741b792b97fd6e1 Bug 27526: Adjust code to use Koha::Items -C4::Biblio::EmbedItemsInMarcBiblio({ - marc_record => $temp, - biblionumber => $biblionumber }); has been removed. I have tried to know where the items subfields could be used and found, in Koha/UI/Form/Builder/Item.pm: 1. only if itemcallnumber is used 164 my $temp2 = $marc_record->field($CNtag); 2. cataloguing plugins: 316 record => $marc_record, I have not found any cataloguing plugins using the MARC::Record (some are retrieving it when they have been passed in parameter, but that's another story). So maybe we could: * Remove marc_record from generate_subfield_form param list * Fetch it in the itemcallnumber block * Remove it from the cataloguing plugins -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 27297] New: When itemtype is marked as required in OpacSuggestion MandatoryFields the field is not required
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27297 Bug ID: 27297 Summary: When itemtype is marked as required in OpacSuggestion MandatoryFields the field is not required Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Two issues: 1 - We only add the required class, we don't make the input required 2 - We don't add a 'blank' option, so the field is preselected -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 29290] New: Add routes to fetch checkouts for a given biblio
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29290 Bug ID: 29290 Summary: Add routes to fetch checkouts for a given biblio Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com I propose we add GET /biblios/:biblio_id/checkouts it will have the same behavior as /checkouts, but filtering by the specified biblio. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 34144] New: Batch item modification run at the command line (cronned).
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34144 Bug ID: 34144 Summary: Batch item modification run at the command line (cronned). Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Created attachment 152783 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=152783&action=e… Example workflow to automate. We would like to automate a workflow we are implementing which will run daily. We will run a Koha report to identify items that need a number of identical changes made to various item record fields. Ideally the report would run by cron, and hand the itemnumbers to the batch item modification tool running at the command line. (Conceptually it is a little like the marvellous patron emailer feature than came in 19.05 where a report runs by the cron and hands the results over to a Koha Notice and an email is sent). The workflow / scenario we are trying to automate is attached, as an example of how useful a batch item modification run at the command line would be. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 27957] New: Attributes removed in LDAP
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27957 Bug ID: 27957 Summary: Attributes removed in LDAP Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Working on bug 27857 (actually, on the follow-up bug 27956), I found that the Koha::Patron->extended_attributes setter is used to write the new attributes. This happens inside a Koha::Patron::Attribute::Types loop which is used to determine 'valid' attributes (good). The problem is 'extended_attributes' actually calls: $self->extended_attributes->filter_by_branch_limitations->delete; which deletes the existing attribute. So calling it for setting a single attribute makes it... delete all the attributes each time! There's also some funky logic in checkpw_ldap. The $patron object seems to be retrieved in several places and even inside a loop. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 30205] New: Add biblio.subtitle to the subscription-detail.pl page
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30205 Bug ID: 30205 Summary: Add biblio.subtitle to the subscription-detail.pl page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On the subscription-detail page we show the biblio.title, we should also show the biblio.subtitle, if it exists. This can be shown both in the h1 heading and on the 'Biblio:' line. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 27909] New: When upgrading, old sysprefs are only copied in english news items
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27909 Bug ID: 27909 Summary: When upgrading, old sysprefs are only copied in english news items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I don't know how to reproduce this... When we upgraded from 18.05 to 19.05, the contents for OpacNavRight was copied into the new news item OpacNavRight (english), but not fr-CA which is also installed in all our clients' OPACs. Now we've started upgrading from 19.05 to 20.05 and the old system preferences are still only copied into the english news items. It's a bit more problematic because there are a lot more and all our clients at least have something in opacheader. My colleague Philippe coded a script to copy everything into our fr_CA news items, but this should probably be handled in the upgrade (atomic update?). Here are the news items from old system preferences: - OpacNavRight (19.05?) - opacheader (20.05 bug 22880) - OpacCustomSearch (20.05.03 bug 23796) - OpacMainUserBlock (20.05 bug 23794) - opaccredits (20.05.03 bug 23795) - OpacLoginInstructions (20.05.03 bug 23797) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 26917] New: Searching for patrons: member.pl vs circulation.pl
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '23

04 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26917 Bug ID: 26917 Summary: Searching for patrons: member.pl vs circulation.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When searching for a partial name, you get a list of results. Depending on whether you start your search in check out or patron search, the results differ. The records are the same, but the layout and information shown is different. This is confusing to staff, as they don't remember which place to search for the information they want to search through. I would suggest that we standardize the results so they are consistent. On top of that, I would like to see the ability to pick what information is included the table of results. There are fields we don't need to see, and there are fields we would like to see, in order to determine which patron is the right one. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 26980] New: UNIMARC_sync_date_created_with_marc_biblio.pl is setting MarcFieldForModifierName to CLI
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '23

04 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26980 Bug ID: 26980 Summary: UNIMARC_sync_date_created_with_marc_biblio.pl is setting MarcFieldForModifierName to CLI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Hi, Since Bug 22600 patches there's a context userenv and MarcFieldForModifierName is modified, but like Bug 21487 it doesn't really make sense. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 26981] New: Writing off Accruing Fines causes another accruing fine to appear at checkin
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '23

04 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26981 Bug ID: 26981 Summary: Writing off Accruing Fines causes another accruing fine to appear at checkin Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This is happening on Koha 20.05.05, similar to [24146] bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24146 if a library writes off an accruing fine and then checks that item in, that fine will be re-charged to the patron as Fine Returned. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4