Data Model for Staff and Partner user information about cbs HOT 4 CLOSED

Agreed with business owners that we use birth year instead of age. Edit: we can't base birth year after all since not all countries have the same calender. => use age + date when it was saved = current age

from cbs.

Comment from discussion with Inge in Admin:

I know that a frequent use-case is Data Collectors with multiple numbers. I think User Mgmt must discuss with Anine or other RC domain expert to determine, but we in Volunteer Reporting are happy with a primary number and possible secondary numbers. Maybe #team_alerts needs to also take this into account (We are considering the option for manual SMS sending to target only primary phone or all phones for a given data collector)

from cbs.

Some thoughts on the creation of a data collector (a user in the system with no login), should probably be a separate thing from the system/staff user signup: A data collector model has a few different fields than a staff/system user, and those two would benefit from being kept as separate entities in the system. If a data collector is "promoted" to a data verifier, that person will need to sign up as a user in the system and be assigned the data verifier role. The two separate users can of course be linked in some way in the database to show the history of the user being "promoted" to data verifier, but they should probably still be two separate entities, because of their difference.

from cbs.

Covered by other issues, and already implemented.

from cbs.