Closed lucasbento closed 8 years ago
thanks @lucasbsilva for the PR,
why can't we put all the information from the Profile model inside User model?
what is a BloodCollection? it is a hospital or something like that?
We could keep this model design for now, but as we discussed this week at gitter, we are going to folllow @keuller approach of creating first the view with mocked data, and then go to the backend
@sibeliusseraphini I like to keep everything separated so it will be easier to scale that's why I kept Profile and User separated but we can merge them right now.
BloodCollection would be a hospital or a spot where you can donate blood.
I do agree with @keuller's opinion on how to proceed with this, the requisites will be determined by the views.
Started database design with simple models, the fields have commentaries to explain themselves.
It's simple but can be used for our MVP.
I have used Profile and User so that the user can have its own profile as in a social network, it also saves the user location so we can notify him if he's close to a blood colletion place.