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

[Bug 21225] New: Add Syndetics enhanced content to staff client
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '23

26 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21225 Bug ID: 21225 Summary: Add Syndetics enhanced content to staff client Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliwho(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Syndetics enhanced content is currently only available in the OPAC. It would be helpful if content were also available in the staff client (as it is for NoveList, for example). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 43

[Bug 18084] New: Language selector hidden in user menu on mobile interfaces
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '23

26 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18084 Bug ID: 18084 Summary: Language selector hidden in user menu on mobile interfaces 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 If you choose to have the language selection at the top, it will be hidden in the 'user menu' on smaller display sizes. That seems a bit counter-intuitive as you wouldn't expect it there. It would be nice if it was visible at all times. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 15765] New: Request to replace patron number list by patron barcode list
by bugzilla-daemon＠bugs.koha-community.org 25 Jan '23

25 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15765 Bug ID: 15765 Summary: Request to replace patron number list by patron barcode list Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: Heinrich.Hartl(a)email.de QA Contact: testopia(a)bugs.koha-community.org Change request: Substitute patron barcodes for patron numbers Patron card creator is working with something called a batch. A batch is a list of patron numbers where patron number is the koha internal index of a patron. Unfortunately the patron number is to my knowledge a patron property that is not known elsewhere. E.g. it is not shown when displaying patron details. But even in the patron search part of patron card creator that number is not shown. In the patron search we see e.g. name and barcode of the patron. Patron barcodes are familiar and found in many reports, in patron import and in patron displays. I suggest to replace the list of patron numbers by a list of patron barcodes. Patron barcodes are also unique identifers of patrons, an unambigous index into the borrowers table. An entered barcode not necessarily identifies an existing patron. However an entered patron number is not more reliable since a patron may have been deleted or may not be existent. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 20621] New: Add ability for Koha::Object objects to update themselves with database generated value automatically
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '23

24 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20621 Bug ID: 20621 Summary: Add ability for Koha::Object objects to update themselves with database generated value automatically 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha objects should, on store() update themselves from the db if the database creates any of the columns. That way we don't have to call discard_changes() manually. This patch has no particular use yet, but I wanted to put it here for posterity. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 26711] New: Editing records subfield code is editable
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '23

24 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26711 Bug ID: 26711 Summary: Editing records subfield code is editable Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: paliotti(a)mdp.edu.ar QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 111898 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=111898&action=e… editor image Hi: With any framework in the records editor, the subfield code is editable. It's confuse to the librarians. Is this for any reason? Best regards Pablo -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 25441] New: Improve columns.def by adding more descriptions
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '23

24 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25441 Bug ID: 25441 Summary: Improve columns.def by adding more descriptions 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I've noticed in training lately that we don't have descriptions for some of the fields shown in guided reports through columns.def. Maybe time for an update there! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 25640] New: [OMNIBUS] Ubuntu 20.04 support
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '23

24 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25640 Bug ID: 25640 Summary: [OMNIBUS] Ubuntu 20.04 support 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 26714] New: Allow libraries to set a default sort order for saved SQL reports
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '23

24 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26714 Bug ID: 26714 Summary: Allow libraries to set a default sort order for saved SQL reports Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org It would be useful to be able to set a default sort order for saved SQL reports. We currently use some jQuery to sort ours by Report ID in descending order. This helps save us time because the newest created reports are at the top and we don't have to scroll to the bottom of the list. Other libraries might find it useful to default to Last Run, Last Edit or Author. It would be a timesaver to have the reports already sorted in the most useful way to a library to prevent unnecessary scrolling and searching for a report. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26722] New: [Omnibus] Don't use "here" and similar as a link text
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '23

24 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26722 Bug ID: 26722 Summary: [Omnibus] Don't use "here" and similar as a link text Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy 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 "Here" should not be used as a link text as it doesn't contain any helpful information for people scanning the page for information and also is a problem for blind users using screen readers jumping from link to link on a page. 2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A) https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html There are plenty of other resources with examples too: https://www.w3.org/QA/Tips/noClickHere https://www.washington.edu/accessibility/links/ https://webaim.org/techniques/hypertext/ -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 23979] New: "Account is locked" message on moremember.pl should be displayed on the "Check out" tab in addition to the "Details" tab
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '23

20 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23979 Bug ID: 23979 Summary: "Account is locked" message on moremember.pl should be displayed on the "Check out" tab in addition to the "Details" tab Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 21311 removes the "This account has been locked!" message from the OPAC when a patron account has been locked because someone has attempted to log into that account with an incorrect password more than the number of times specified by the system preference FailedLoginAttempts. This means that a patron may not know that their account has been locked if someone other than themselves has attempted to hack their account. Bug 21312 adds an "Account is locked" message on the patron's "Details" tab when a patron has locked their account by logging in with an incorrect password more than the number of times specified by the system preference FailedLoginAttempts. Most public library staff access a patron's account through the "Check out" tool which takes them directly to the "Check out" tab on the patron's account rather than the "Details" tab. The "Check out" tool is, after all, the default action of the header_search input box on the Koha home page. Having the "Account is locked" message only on the "Details" tab means that when a patron comes into the library and says "I don't understand why I can't get into my account" when staff look up the patron's account through "Check out", as they normally do, they have to take the extra step of switching to the "Details" tab to find out that the "Account is locked." The "Account is locked" message on moremember.pl should be displayed on the "Check out" tab in addition to the "Details" tab. George -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24