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

[Bug 23042] Local login attempt populates shibboleth url with userid and password in plain text
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

1 0

[Bug 22543] Patron might be logged in again using browser back button
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

1 0

[Bug 15331] Sort order breaks at offset=1000 (both OPAC and Intranet)
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15331 --- Comment #7 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I fear the performance hit would be too big to justify a change to a high number by default. What we could do is document this option/behaviour better, so libraries can choose to take the hit. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15331] Sort order breaks at offset=1000 (both OPAC and Intranet)
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15331 Patrick <pm(a)interleaf.ie> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pm(a)interleaf.ie --- Comment #6 from Patrick <pm(a)interleaf.ie> --- On review can I ask if there is a difference between 7041 & 15331 in that: What is being requested here is a "sort all" parameter - that is the system will sort all results in the set whether it is 10 or 100,000. Where as 7041 is a specified number and after that number the results will be no longer sorted. Potentially this would cause a performance hit on some searches, but that would be expected. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15342] Performance 3.22 - Omnibus
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15342 --- Comment #4 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Katrin Fischer from comment #3) > Should we keep this open and/or update the bug title? I would keep it like that until nobody get back to it. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12038] Need a provision to search specific barcode/accession number
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12038 --- Comment #2 from vimal kumar <vimal0212(a)gmail.com> --- This problem can be solve by using "bc:" along with barcode. Thank you. -- 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 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #9 from Agnes Rivers-Moore <arm(a)hanover.ca> --- Summary so far - A timestamp, updated by checkout / renew / return / SIP2 / OPAC login. (Nicole) The type of activity needs to be indicated as well as the timestamp. (Christopher) SIP2 activity needs to be tracked. (Martha) Noted "Lastseen" seems to capture OPAC login and authenticated by SIP. This would be the "updated" timestamp displayed in the patron summary. My thoughts - It would help to know more about how people want to use this timestamp. Is it for reports (inactive patrons for weeding, or activity for statistics), or to be visible to staff in the patron record, like the "Updated" timestamp? We would need clearer labels - "updated" implies but does not actually indicate when the borrower record was renewed or edited. Checkout / renew / return (whether through intranet, OPAC or SIP) are one kind of activity, and are captured already in circulation history. OPAC login and SIP (e.g. for authentication of outside systems like Overdrive) are another, and they are also already captured somewhere but not clear to staff. Should they be handled separately or feed into a single last activity date? I would also like a way to update that activity timestamp without checking out. Something like the "statistical borrower" but a "statistical item" that could be scanned to record library activity not connected to Koha. For example, people who use computers or sign up for programmes. Maybe there is one I have missed. I agree with Martha that tracking SIP2 connections is important, and perhaps should be addressed in more detail. We use it for self-checkout, computer booking (in-library activities) and authentication for accessing Overdrive, RBDigital (external resources). Some label suggestions - last-login (OPAC or self-checkout), updated (patron details changed through OPAC or Intranet), last-activity (activity from any channel including SIP), remote-use (outside resource SIP connections and OPAC login). Just suggestions, for wider discussion. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 15504] Track Patron's Last Activity
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 Agnes Rivers-Moore <arm(a)hanover.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arm(a)hanover.ca -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 3150] Move emails for sending cart and list contents into notices tool
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3150 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=23554 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15949] New: Making certain alerts stand out
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15949 Bug ID: 15949 Summary: Making certain alerts stand out Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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 In the attempt to make certain messages stand out from others (in this case, when an item is checked in that is not in the system or is miss-scanned), I added the following jquery: //Enhance No item with barcode message $("p.problem:contains('No item with barcode:')").parent("div").removeClass("alert").css("background-color","red").css("border","1px solid #e0c726").css("background","rgba(0, 0, 0, 0) -moz-linear-gradient(center top , #FAECEC 0%, #FAECEC 9%, #FC1B1B 89%, #FA2A2A 100%) repeat scroll 0 0"); //End Enhance Would love to see visual enhancements of the alerts become a preference in admin. Christopher -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4