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

WIP: updated family model -DO NOT MERGE #85

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Conversation

putmantime
Copy link
Collaborator

  • added FamilyRelationship Class
  • removed family member ids from participant e.g. mother_id
  • created relationship_type and corresponding enum

@putmantime putmantime requested a review from mbrush December 6, 2022 23:06
FamilyRelationship:
name: FamilyRelationship
definition_uri: include:FamilyRelationship
description: Object that captures relationships between the Participants and metadata about that relationship
Copy link

@mbrush mbrush Dec 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggested definition: "Object that captures a relationship between the Participant and another member of their family, along with metadata about that relationship."

description: Participant ID for Participant's father
title: Father Id
range: string
relationship_type:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might name this family_relationship_type - since it specifically holds familial relationships.

has_participant:
definition_uri: include:has_participant
description: Link to a Participant
title: Has Participant
range: Participant
has_relationship:
definition_uri: include:has_relationship
description: Link to a Relationship
Copy link

@mbrush mbrush Dec 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the class is now called FamilyRelationship, this should be reflected in the definition, with perhaps a bit more detail, e.g.: "A link to a FamilyRelationship object that describes the nature of a Participant's relationship to another family member."

@@ -226,13 +235,31 @@ slots:
title: Race
range: enum_race
required: true
related_participant:
definition_uri: include:related_participant
description: Participant related to Subject Participant
Copy link

@mbrush mbrush Dec 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might add a bit more detail/specificity here, e.g. "A family member to which the Participant is related" . . . unless you mean for this slot to be used more generally to describe any relationship to a participant.

Also, the phrase 'subject participant' might be confusing to those not thinking in terms of a relationship having a subject and object (which I think is the sense of 'subject' you mean here).

sex:
definition_uri: include:sex
description: Sex of participant
title: Sex
range: enum_sex
required: true
enums:
enum_relationship_type:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we name this family_relationship_type to be more precise here?

@putmantime putmantime changed the title updated family model WIP: updated family model -DO NOT MERGE Dec 13, 2022
@lopierra lopierra mentioned this pull request Feb 7, 2023
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

Successfully merging this pull request may close these issues.

2 participants