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

[Bug 25446] New: Terminology: Replace relatives by other term? (family members, group members...)
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '24

04 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25446 Bug ID: 25446 Summary: Terminology: Replace relatives by other term? (family members, group members...) 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 I've been wondering if relatives is a good term to use in Koha context. In times where families are not all related to each other, maybe using another term would be nicer and more inclusive? -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 25328] New: Date formatting from JS - Remove tz handling
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25328 Bug ID: 25328 Summary: Date formatting from JS - Remove tz handling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: agustinmoyano(a)theke.io Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)bugs.koha-community.org, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 24455, 24980 After some discussion, I now believe timezone handling in JS is redundant, and should be removed. Dates that comes from the API are already converted to the corresponding timezone with dt_from_string, so there is no need for a second conversion here. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24455 [Bug 24455] Date formatting from JS https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24980 [Bug 24980] Date formatting from JS - use timezone only with dates with offset -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 19616] New: Formatted Contents Note (Marc 21 505), subfield g isn' t visible in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19616 Bug ID: 19616 Summary: Formatted Contents Note (Marc 21 505), subfield g isn't visible in the OPAC Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org The 505 field in Marc 21, Formatted Contents Note, includes subfield g "Miscellaneous information". According to the Marc 21 format for bibliographic data, it is used to record "volume, part, page numbering or other extent information such as dates". If you use it in Koha, this information isn't visible in the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 25467] New: Improve performance of ViewPolicy filter
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25467 Bug ID: 25467 Summary: Improve performance of ViewPolicy filter Change sponsored?: --- Product: Koha Version: master 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Rather than looping through every field of every record, it might be better to determine which fields must be hidden, then deal only with those? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24261] New: Google openID Authethication drops requested url
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24261 Bug ID: 24261 Summary: Google openID Authethication drops requested url Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: mihai.bojonca(a)tcmi.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi everyone, i think this is a bug, we have setup access to catalog after login, we use 2 authentication methods, username and password or google openid, when a patron opens a direct link to an item and authenticates with username and password they get to the item itself however with openid they get redirected to the opac main page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 25221] New: Imported records are not checked for accuracy
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25221 Bug ID: 25221 Summary: Imported records are not checked for accuracy Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When you create a new bib record, Koha checks if certain fields are filled out. When you import a bib record, Koha does not check if that record has those fields filled out. I would suggest that when a record is imported, it either needs to be taken immediately into editing so that Koha can catch issues, or it needs to be put into a quarantine state, and unusable anywhere in the system until it is edited and saved. When importing a bib for an order, since you are dealing with a single record, I could see how going straight into editing after importing could work. However, if you are importing bibs through an batch import tool, if the process isn't already checking for issues or missing fields, these items should be set in quarantine and require the cataloger to edit the record to remove it from quarantine. This process would address problems elsewhere in Koha where incomplete or compromised records cause an error in Koha or in a process that can't complete due to a faulty record. I'm not a cataloger, but this seems like a reasonable workflow for bringing outside records into your own system. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 24967] New: Allow final user to choose ordering column
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24967 Bug ID: 24967 Summary: Allow final user to choose ordering column Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: pascale.nalon(a)mines-paristech.fr QA Contact: testopia(a)bugs.koha-community.org It would be fine, if members of staff, who have not permissions to modify a SQL requests, but only to run them, could choose the column and the way (ASC or DESC) to order the pre-builded request -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 25554] New: Refactor rule kinds assignments in CirculationRules.pm
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25554 Bug ID: 25554 Summary: Refactor rule kinds assignments in CirculationRules.pm Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Circulation Assignee: stalkernoid(a)gmail.com Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Rule kinds in CirculationRules.pm have repeated code with the same values assigned many times. Refactored code is already in a patch that will be pushed promptly to this ticket. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 25112] New: Koha::CirculationRules->set_rules should handle scopes per rule
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25112 Bug ID: 25112 Summary: Koha::CirculationRules->set_rules should handle scopes per rule 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: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org Koha::CirculationRules->set_rules is currently too complicated to use. Right now, in order to specify multiple rules at once, they must all be rules that accept the same set of scopes. Otherwise we can get this type of errors: 1/9 set_rule cannot set 'holds_per_record' for a 'checkout_type'! at t/db_dependent/Circulation/GetHardDueDate.t line 215. Validating scopes at set_rule() is good, but set_rules() should examine each rule and pass the correct scope to set_rule() instead of passing all scopes to every rule like it is doing now. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 25134] New: Return claims column should not be shown if ClaimReturnedLostValue is not set
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25134 Bug ID: 25134 Summary: Return claims column should not be shown if ClaimReturnedLostValue is not set Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Circulation Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the checkouts table shown on circulation and patron details the "Return claims" column should be wrapped in a conditional checking for the presence of a value in the ClaimReturnedLostValue system preference. -- You are receiving this mail because: You are watching all bug changes.

1 14