search

brighthive / master-client-index

BrightHive's Master Client Index framework.
MIT License
2 stars 2 forks source link

Should we populate Gender, Ethnicity, Education Level, and Employment Status? #14

Closed reginafcompton closed 5 years ago

reginafcompton commented 5 years ago

Should we populate Gender, Ethnicity, Education Level, and Employment Status when POSTing a new user, if those values do not exist in the database?

Currently, we raise an error, if someone POSTs, say, a gender but that gender does not exist in the database:

https://github.com/brighthive/master-client-index/blob/78d98f4e50f1a04968a8c524a2090b1d7c6b08cd/mci/api/v1_0_0/user_handler.py#L156

reginafcompton commented 5 years ago

@gregmundy - question for you!

reginafcompton commented 5 years ago

The classifications show consistency across data sets (e.g., ethnicity, gender) – we can likely pre-populate. That should happen upon initialization of an MCI.

E.g., we run a migrations script that adds the data! (New issue forthcoming.)

But why not create it when POSTing a user? You end up with the possibility of adding bad data, e.g., misspellings.

reginafcompton commented 5 years ago

Closed in favor of https://github.com/brighthive/master-client-index/issues/17