It would be better if the system incorporates a few more gender options by default. d.o has already tackled this in the user profiles with male/female/transgender/other .
see also: http://opensupporter.org/gender-pronouns-and-netroots-nation/
which touched on providing subject/object/possessive bits of language: they/them/theirs . Such attributes would be nice on the user interface such as "their phone call" vs "her phone call" or "They were called" or "node belongs to them"
on config/install/field.storage.profile.crm_gender.yml
Module looks great!! Inclusion always cool :)
Comments
Comment #2
nedjoThe Gender Field module, https://www.drupal.org/project/gender, is the recommended solution here.
Comment #3
nedjoOn second thought, the Gender Field module looks to be designed mainly for self-registered information as distinct from the CRM use case where data is usually being collected and registered about others. I've posted a related question here. But overall the best approach here is probably to reconsider whether a gender field is needed. What purpose does it serve? The Gender Field project page does a good job of presenting these questions and options. If there is an important purpose, would that aim better be served by some other form of data collection, such as a pronoun field, or a title or prefix (such as Mr./Ms./Mx.)?
Comment #4
andrewbelcher commented@nedjo The gender field is just initial config. You can update it / remove it / replace it with Gender Field as you require.
I would say it is questionable how worth keeping the initial config for a gender field is! It's fairly opinionated in a way it probably doesn't need to be, so perhaps it's best to simply remove it?
Comment #5
mrdalesmith commentedClosed as no response for 8 months. Field settings can be changed or deleted through the normal Profile user interface, so no changes needed to the Contacts module.