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.
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!
(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.
(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.
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.