April 2021 - Koha-bugs - lists.koha-community.org

[Bug 26635] New: Expand authorised values in REST API call
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26635 Bug ID: 26635 Summary: Expand authorised values in REST API call Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: agustinmoyano(a)theke.io Reporter: agustinmoyano(a)theke.io We need a way to embed expanded authorised values in a REST API call. It's specially needed when you have to show authorised values descriptions in tables that are fetched through api. The proposed solution adds to object's api definition (even embedded content) the following key: _authorised_values For each column that contains an authorised value, it will be reflected inside this property, with the authorised value expanded. So for example if we embed the authorised values of an item, the result from the API call could look like this: GET /api/v1/items/1 { "_authorised_values": { "location": { "authorised_value": "GEN", "category": "LOC", "id": 27, "imageurl": null, "lib": "General Stacks", "lib_opac": null } }, "acquisition_date": "2014-05-07", "acquisition_source": null, "biblio_id": 1, "item_id": 1, ... "location": "GEN", ... "uri": null, "withdrawn": 0, "withdrawn_date": null } -- You are receiving this mail because: You are watching all bug changes.

1 155

[Bug 24284] New: Canelling of holds and order should allow for different translation then cancel as options in dialogs
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24284 Bug ID: 24284 Summary: Canelling of holds and order should allow for different translation then cancel as options in dialogs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr At least in German the verb used for cancelling orders/holds is different than the verb used for cancelling a process/cancelling a dialog. It would be nice if Koha allowed for different translations in this case. Maybe the new I18N features could be helpful here? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 27875] New: CollapseFieldsPatronAddForm reveals guarantor_template
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27875 Bug ID: 27875 Summary: CollapseFieldsPatronAddForm reveals guarantor_template 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 If you use CollapseFieldsPatronAddForm to hide the guarantor section of the member entry form, toggling that section reveals the guarantor_template. I have yet to find a way to work around this problem. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26977] New: Update Koha Documentation to use absolute paths instead of relative ones
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26977 Bug ID: 26977 Summary: Update Koha Documentation to use absolute paths instead of relative ones Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: rex(a)nicic.gov QA Contact: testopia(a)bugs.koha-community.org Hi, I'm new to Koha, the previous Koha expert left their position a number of years ago and we left our version running along until the server crashed during an OS update. After that, I had to build a new server from scratch, install and upgrade Koha and get it working. I would like to ask that the Koha documentation be updated to make it easier for new people to learn Koha. Request: Please provide at least one absolute path location (rather than relative paths) when referring to file locations in a section. One example is the Cron jobs and Daemons page. I guess under the Cron Jobs subheading, I'm supposed to infer where files are located in the OS based on my flavor, but for someone new like me who is now responsible for becoming the expert on Koha, it would really ease my learning curve to have an absolute path offered at least once on the page. The relative paths on the page give me no indication of absolute location and even the Cron jobs description is making a huge assumption as to the user having knowledge that the writer of the documentation does. The text suggests that the files are in misc/ or bin/ but doesn't state that those are to be found in /usr/share/koha/, which would really help. Alternatively, a find command suggestion could be offered under the "Cron jobs" subheading for the user to locate the files. Since Koha files can be found in so many places, a new person like me doesn't know where to look and at least one absolute path to help someone get started and have a little confidence that they're finding the right file would be really nice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[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 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 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 05 Jul '23

05 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 05 Jul '23

05 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 05 Jul '23

05 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