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
Beth,
Thanks for a marketing take on things. Being a DBA means I love data and its always good to see how it is being used by different disciplines.
My hope would be that the gender field would become something that organizations could customize to their needs (either through system tables or something similar).There will obviously be organizations who never touch the default values, but for those who do see a need to customize it, it would be a great tool to have.
There was some follow up to this conversation on the web through a few other blog posts. The most interesting one I saw was from Metafilter.com. One of the DBAs did some quick analysis on their database. It is a realtively small sample size (< 10,000 records with a value entered for gender) but even with a free text field in place, they were still able to identify over 75% of the values as indicating a preference for being identified as either male or female. The full comment has a detailed breakdown of the remaining values (along with his caveats), but it is interesting to see what kinds of things people will enter when left to their own devices.