Currently components are stored in different places without a clear hierarchy. Reorganize the components into the following buckets:
DataInput: Core GeoTimeline (i.e. data input of geotimelines using map interface), future additions regarding authentication and signing for data integrity as well as optional metadata forms to add additional information that a contact tracing organization might want (such as who to follow-up with about contact -- this kind of info would obviously not be stored in the open, even anonymized).
UserFacing: UserMapInput (i.e. end user checking positions and using map for reorganized directions), and DataView
AccountManagement: Registration and Login, Intro Landing Screen With Instructions, Add Users/Workers, Support, Training and Integration Plans, Billing
DataAnalyticsComponents: DataInputAnalytics (e.g. how many geotimelines captured), ShareOfCaseAnalytics (i.e. of number of new cases in region covered how many were contact traced), Leaderboard, LeaderboardSubmissionForm
Currently components are stored in different places without a clear hierarchy. Reorganize the components into the following buckets:
DataInput: Core GeoTimeline (i.e. data input of geotimelines using map interface), future additions regarding authentication and signing for data integrity as well as optional metadata forms to add additional information that a contact tracing organization might want (such as who to follow-up with about contact -- this kind of info would obviously not be stored in the open, even anonymized).
UserFacing: UserMapInput (i.e. end user checking positions and using map for reorganized directions), and DataView
AccountManagement: Registration and Login, Intro Landing Screen With Instructions, Add Users/Workers, Support, Training and Integration Plans, Billing
DataAnalyticsComponents: DataInputAnalytics (e.g. how many geotimelines captured), ShareOfCaseAnalytics (i.e. of number of new cases in region covered how many were contact traced), Leaderboard, LeaderboardSubmissionForm