Bug 30981

Summary: Add option to configure preferred pronouns as a pull down
Product: Koha Reporter: Katrin Fischer <katrin.fischer>
Component: PatronsAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: andrew, bugzilla, gmcharlt, kebliss, kyle.m.hall, lucas, rcoert, sbcornell
Version: Main   
Hardware: All   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:
Bug Depends on: 10950    
Bug Blocks:    

Description Katrin Fischer 2022-06-17 08:40:56 UTC
This could work just like bsort1 and bsort2 for the statistic fields. We add a AV category that is emtpy, but once it is filled in, the pronouns field will show up as a pull down. While it's empty, it's a free text field.
Comment 1 Katrin Fischer 2022-10-01 08:09:45 UTC
Now that bug 10950 has passed, it would be great if we could also have this, so people starting with using the new pronouns field have both options (free text and normalized) from the beginning!
Comment 2 Lucas Gass (lukeg) 2023-04-03 19:26:25 UTC
(In reply to Katrin Fischer from comment #0)
> This could work just like bsort1 and bsort2 for the statistic fields. We add
> a AV category that is emtpy, but once it is filled in, the pronouns field
> will show up as a pull down. While it's empty, it's a free text field.

I just filed this Bug 33397, the way we add custom values can result in data loss.
Comment 3 Katrin Fischer 2023-04-05 21:45:12 UTC
(In reply to Lucas Gass from comment #2)
> (In reply to Katrin Fischer from comment #0)
> > This could work just like bsort1 and bsort2 for the statistic fields. We add
> > a AV category that is emtpy, but once it is filled in, the pronouns field
> > will show up as a pull down. While it's empty, it's a free text field.
> 
> I just filed this Bug 33397, the way we add custom values can result in data
> loss.

True, and it would have been much easier to resolve if this had been fixed before the last release. 

But I still think having this optionally turned into an AV would be great. We could add a warning to the release notes or fix it 'right' from the beginning by adding a pull down value for a non-existing AV entry.
Comment 4 Sarah Cornell 2023-07-20 17:49:11 UTC
We were excited to see a pronoun field in the borrowers table in 22.11, but will be waiting to fix up our existing pronoun workaround until there is an authorized value option for the field.  

So our vote is definitely for the optional application of auth values to the pronoun field. We'd rather not wait for the issue in Bug 33397 to be resolved, and we're okay with only having preset values, rather than being able to select authorized values *or* enter free text.