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

Adding a service_at_location_id to the service_area table #497

Open
dan-odsc opened this issue May 8, 2024 · 0 comments
Open

Adding a service_at_location_id to the service_area table #497

dan-odsc opened this issue May 8, 2024 · 0 comments
Assignees
Labels
MINOR upgrade Clear requests that would require a MINOR upgrade to the schema schema

Comments

@dan-odsc
Copy link
Contributor

dan-odsc commented May 8, 2024

Hi all, I have another use case, contributed by Karen Henry at the 211 for Finger Lakes Region, New York:

When pulling the details for a program, the service area should be related to the location, not the program. Such as Food Pantry at High Street Food Pantry is only available for Chemung County residents, and the Food Pantry at Schuyler Outreach Food Pantry is only available for Schuyler County residents. They are both food pantries offered by Catholic Charities of Chemung and Schuyler Counties. Currently, the service area shows Chemung and Schuyler counties for both locations. It is the same program in our database, but different locations with different eligibility.

I think we have definitely found a case for adding adding a service_at_location_id to the service_area table. I would like to propose this for the next minor version of HSDS.

@mrshll @Dan-ODS @bloom

@dan-odsc dan-odsc added schema MINOR upgrade Clear requests that would require a MINOR upgrade to the schema labels May 9, 2024
@dan-odsc dan-odsc self-assigned this May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MINOR upgrade Clear requests that would require a MINOR upgrade to the schema schema
Projects
Status: Proposed
Development

No branches or pull requests

3 participants