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

[Bug 26177] New: The 'set library' functionality should be changed to 'session settings' or similar
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '24

11 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26177 Bug ID: 26177 Summary: The 'set library' functionality should be changed to 'session settings' or similar 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The set library controller and template will soon allow the setting of other session level information like 'desk' and 'cash register'.. as such we should rename and clean up the controller and template to reflect their new functionality. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 28532] New: Accessibility: Staff Client - add legends to forms
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '24

10 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28532 Bug ID: 28532 Summary: Accessibility: Staff Client - add legends to forms 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: wainuiwitikapark(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Many of the forms in the Staff Client do not have legend tags to describe them. This is not accessible and makes it hard for navigation when using a screen-reader. However, adding these legends to forms can create redundancy and appear unnecessary. Therefore, it may be beneficial for these legends to be in the class "sr-only" so that they are not visible, they are just available for those who use screen readers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 27877] New: Accessibility: Staff Client - Reduce heading redundancy and correct error/alert headings
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '24

10 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27877 Bug ID: 27877 Summary: Accessibility: Staff Client - Reduce heading redundancy and correct error/alert headings 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: wainuiwitikapark(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 27631 created <h1> headings on each page of the Staff Client, then Bug 27741 fixed the hierarchy of the other headings in each page to ensure there was no skipping of heading levels, and that items that appeared as headings of some sort, had an <h> tag. There are now a few headings that are redundant so this bug will deal with issues like this. Many of the alerts and errors are also tagged as headings, which for many cases is not correct. Therefore, this bug will also deal with these issues -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 16605] New: All notices should give the ability to unsubscribe or flag account
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '24

10 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16605 Bug ID: 16605 Summary: All notices should give the ability to unsubscribe or flag account Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org There should be a way to unsubscribe to notifications within the e-mail. This could be a link to the patron's notification settings, or simply turn the switch off for that notification. There should also be a way to indicate that the e-mail has gone to the wrong person. A link that says "Not my account", or something to that effect. It could either put a restriction on the account indicating the e-mail address has been flagged as wrong, or just be a note on the account that it is wrong. Christopher -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 23668] New: Information on syntax for patron attributes
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '24

08 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23668 Bug ID: 23668 Summary: Information on syntax for patron attributes Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: anke.bruns(a)gwdg.de QA Contact: testopia(a)bugs.koha-community.org In the manual at https://koha-community.org/manual//19.05/en/html/tools.html#patron-import-l… the syntax for multiple patron attributes which, to complicate things, consist of multiple words separated by blanks isn't described correctly. It says: <citation> "Note If loading patron attributes, the ‘patron_attributes’ field should contain a comma-separated list of attribute types and values. The attribute type code and a colon should precede each value. For example: “INSTID:12345,BASEBALL:Cubs” This field must be wrapped in quotes if multiple values are defined. Since values can contain spaces, additional doubled-quotes may be required: “INSTID:12345,BASEBALL:Cubs,””BASEBALL:White Sox”” " </citation> After trying this, and all other possible combinations of attributes and quotes I could come up with, I found that import only works if the attributes are entered in the most simple way, namely in single quotes. The blanks can be which, for the above example, would read: “INSTID:12345,BASEBALL:Cubs,BASEBALL:White Sox” I didn't test exactly this combination of attributes, but with similar ones it worked. If this can be confirmed, maybe the manual can be updated accordingly? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 22709] New: Add hooks to notify plugins of biblio and item changes
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '24

08 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22709 Bug ID: 22709 Summary: Add hooks to notify plugins of biblio and item changes 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- We should have a way to make *Biblio *Item methods trigger actions on plugins. Maybe if we have a message queue, then enqueue messages for registered plugins (i.e. to avoid synchronous calls). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 22569] New: Stock rotation: need transfer reports
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '24

08 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22569 Bug ID: 22569 Summary: Stock rotation: need transfer reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client 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 Target Milestone: --- The cronjob provides a report email tot he branch, however, there is no way on the staff client to view current items needing checked in/advanced at the current branch. Perhaps a 'transfers to send' report like 'transfers to receive' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 148

[Bug 28678] New: OPAC description for SUGGEST_FORMAT authorized values not taken into account
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '24

07 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28678 Bug ID: 28678 Summary: OPAC description for SUGGEST_FORMAT authorized values not taken into account Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I don't know if this problem is limited to SUGGEST_FORMAT or if it applies to other AV categories as well. To replicate: 1) Go to Administration > Authorized values > SUGGEST_FORMAT 2) Edit one of the values and change only the Description, not the Description (OPAC), e.g. Authorized value : BOOK Description : Booooooook Description (OPAC) : Book 3) Go to OPAC and log in 4) In your account, go to You purchase suggestions 5) Create a new purchase suggestion 6) Note that in the Item type drop-down menu, the label for Book is actually Booooooook I would expect the Description (OPAC) to be used here, and only if Description (OPAC) is empty, then Description would be used. (In case you're wondering the use case, while it is not possible right now to make one value the default as in bug 20682, I usually advise my clients to put numbers in front of the labels to force the alphabetical order in the order they want. For example, 1. Book; 2. DVD; 3. Audiobook; etc. It would be nice if we could have the numbers in the Description and no numbers in Description (OPAC), that way patrons don't see the numbers.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 26775] New: Cannot put newly imported authority into biblio field
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '24

05 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26775 Bug ID: 26775 Summary: Cannot put newly imported authority into biblio field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Open authority finder on say field 100 (author) Click Create new authority Click Z3950 search Import a new authority No way to choose this authority and put it in the 100 field -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25163] New: Add the ability to bulk attach items to a bib record
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '24

05 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25163 Bug ID: 25163 Summary: Add the ability to bulk attach items to a bib record Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, in Koha, a single item can be attached to a biblio record at one at a time. Libraries do have the need to do this in bulk as they could be possibly moving multiple items to another bib record and having the ability to do it in bulk would be beneficial. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5