As a user I would like to register myself in the system

[petertheprofessional]

A user must be able to register in the system.

• Anyone can register in the system with basic information, e-mail, phone, if it is active or not, and the role.
• A profile must be associated with the user later after registration.
• Requests must provide the minimum information required. An invalid request is an error.

Tests

• not to users can be registered with the same e-mail.
• requests missing data must be rejected and User not registered, accepted otherwise.
• user not associated with profiles must be inactive until.

[petertheprofessional]

Are Users assigned a role? When a teacher registers how do we know they are a teacher

[petertheprofessional]

Should we handle institutions, persons on the same ticket?

[mathiasbrito-dci]

I would say, that we first register the user... and as a second step we could set the profile... This would require some changes in the model maybe, but I would say that we can register the user, and then associate a profile to the user... the thing here is the hierarchy... the inheritance... Y

[mathiasbrito-dci]

Let's do one thing, please add the "role" field on User model, what do you think?

[petertheprofessional]

1. So far Hila and I have implemented a test to see if valid data has a True bool in the is_active attribute
2. Today I plan on writing routes to post a new user based on user input data
3. The biggest block for me is the group aspect of this sprint, I'm not sure we are working on unique enough issues. I think a lot of what we are doing will overlap yet we will have written the information differently

[mathiasbrito-dci]

We need to identify the overlapping and make you sync your work. Let's try to list here all the overlapping issues... Anynone?