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

[Bug 32505] New: Cannot search by dateofbirth in specified dateformat
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '23

07 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32505 Bug ID: 32505 Summary: Cannot search by dateofbirth in specified dateformat Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(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. Set DefaultPatronSearchFields to include dateofbirth 2. Set dateformat to something besides iso. I am using mm/dd/yyyy. 3. Set a patron to have a dateofbirth 4. Search for them in your specified dateformat. For me "04/24/1980". It doesn't return your patron. 5. Try ISO format, "1980-04-24". It works. We should be able to find patrons in a search based on the dateformat specified. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 32970] New: Allow export of batch item modification results in background jobs
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '23

07 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32970 Bug ID: 32970 Summary: Allow export of batch item modification results in background jobs 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bath item modification results present the user with a DataTable containing the results. Other tables in Koha can be exported, we should add that feature to this page -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 28607] New: Error: Session timed out. Please log in again
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '23

06 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28607 Bug ID: 28607 Summary: Error: Session timed out. Please log in again Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: xuan(a)klc.edu.sg QA Contact: testopia(a)bugs.koha-community.org Created attachment 122228 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=122228&action=e… error prompt once user login, unable to click on buttons as it redirect us to this timeout error. please advise. http://23.239.31.27:8080/cgi-bin/koha/admin/authorised_values.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 32339] New: [Elasticsearch] Provide record when cataloguing biblios
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32339 Bug ID: 32339 Summary: [Elasticsearch] Provide record when cataloguing biblios Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When reindexing with elasticsearch, the record is passed for authorities but not for biblios. This means that authorities are indexed as they are, while biblios are pushed to a background job. These processes should be consistent. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[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 31168] New: Temporary Item Locations
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31168 Bug ID: 31168 Summary: Temporary Item Locations Change sponsored?: --- Product: Koha Version: 21.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 There is a needed item field when it comes to locations. Right now, if you put in a permanent location, if an item is returned, the location is temporarily changed to the cart location, and then back. However, there are other scenarios that are getting overlooked. Sometimes an item lives on a new books shelving location. Sometimes it lives on a display. These locations are temporary, and these items eventually have to make their way back to their permanent shelving location. There is no field for a temporary location, so we end up using the permanent location. And because we do this, we are unable to automate the process of setting it back to its regular shelving location when it is time, because there is nothing for the automatic item modifications by age tool to look at to determine what the permanent shelving location needs to be changed too. I propose that a temporary shelving location field be added, where we can select from the shelving locations the place that it will live for a little while, and the permanent shelving location can be set where it will usually live. We can then use the automatic item modifications by age tool to set this back after a set time. Ideally, it would be better if we could automate this from the record itself, perhaps setting a temporarily shelving location cutoff date. Otherwise, the temporary shelving location is only good as long as a rule exists for it in the tool. Having the cutoff date in the item record would make this extremely easy to use. Maybe fore a little extra, we could have a couple buttons next to the field with pre-defined (in preferences) lengths of time. For example, one button for New Books, and another for Displays. Click whichever button, and it would set the date x days from today based on the pref. Or you could manually pick a date from a date picker as to when it would revert back. Once that date comes around, that temporarily location can either be cleared or remain, but the permanent shelving location is displayed past the date. If a date is not entered, the temporary location is used indefinitely. And of course, if there is no temporary shelving location, the permanent location is used. Some of this could be done in stages, if not all at once, but this would be a fantastic step forward for libraries that utilize temporary placement and shelving. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[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 32932] New: Re-structure Vue router-links to use "name" instead of urls
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '23

05 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32932 Bug ID: 32932 Summary: Re-structure Vue router-links to use "name" instead of urls Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: matt.blenkinsop(a)ptfs-europe.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Currently the Vue router is set up with urls assigned to components with no "name" property. This means that in the components, where a router-link tag is used the full URL has been written out again. In the event that a url needs to be changed in the router, the url will also have to be changed in every component that uses that route. By using the "name" property we can avoid this and make maintenance of the router much more efficient. -- You are receiving this mail because: You are watching all bug changes.

1 73