Repository navigation
Conversation
| 022;22;i1115;22-4 | ||
| 023;23;i1102;23-4 | ||
| 024;24;i1113;24-4 | ||
| participant_id;record_id_s;id_number_pre;myfood24_id;liva_citizenid |
There was a problem hiding this comment.
| participant_id;record_id_s;id_number_pre;myfood24_id;liva_citizenid | |
| participant_id;record_id_s;id_number_pre;myfood24_id;liva_citizen_id |
There was a problem hiding this comment.
I'm trying to keep to the original from the source. In my eyes this is just good data practice, as this is meant to be the table that will help identifying the link IDs from a variety of systems.
| 022;22;i1115;22-4 | ||
| 023;23;i1102;23-4 | ||
| 024;24;i1113;24-4 | ||
| participant_id;record_id_s;id_number_pre;myfood24_id;liva_citizenid |
There was a problem hiding this comment.
And maybe even change id_number_pre to pre_number_id, so all ID's end with _id? If you agree, you can add another PR with that since that's unrelated to adding ID's from Liva 😊
There was a problem hiding this comment.
Same as above, the first couple of IDs comes directly from REDCap, actually, maybe we should prefix them with exactly that...
There was a problem hiding this comment.
During processing we can rename them to all end in _id. And in the end all of these ids will be consolidated into a single participant_id, regardless of data source.
Description
Got a list of IDs from Liva with a corresponding ID in our system and have added them to the ids.csv
I've just added liva_ to the field name, as citizenid is what Liva refers to their user IDs as.
Closes #
Needs a quick review.
Checklist
just run-alljust build-package