This is a big issue across the board. The more that can be done about this the better. We are all striving to support our constituents as best we can, and make them as happy as possible. To have this ability would be a benefit to our university.
There are best practice gender options that exist. Progressive research institutions already use them. This doesn't need to be a big production but it is pretty essential to honoring a donor's intentions and identity.
A short term solution is to create a constituent attribute to capture this information. We continue to evaluate a longer term solution to support this need. We will update when we can provide more information.
I agree with Jessica's comment. We need to demonstrate that we care about and honour our constituents and donors, and we need to get fundamental things such as their gender right in order to be able to do that.
We would really like to see this implemented to better serve our constituent base and respect their gender identity and privacy as best as we can.
We are releasing updated functionality to support an "other" table value that can then be tied to an attribute. We are targeting 4.0 SP13 for release.
The Other gender option was added in SP13. However, you have to create an Attribute Form Extension, create an "other" gender table and an "Other" gender field tied to the new table.
The thing I think will be most confusing for the business users is that the “new” gender field that contains the additional gender types will not appear next to the current Gender field.
I also cannot make the additional gender type field required when Other is selected unless I involve my development team.
This means that a business user can select Other and not select an option from the additional gender field.
Also, I could technically select Female and Transgender. This would result in bad data.
You won't be notified about changes to this idea.