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

[reginafcompton]

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:

master-client-index/mci/api/v1_0_0/user_handler.py

Line 156 in 78d98f4

result['error'] = 'Invalid gender type specified.'

[reginafcompton]

@gregmundy - question for you!

[reginafcompton]

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]

Closed in favor of #17