We're looking to make preferred pronouns front and centre for our users and are thinking of changing the Gender field to record a patrons preferred pronouns. Has anyone else done this and if so, can provide any feedback? (PS - I'd be changing the field label as well from Gender to Pref. Pronoun and creating different pronouns in the TR_Gender table.)
Michele
Hey Michele -
There is a standard attribute that comes with the database called Preferred Pronouns and this comes along with its own flex header element. The values for that attribute are configured in TR_PRONOUN. Pronouns and gender identity can be two very different things, hence the two data points.
Thanks,
Patrick
Michele-
I have used the attribute Patrick mentioned and put it in the header as field, so our front end users can easily see it. Note: I did ask Tessitura to consider changing "Preferred Pronoun" to just "Pronoun". I am hopeful that change request will be implemented.
The only feedback I would offer is to consider making this an optional field, rather than required. It is my understanding that some may not be comfortable sharing their pronouns, or committing to a pronoun, so making this optional relieves the pressure.
Hi Jessica. We understand the importance on this, and the field has been changed to "Pronouns" in v16 (where it also gets migrated from an attribute to the constituent record proper, similar to how gender is now). In v15, you can safely change the description of the attribute in T_KEYWORD without any issue.