-
Notifications
You must be signed in to change notification settings - Fork 10
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
Updated readme and added demographics table #63
Conversation
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.
Almost there!
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.
Almost there.
Just some documentation/formatting cleanup and one clarification request...
Please also indicate "Testing done".
"If it is not tested, it is broken"
Code looks fine. |
@achasmita thank you for including the screenshot. However, the testing is not sufficient because it doesn't actually show any of the demographic survey fields. Also, please automatically exclude the vast majority of the metadata fields. We don't need the Please updated with more descriptive screenshots that show what you are actually testing. |
Here is the one after removing metadata.key and including demographic survey fields. |
Does this only remove
You can, and should, include multiple screenshots to showcase the breadth of your testing. |
i mean all the columns that starts with metadata. |
Please push these changes and I can merge |
utils/db_utils.py
Outdated
df[col] = df[col].apply(str) | ||
columns_to_drop = [col for col in df.columns if col.startswith("metadata")] | ||
df.drop(columns= columns_to_drop, inplace=True) | ||
df.drop(columns=['data.xmlResponse', 'data.name', 'data.version', 'data.label', 'data.jsonDocResponse.aSfdnWs9LE6q8YEF7u9n85.attr.id','data.jsonDocResponse.aSfdnWs9LE6q8YEF7u9n85.attr.xmlns:jr','data.jsonDocResponse.aSfdnWs9LE6q8YEF7u9n85.attr.xmlns:orx'], inplace=True) |
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.
I don't think we should hardcode any of the form ids (such as aSfdnWs9LE6q8YEF7u9n85
) because I believe they can be different from form to form. But the other changes are fine.
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.
e.g. the form ID for the time use survey, for example, is time_use_survey_form_v9_1
https://github.com/sebastianbarry/nrel-openpath-deploy-configs/blob/surveys-info-and-surveys-data/survey-resources/data-json/time-use-survey-form-v9.json
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.
I am going to approve this for now and we can tweak based on feedback.
No description provided.