soc-se-bot
commented
4 months ago [IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Team's Response
We understand your concern, however, I would like to clarify that this is not a bug but an intentional design choice that reflects a conscious and inclusive understanding of gender diversity.
The distinction between 'sex' as a biological attribute and 'gender' as a social construct is well-acknowledged, and our application respects this differentiation. As per the User Guide, only predefined attributes are subjected to logic checks, which include 'Sex' but not 'Gender'. This is explicitly stated to ensure clarity for our users. Hence, any attributes that are not the predefined ones are "not policed" and as such, any discrepancies cannot be held liable with us as it has been specifically mentioned and bolded for users.
In today's world, where the recognition of diverse gender identities is increasingly important, our application aims to be inclusive by design. It's not merely a matter of being progressive; it's about being accurate and respectful to all users. By catering to genealogists and other users who value inclusivity, we are not only respecting individual identities but also enhancing the tool's utility.
We appreciate that you may have expected the 'Gender' attribute to function similarly to 'Sex'. However, to conflate the two would be to disregard the complexities and the real-world application of these terms. Our decision to separate these attributes is not an oversight but a deliberate feature to ensure that our application remains adaptable and relevant to all users.
We remain committed to providing a tool that is both user-friendly and inclusive, aligning with best practices as understood in 2024.
https://medicine.yale.edu/news-article/what-do-we-mean-by-sex-and-gender/
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Damn, I did not expect a societal dispute. While the differentiation between sex and gender is increasingly recognized in academic and social circles, it's essential to acknowledge that this understanding may not be universal among all users, especially those who are not familiar with gender studies or related fields. Or at least not mentioned in this course. Many individuals still use the terms interchangeably or may not fully grasp the nuanced differences between them. Your user base likely consists of individuals with varying levels of education, cultural backgrounds, and experiences. Not all users may be familiar with the distinction between sex and gender, particularly if they come from backgrounds where these concepts are not commonly discussed or emphasized. Hence, I believe that the feature could be implemented or discussed in the guides to reduce confusion/ misuse.
Gender attributes could be added to represent sex instead. When users use the application, the 2 categories would be synonymous. Rendering the gender check with specific relationships non optimal.