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

[Bug 21445] New: Report - having two date ranges in query creates a formatting issue when running report
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21445 Bug ID: 21445 Summary: Report - having two date ranges in query creates a formatting issue when running report Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: tgoatley(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When the report is run like the following query, the second half of the second date range does not display. SELECT borrowers.cardnumber, borrowers.surname, borrowers.firstname, borrowers.dateofbirth, borrowers.dateenrolled FROM borrowers WHERE dateofbirth BETWEEN <<Date of Birth BETWEEN (yyyy-mm-dd)|date>> AND << AND (yyyy-mm-dd)|date>> AND dateenrolled BETWEEN <<Enrollment Date BETWEEN (yyyy-mm-dd)|date>> AND <<and (yyyy-mm-dd)|date>> AND branchcode=<<Branch|branches>> ORDER BY borrowers.surname ASC Reformatting the query as follows all dates ranges display correctly. SELECT borrowers.cardnumber, borrowers.surname, borrowers.firstname, borrowers.dateofbirth, borrowers.dateenrolled FROM borrowers WHERE dateofbirth BETWEEN <<Date of Birth BETWEEN (yyyy-mm-dd)|date>> AND << AND (yyyy-mm-dd)|date>> AND dateenrolled BETWEEN <<Enrollment Date BETWEEN (yyyy-mm-dd)|date>> AND <<and (yyyy-mm-dd)|date>> AND branchcode=<<Branch|branches>> ORDER BY borrowers.surname ASC -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21414] New: view_borrower_infos_from_any_libraries can't be used with IndependentBranches
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21414 Bug ID: 21414 Summary: view_borrower_infos_from_any_libraries can't be used with IndependentBranches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When IndependentBranches is turned on, library filter on 'Patrons' menu page ('cgi-bin/koha/members/members-home.pl') only allows the current user site. In spite of the use of the 'view_borrower_infos_from_any_libraries permission', it's not possible to search for patrons from other libraries, even if we're part of the same group of libraries. We can access patron account using the url. No modifications are allowed whether we set IndependentBranchesPatronModifications to 'yes' or 'no'. See also Bug 12599 - IndependentBranches Holes -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 27187] New: Cannot delete/update local cover image with LocalCoverImages off
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '23

06 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27187 Bug ID: 27187 Summary: Cannot delete/update local cover image with LocalCoverImages off 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When the LocalCoverImages syspref is set to "Don't display," Koha hides the image itself as well as the Images tab on the bib details page. However, if a library has OPACLocalCoverImages on, they'll likely want to access that Images tab to delete or change the images they're displaying on the OPAC. Could we hide the tab only if *both* sysprefs are off? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31003] New: WhatsApp notifications
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31003 Bug ID: 31003 Summary: WhatsApp notifications 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be great to support WhatsApp as a delivery medium for notices. https://developers.facebook.com/docs/whatsapp/cloud-api/get-started -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 17868] New: Improve display of authors in cart and list emails
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17868 Bug ID: 17868 Summary: Improve display of authors in cart and list emails Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The cart and list emails display a lot of subfields for the author. Example: Author: Seemann, Christian --Bearb. --adp $a $e $4 It would be nice to not display $4 (relator code) if there is $e (relator term). -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 23134] New: Having an "internal notes" field which would be available throughout the suggestion process
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23134 Bug ID: 23134 Summary: Having an "internal notes" field which would be available throughout the suggestion process Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.thornton(a)educampus.ie QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When editing a Purchase Suggestion there is no field to allow staff communicate or add internal notes for other staff. Due to the workflow relating to Purchase Suggestions a suggestion is often passed to another member of staff for approval. Having an "internal notes" field which would be available throughout the suggestion process, would help to facilitate this communication. Staff are currently relying on coded text to communicate using the Notes field e.g. "Lot 1.1 1 X NCM-ML; 1 X NCSL-SL". They also set the reason in the drop-down menu. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31374] New: Add a non-public note column to the suggestions table
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31374 Bug ID: 31374 Summary: Add a non-public note column to the suggestions table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: lucas(a)bywatersolutions.com Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries would like to have a non-public note field when entering suggestions so they can add suggestion notes that would not be visible to the public. -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 22590] New: Allow batch printing of routing lists
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22590 Bug ID: 22590 Summary: Allow batch printing of routing lists 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Target Milestone: --- For libraries dealing with lots of routing lists it would be nice if they could be printed in batch on demand after receiving several issues. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 27949] New: Batch printing of article request slips
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27949 Bug ID: 27949 Summary: Batch printing of article request slips Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 We propose allowing for staff to select multiple article requests on the screen and have Koha generate them and print in one transaction through the browser. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 22362] New: Make item column in cart sortable in OPAC
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22362 Bug ID: 22362 Summary: Make item column in cart sortable in OPAC 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- While the items column in the staff client is sortable, the same is not true for the cart view in the OPAC. I know that the most we could do is sort on the first callnumber available in the list, but I think this would still be helpful in some setups. For example for libraries with only one branch it would be really helpful if the column was sortable as it would help to generate a list that can be used at the library to efficiently get the books from the shelves. -- You are receiving this mail because: You are watching all bug changes.

1 2