Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lets resolve changes in our models that we want to break down as we merge with Human Connection #5

Open
sfc-gh-eraigosa opened this issue Jun 14, 2020 · 1 comment

Comments

@sfc-gh-eraigosa
Copy link
Contributor

Is your feature request related to a problem? Please describe.
We have a data structure that we developed that needs to merge with the models that we need from Human Connection. Here are some basic assumptions:

  • We will have many services that are sourced outside from other NGO's that will be loadable. These will come as a category we call our Basic Plan that has no service providers taking ownership.
  • As service providers want to take ownership, we will have a secondary plan called Standard Plan, which will allow service providers to take ownership of services, and add new associated services.

These assumptions are important for us to model in our backend.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@Carlosgsuarez
Copy link
Contributor

Carlosgsuarez commented Jun 26, 2020

One observation: Once the social service provider takes ownership of her/his profile, s/he might or might not upgrade to the standard plan. If not, he will continue to be filtered or searchable through the broad category or categories he has been placed in or the one or ones he has decided to place her/himself.

In this aspect is also important to take in consideration what we are counting. In the case of the basic plan, we are counting persons served by category (or the generic service that represents that category??). in the standard plan, once the service provider gets to define the detailed services they offer, the app will be counting services, that could be aggregated to a total per category. Notice that in both cases we could calculate a total of the number of persons served by that particular provider, but we need to avoid counting twice a person that was given two different services in the same location and/or on different times. I think this is obvious, just wanted to point it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants