You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.
As we in many of our emergency responses will be reporting from structures instead of volunteers, I would like an option to register "points" like oral rehydration points instead of individuals.
So when you choose to register data collector, you pick either "person" or "reporting point". (or if you have suggestions for better names)
Point page would look the same as for data collector person, but instead of name, you have "name of reporting point" and "type of reporting point". It also does not have year of birth.
Click on "add reporting point". Just a first version of your thoughts.
For this example I have changed the submenu to "data collection" and then within this we have "data collectors" and "reporting points"... Nothing is set, we can discuss it.
I think we have to go through all the naming we chosen in the UI :)
I will make some material we can choose from. I know this is difficult but we should have a second look at what we have chosen now.
I am thinking the reporting points should also be shown in a table in case you make several reporting points? I am assuming there can be a need to create more than 1 reporting point?
As we in many of our emergency responses will be reporting from structures instead of volunteers, I would like an option to register "points" like oral rehydration points instead of individuals.
So when you choose to register data collector, you pick either "person" or "reporting point". (or if you have suggestions for better names)
Point page would look the same as for data collector person, but instead of name, you have "name of reporting point" and "type of reporting point". It also does not have year of birth.
@hodoea could you draw this up?:)
The text was updated successfully, but these errors were encountered: