Resolve "clean initial database"

Closes #345 (closed)

This PRC implements following changes:

1. nd_number field is renamed to Subject number (ND is for NCER)
2. following fields will be removed in new installations of smasch: mpower_id, screening, diagnosis, previously_in_study, year_of_diagnosis, pd_in_family, brain_donation_agreement, virus_test_X, virus_test_X_updated, virus_test_X_collection_date, virus_test_X_iga_status, virus_test_X_igg_status. In the existing studies (wiuth at least one subject) the fields would have to removed manually
3. I added a gitlab CI test to check if create_dummy_data script runs without errors

changed milestone to %1.0.0

added enhancement label

added 10 commits

• 679c9528 - visible subject columns are editable
• 9bab8707 - tests for the new form
• 10a17ba3 - visibilty of custom fields is linked to tables
• e08379ec - Merge branch '348-list-of-default-visible-colums-in-subject-lists' into 345-clean-initial-database
• d512c773 - virus_result is properly stored in database
• cd7509c0 - mpower_id moved to custom field
• a065fc83 - diagnosis and screening fields moved to custom fields
• e7cfc46f - previously_in_study brain_donation_agreement and pd_in_family moved to custom fields
• c23f96c2 - year_od_diagnosis moved to custom field
• 28c67ba0 - all PCR related fields moved to custom fields

Compare with previous version

added 4 commits

• 8d031162 - pip 20.3 use new dependency resolver that breaks current config
• 0187e8c5 - columns that cannot be visible in subject table removed from the configuration option
• a2209e95 - Merge branch 'pip-issue' into 348-list-of-default-visible-colums-in-subject-lists
• 0bfb7d75 - Merge branch '348-list-of-default-visible-colums-in-subject-lists' into 345-clean-initial-database

Compare with previous version

added 3 commits

• f3ae0d8f - columns that cannot be shown in table are hidden in the form
• b88d14c1 - Merge branch 'pip-issue' into 348-list-of-default-visible-colums-in-subject-lists
• ba99524e - Merge branch '348-list-of-default-visible-colums-in-subject-lists' into 345-clean-initial-database

Compare with previous version

approved this merge request

unapproved this merge request

added 2 commits

• 80eb6396 - max custom field name should be longer
• e6c83415 - test if create dummy script is executed without issues

Compare with previous version

unmarked as a Work In Progress

changed the description

assigned to @carlos.vega

so, are we keeping the dummy data script? no license issues?

Keep it for now because if we cannot remove/replace fullcalendar-scheduler (and I assume we cannot) the license restriction will be the same

approved this merge request

what will happen to NCER, PDP, COVID deployments if those fields are removed? I see we will have to do it manually, but will they become custom fields?

yes they will become custom fields visible normally in the study subject, so nothing will change

mentioned in commit 15cc8e1e

merged