Bug 39205 - Have a way to add optional fields to patron search that won't be included in a standard search
Summary: Have a way to add optional fields to patron search that won't be included in ...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-26 17:50 UTC by Lucas Gass (lukeg)
Modified: 2025-12-05 07:00 UTC (History)
4 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lucas Gass (lukeg) 2025-02-26 17:50:59 UTC
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.
Comment 1 Saiful Amin 2025-12-05 06:52:37 UTC
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.
Comment 2 Saiful Amin 2025-12-05 07:00:58 UTC
(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.