[Bug 39205] New: Have a way to add optional fields to patron search that won't be included in a standard search
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39205 Bug ID: 39205 Summary: Have a way to add optional fields to patron search that won't be included in a standard search Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs@lists.koha-community.org Reporter: lucas@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com It would be nice if there was a way to add some search fields that could be optionally chosen by staff when running a patron search but not included in the standard search. Example, I want to sometimes search a borrowernote but I don't want to add it to DefaultPatronSearchFields so that all standard searches are searching borrowernote. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39205 hebah@bywatersolutions.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hebah@bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39205 Saiful Amin <saiful@semanticconsulting.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |saiful@semanticconsulting.c | |om --- Comment #1 from Saiful Amin <saiful@semanticconsulting.com> --- Another use-case supporting this as an enhancement: Many libraries use unique extended patron attributes to store alternate IDs (e.g., HID/NFC card numbers). These attributes are searchable only directly and not in Standard search. Historically, staff could identify a patron by scanning the HID card directly in the checkout box. After the introduction of DefaultPatronSearchFields, this is no longer possible. Allowing extended patron attributes to be selected in DefaultPatronSearchFields would restore this workflow and cover this use-case. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39205 Saiful Amin <saiful@semanticconsulting.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Version|unspecified |Main -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39205 --- Comment #2 from Saiful Amin <saiful@semanticconsulting.com> --- (In reply to Saiful Amin from comment #1)
Allowing extended patron attributes to be selected in DefaultPatronSearchFields would restore this workflow and cover this use-case.
I probably misunderstood the original intent of this bug. Perhaps I will create a new one for this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org