Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identifying self-assigned terms #27

Open
zenlan opened this issue Oct 26, 2017 · 2 comments
Open

Identifying self-assigned terms #27

zenlan opened this issue Oct 26, 2017 · 2 comments
Milestone

Comments

@zenlan
Copy link

zenlan commented Oct 26, 2017

If someone were to come across a database some time in the future and wanted to analyse the, e.g. gender, demographics, how would they differentiate between values that were input by the subject and those input by a third party, i.e. a self-assigned value and a value assigned by another person or a machine.

@sparklingrobots
Copy link

This is also related at least somewhat to what I mention here: #26 in that there is value in knowing how someone self-identified rather than only knowing the way that term or terms later got merged with new or different identities.

@drnikko
Copy link
Owner

drnikko commented Apr 13, 2018

This is a great issue - reading this (after a bit of a hiatus) makes me feel like having a development/engineering plan for this project in addition to a data/question plan would be a good idea.

@drnikko drnikko added this to the Backlog milestone Jun 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants