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

dataservice replaces specific reverse family relationships with generic ones #462

Open
fiendish opened this issue Oct 24, 2018 · 0 comments
Labels
question Further information is requested

Comments

@fiendish
Copy link
Contributor

fiendish commented Oct 24, 2018

The dataservice replaces any participant2_to_participant1_relation value that you set if your participant1_to_participant2_relation is in its list of basic reverse relationships.

So if you submit e.g.

"participant1_to_participant2_relation": "Mother",
"participant2_to_participant1_relation": "Daughter"

The dataservice will always replace "Daughter" with "Child", because it says that "Child" is the reverse of "Mother". Is this forced replacement behavior intentional?

Should all family relationships be sexless? Should we be sending "Parent" instead of "Mother" and "Father" and rely on the participant sex field?

@fiendish fiendish changed the title dataservice replaces sent reverse family relationships dataservice replaces specific reverse family relationships with generic ones Oct 24, 2018
@fiendish fiendish added the question Further information is requested label Oct 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant