Difference between revisions of "GEPS 027: Gender as an Entry Field"

From Gramps
Jump to: navigation, search
m (See also)
m (ISO/IEC 5218 was created by ISO's Data Management and Interchange Technical Committee, proposed in November 1976, and updated in July 2004.)
Line 25: Line 25:
  
 
==Concerns==
 
==Concerns==
Here're the areas with prospective problems:
+
Here are the areas with prospective problems:
  
 
* genderstats
 
* genderstats
Line 34: Line 34:
  
 
==See also==
 
==See also==
* bug [http://www.gramps-project.org/bugs/view.php?id=5730 5730], with patches
+
* bug {{bug|5730}}, with patches
* bug [http://www.gramps-project.org/bugs/view.php?id=3718 3718]
+
* bug {{bug|3718}}
* bug [http://www.gramps-project.org/bugs/view.php?id=3346 3346]
+
* bug {{bug|3346}}
 
*[[Portal:Translators|sub-translation]]
 
*[[Portal:Translators|sub-translation]]
 
*[[Animal pedigree]]
 
*[[Animal pedigree]]
  
 
Also:  
 
Also:  
* bug [http://www.gramps-project.org/bugs/view.php?id=4617]
+
* bug {{bug|4617}}
* bug [http://www.gramps-project.org/bugs/view.php?id=4170]
+
* bug {{bug|4170}}
  
 
==Resources==
 
==Resources==
Line 48: Line 48:
 
*[http://en.wikipedia.org/wiki/Gender Gender], From Wikipedia
 
*[http://en.wikipedia.org/wiki/Gender Gender], From Wikipedia
 
*[http://tranarchism.com/2010/11/26/not-your-moms-trans-101/ Not Your Mom’s Trans 101 « Tranarchism]
 
*[http://tranarchism.com/2010/11/26/not-your-moms-trans-101/ Not Your Mom’s Trans 101 « Tranarchism]
* [http://www.sarahmei.com/blog/2010/11/26/disalienation/ Sarah Mei » Disalienation: Why Gender is a Text Field on Diaspora]
+
*[http://www.sarahmei.com/blog/2010/11/26/disalienation/ Sarah Mei » Disalienation: Why Gender is a Text Field on Diaspora]
 
*[http://web.uvic.ca/~ahdevor/HowMany/HowMany.html How Many Sexes? How Many Genders? When Two Are Not Enough], by A. H. Devor, Ph.D.
 
*[http://web.uvic.ca/~ahdevor/HowMany/HowMany.html How Many Sexes? How Many Genders? When Two Are Not Enough], by A. H. Devor, Ph.D.
 
*[http://www.cosmosmagazine.com/node/1461 Intersex: The space between the genders], Issue 15 of Cosmos, June 2007, by David Salt
 
*[http://www.cosmosmagazine.com/node/1461 Intersex: The space between the genders], Issue 15 of Cosmos, June 2007, by David Salt
  
 
*[http://www.genders.org/ genders.org]
 
*[http://www.genders.org/ genders.org]
 +
 +
*[https://en.wikipedia.org/wiki/ISO_5218 ISO/IEC 5218] - Codes for the representation of human sexes is an international standard that defines a representation of human sexes through a language-neutral single-digit code. The four codes specified in ISO/IEC 5218 are: 0 = not known, 1 = male, 2 = female, 9 = not applicable.
 +
  
 
[[Category:GEPS|G]]
 
[[Category:GEPS|G]]

Revision as of 00:36, 4 February 2014

  • Feature request 5730 Make Gramps more functional for LGBT data

Introduction

Although it is commonly claimed that there are only two genders, there are actually countless genders. There are transmen and transwomen, there are genderqueers, there are intersex people and there are many many more types. These people are not secretive or rare, instead we are made to be invisible when we are forced to place ourselves into a recognizable category. These people cannot fit themselves into the categories of Female, Male, or Unknown and thus they cannot catalog themselves in GRAMPS. Even if this incapability is only a mistake in GRAMPS, it is a mistake which continues to invisibilize and alienate people.

Proposed Solution

I propose that to fix this, we create a new way to recognize gender within the GRAMPS databases. This can be done through the creation of a new GenderType class, a child of GrampsType that is created in a similar way to EventType or NameOriginType. Then, using this type, gender would be decided from a ComboBoxEntry system, allowing people to select Male, Female or Unknown, but also allowing people to fill in their own genders.

Some aspects of GRAMPS such as gender stats and gender-guessing (based on given name, which actually is only useful for finding the gender one was assigned at birth) would have to be retooled/rethought. Another barrier might be the conversion of the old data to the new.

How Extensive a Change Would this be ?

I'm in the process of making this change on my own machine, and so far I've edited 8 files ( gui/editors/editperson.py, plugins/view/relview.py, gen/lib/person.py, glade/editperson.glade, gen/db/read.py, gui/views/treemodels/peoplemodel.py) and created one (gen/lib/gendertype.py) and it works! (mostly...) There are obviously still bugs, but this was just what I've been able to do with a week or so.

I'd be interested in doing a lot of the work on this project, I'm pretty new to python coding, but I feel capable, and as long as my work is reviewed, I'm sure I wouldn't do anything destructive.


Concerns

Here are the areas with prospective problems:

  • genderstats
  • gender guessing
  • translation?

If you have any concerns about this project, feel free to add them to this section:

See also

Also:

Resources

  • ISO/IEC 5218 - Codes for the representation of human sexes is an international standard that defines a representation of human sexes through a language-neutral single-digit code. The four codes specified in ISO/IEC 5218 are: 0 = not known, 1 = male, 2 = female, 9 = not applicable.