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

[Bug 10902] Highlight patrons from logged-in library in patron searches
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '21

07 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10902 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #119057|0 |1 is obsolete| | --- Comment #8 from David Nind <david(a)davidnind.com> --- Created attachment 123587 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=123587&action=e… Bug 10902: Highlight patrons from logged-in library in patron searches This patch alters a few different patron search interfaces so that patrons from the currently-logged-in library are highlighted in a way that differentiates them from other patrons. To test, apply the patch and rebuild the staff interface CSS (https://wiki.koha-community.org/wiki/Working_with_SCSS_in_the_OPAC_and_staf…) - In Administration -> System preferences, make sure the PatronAutoComplete preference is enabled. - In the "Check out" tab in the header, type a partial patron name which will return multiple results and wait for the autocomplete menu to appear.. - Patrons in the autocomplete results should show the branchcode, and patrons from the currently-logged-in library should be highlighted in green. - Submit your partial name in the "check out" tab. - In the search results the branch name of patrons from the currently-logged-in library should be similarly highlighted. - Go to patrons browse for patrons. These results should be highlighted as in the previous steps. Signed-off-by: David Nind <david(a)davidnind.com> Signed-off-by: Sally <sally.healey(a)cheshiresharedservices.gov.uk> Signed-off-by: David Nind <david(a)davidnind.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15504] Track Patron's Last Activity
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '21

06 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #33 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- (In reply to Andrew Fuerste-Henry from comment #32) > Bug 28455, signed off, adds checkouts to lastseen. So we're kinda working in > two different directions here. > > I'm in favor of a simple approach here: a single field with a datetime that > updates each time a patron does any of the listed actions (log in to OPAC, > SIP, ILSDI, API, checkout, checkin). > > The batch patron deletion tool already knows how to filter by both lastseen > and circ activity. The need I run into here relates to reports rather than > the deletion tool itself. We get regular requests for a report that will > give a column of the last date on which a patron either logged in to > something or checked something in or out. That's much messier SQL than it > needs to be with the current data structure. +1. I would add, if it is a need for anyone to define what triggers this field, a permission with checkboxes of actions that would trigger it would finish this off nicely. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15504] Track Patron's Last Activity
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '21

06 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 Bug 15504 depends on bug 28630, which changed state. Bug 28630 Summary: ILSDI::AuthenticatePatron should set borrowers.lastseen https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28630 What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15504] Track Patron's Last Activity
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '21

06 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 Bug 15504 depends on bug 28630, which changed state. Bug 28630 Summary: ILSDI::AuthenticatePatron should set borrowers.lastseen https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28630 What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to master |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 28142] New: Accessibility: OPAC Cart/basket checkboxes are not labelled
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '21

06 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28142 Bug ID: 28142 Summary: Accessibility: OPAC Cart/basket checkboxes are not labelled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The checkboxes on the OPAC cart ("Basket") pages are not labelled. this makes it hard for users of screen readers to determine their purpose. This applies to both the brief and verbose displays. e.g. the checkbox appears in NVDA as: "Unlabeled; check box; not selected" We should add distinct labels so that users can identify the purpose of the checkboxes without visual context. The labels should include the title of the item so that users can decide which items to select from a list e.g. "Select [Title]" rather than "Select item". >From what I've read it is better to use <label> with the .sr-only class rather than using aria-label. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 27848] New: Elasticsearch - include 245b subtitle subfield in the default title index mappings
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '21

06 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27848 Bug ID: 27848 Summary: Elasticsearch - include 245b subtitle subfield in the default title index mappings Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucy.vaux-harvey(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Currently the Elasticsearch default mappings do not include 245b so searches including subtitles will not return results. It would be useful to have this added as a default mapping as it is a widely used subfield. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 28391] New: Elasticsearch - Add 264b to publisher index mapping
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '21

06 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28391 Bug ID: 28391 Summary: Elasticsearch - Add 264b to publisher index mapping Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com The publisher index currently only looks in 260b, but 264b is also often used for the publisher. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 15067] Add additional languages to advanced search language search
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '21

06 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15067 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle(a)bywatersolutions.com Status|Pushed to master |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '21

06 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 --- Comment #223 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Created attachment 123583 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=123583&action=e… Detail view of record with RTL and LTR script Adding a screenshot to explain the issue a little better. I believe usability of the scroll box might not be too well if you have really a lot of records, because it limits you to a relatively small "view". Also slightly worried about handling on mobile interfaces as it sticks to the 2 column layout and won't stack as other elements on smaller sizes. I haven't checked all the comments yet, but could we imagine a different placing? Maybe below or above the items? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14083] Make it possible to record the date the order was placed/sent to the vendor
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '21

06 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14083 --- Comment #10 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- > What is needed is a reportable 'order date' and this needs to be the date > the order is sent to the vendor. This cannot change. I need to be able to > make adjustments to funds, and pricing subsequent to this, if updates come > from the vendor, without it changing the initial 'order date'. Yes, I understand. Daphne described a solution in comment#6 that would have us have an additional database field recording the first time the order was closed. And use this for the purpose you describe. > I can't see why Koha developers do not prioritise financial functions in > Acquisitions. Most libraries (both public and academic) use framework > agreements which our purchasing must adhere to. The vendors have a set > number of weeks to respond to our orders and this is a legal requirement. We > have reports set up in Koha to compile all our transactions and 'order date' > is key to many, if not all of these. > We use EDIFACT ordering for all our orders. I am not saying that your bug is not valid. I was only pointing out that most changes in Koha happen as funded developments. Some support companies might prioritize developments like this on demand of their customers or have hours for it included in support contracts, but I cannot tell about that. So far this bug is not assigned to anyone for development, so at the moment I don't see a fix coming. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0