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

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

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #25 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- Please double check, as a non-native speaker, misunderstandings are bound to happen someday :) (In reply to David Cook from comment #2) > I noticed recently that "lastseen" updates for "Patron logs into OPAC" and > "Patron is authenticated via SIP2" and that's it. I've had libraries > interested in the field being updated for the other activities Nicole > mentioned as well. -- 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 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #24 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- (In reply to Christopher Brannon from comment #23) > I must be missing something here. Where is the information on patron logins > to OPAC or authentication via SIP2 that isn't in a log? borrowers.lastseen IIUC -- 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 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #23 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- I must be missing something here. Where is the information on patron logins to OPAC or authentication via SIP2 that isn't in a log? I'm not sure what tables I should be looking at for this information. -- 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 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #22 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- (In reply to Christopher Brannon from comment #21) > (In reply to Victor Grousset/tuxayo from comment #20) > > > (assuming SQL report are not enough?) > > As was mentioned, pulling stuff from activity logs is hit or miss. I missed that part. What do you mean by activity logs? The issues and old_issues tables? Because if I understand correctly, the following data is in the above tables + borrowers.lastseen > Patron checks out item > Patron renews an item > Patron returns an item > Patron is authenticated via SIP2 > Patron logs into OPAC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 24862] New: REST API throws 500 errors for browser after logout
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24862 Bug ID: 24862 Summary: REST API throws 500 errors for browser after logout Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au It looks like the REST API might not be handling cookies correctly. To test: 0. Use koha-testing-docker 1. Login to http://localhost:8080/ 2. Go to http://localhost:8080/api/v1/libraries 3. Observe a 200 OK HTTP code and JSON output 4. Logout from http://localhost:8080/ 5. Go to http://localhost:8080/api/v1/libraries 6. Observe a 500 Internal Server Error and the following JSON output: {"error":"Something went wrong, check the logs."} It seems to me that really that should be returning a 401 and the following JSON output: {"error":"Authentication failure."} -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 25902] New: Export MARC records for all titles in a virtual shelf
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25902 Bug ID: 25902 Summary: Export MARC records for all titles in a virtual shelf Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists 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 We let user-defined lists / virtual shelves be used to select bibs for record deletion and modification. It would be nice to be able to use a list to export records, too. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

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

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #21 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- (In reply to Victor Grousset/tuxayo from comment #20) > (assuming SQL report are not enough?) As was mentioned, pulling stuff from activity logs is hit or miss. Depending on how often information is purged, you won't get very accurate results. This is data that is best recorded in the patron record or related table. -- 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 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #20 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- (In reply to Christopher Brannon from comment #17) > The link to dev list is a dead link. http://devs.bywatersolutions.com/projects/track-patrons-last-activity/ isn't the dev list. It was a page ByWater Solutions had on this topic. The mailing lists are here: https://koha-community.org/support/koha-mailing-lists/ «General List» and «Koha Developers List» seems to me the good ones to seek organizations to cosponsor or/and to contract to work on this. (assuming SQL report are not enough?) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 22167] New: Allow itemnumber column to be labelled differently when using bach item edit feature
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22167 Bug ID: 22167 Summary: Allow itemnumber column to be labelled differently when using bach item edit feature Change sponsored?: --- Product: Koha Version: 17.11 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 Target Milestone: --- Bug 19233 added a feature that allows you to send a list of items to the item batch edit from a saved SQL report. At the moment this only works, if your column is displayed as itemnumber. Example: Works: show itemnumber from items; Doesn't work: show itemnumber as "Item#" from items; This is not nice for translations. It would be nice if there was a different way to mark the itemnumber and explicitly activate the feature. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

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

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 --- Comment #19 from Agnes Rivers-Moore <arm(a)hanover.ca> --- (In reply to Martha Fuerst from comment #18) > Chiming in again. > > This is ESPECIALLY important for us now, with COVID-19 and social distancing > procedures, we have more people using 100% online resources - and people who > have gotten cards using online registration, verified via email, to use > those resources. > > Tracking last patron activity via SIP2/OPAC login is definitely a priority > for US at Huntsville-Madison County. > > Best, > > -Marti Fuerst +1 - COVID-19 has certainly increased the urgency on this! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0