Some time ago I had made an inquiry with Tess support about the possibility of altering the potential values of the gender dropdown in the application. The answer at the time was that making such a change wasn't possible in the current application, but that some consideration might be given to it in the design of the NextGen product.
This morning I came across a blog post from one of the developers on the Diaspora project. (Diaspora is intended to be a Facebook-esque social network in which the backbone consists of "nodes" installed onto servers by the users of the system.)
The blog post, Why Gender is a text field on Diaspora, is a brief look at the developers thought process in making gender a very flexible piece of data.
Four years ago, at my first rails job, I worked at a company with a mostly-*** customer base. It turns out, in that context, knowing if someone is “male” or “female” gives you almost no useful information. The *** community has other widely-accepted categories of gender, but the company’s internal order tracking software — a well-known package from a national vendor — offered only male or female.
...
I made this change to Diaspora so that I won’t alienate anyone I love before they finish signing up.
The comments seem to be running about 50/50 between "So happy you've done this!" and "Meh".
I know there are a lot of design considerations being made in the planning for the NextGen project. Just wanted to share this link as a bit of a thought provoker and conversation starter. I suspect that some Tessitura licensees find themselves with unique constituent populations that might benefit from this type of flexibility.
-Levi