When reading columns, we should use code to standardize certain column headings. All searchers should be case in-sensitive.
- ParticipantID - ParticipantID, Participant ID, participant_id, participantidentifier, participant_identifier, patient_id, patientid, patientidentifier, patient_identifier; if none found, look for MRN, MRN_No, MRN_Number, mrn_num, mrn_number, pid, p_id, userid, user_id in that order.
- StudyID - StudyID, Study ID, study_id, studyidentifier, study_identifier, studynumber, study_number, study_no in that order. If none found, look for StudyName, Study Name, Study_Name, Study.
This gives us more flexibility without forcing the users to rename vital columns or pre-process their sheet. We should do the same, if possible, with date columns, device type columns, and anything else that could differ significantly depending on which vendor exported it.
Internally, we need to stop using participantidentifier and study_id, and stick to participantid and studyid (no underscores). That will make it more consistent across other apps published the the Depression Center.
When reading columns, we should use code to standardize certain column headings. All searchers should be case in-sensitive.
This gives us more flexibility without forcing the users to rename vital columns or pre-process their sheet. We should do the same, if possible, with date columns, device type columns, and anything else that could differ significantly depending on which vendor exported it.
Internally, we need to stop using participantidentifier and study_id, and stick to participantid and studyid (no underscores). That will make it more consistent across other apps published the the Depression Center.