-
Notifications
You must be signed in to change notification settings - Fork 1
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
Ensure participant properties at site metadata #658
Conversation
$addToSet: { | ||
participants: { | ||
Active: 1, | ||
Consent: new Date(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be a date from the metadata, or do we track consent based on upload date?
participants: { | ||
Active: 1, | ||
Consent: new Date(), | ||
study, | ||
participant, | ||
synced: new Date(), | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it matter that participants
is no longer a participant
, but now contains a participant
?
Thinking of a scenario where something like participants.name
used to work, but now it would need to be participants.participant.name
can/should we spread participant
?
participants: { | |
Active: 1, | |
Consent: new Date(), | |
study, | |
participant, | |
synced: new Date(), | |
}, | |
participants: { | |
Active: 1, | |
Consent: new Date(), | |
study, | |
synced: new Date(), | |
...participant, | |
}, |
Also just based on participants
being plural, should this be an array of participant objects?
closing because this will be handled in #665 |
closes #661
This pr ensures that the participant that is stored has all the properties to render