-
-
Notifications
You must be signed in to change notification settings - Fork 486
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
Partner Groups: Classification Tags for Partners #2059
Partner Groups: Classification Tags for Partners #2059
Comments
@designbygia thanks for creating this issue! @albertchae I've assigned you to this issue. Let's discuss the implementation details and the approach. I have some thoughts about how this might extend to more features in the future such as the idea of having 'tiers' to see how many items a partner should request per month or time period. Though that might be a feature creep, it might be good to see how it may fit into the future. |
@edwinthinks @albertchae
|
@armahillo good catch! I do agree that I propose maybe a name like I suggest we hold off jumping to |
I agree about the name. It felt awkward while working with it to be honest. It seems we might have 2 separate concepts here. One is for defining a set of items that some partner can request which we are all in agreement with. The other is how do we assign these sets of items to different (maybe multiple?) partners. Are we still thinking we'll allow diaper banks to assign a set of requestable items to multiple partners at once but not call it |
This is really exciting functionality that's being added, and I'm wondering if it can be incorporated with #2121 that I put in about a month ago. If this categorization of products is happening, it will be a natural separation by "program", and it would be GREAT to be able to see totals/reports for each of those "requestable items lists". |
Summary
Our stakeholders serve a number of different organizations and often distribute items based on the type of organization. So, for example, they may distribute both diapers and period supplies to a women's shelter, only newborn diapers to a neonatal clinic, adult incontinence supplies to a shelter, and everything to a food pantry. In the drop-down list of items, currently any kind of partner can view all items that a organization supplies and request any of them.
This often leads to challenges as users accidentally request items that they should not be requesting, which puts an unnecessary burden on our diaper bank users, and requires them to do additional work. Based on stakeholder input, we came up with the concept of partner groups. Partner groups are classifications that are meant to create groups that show which items a partner is able to request. So, for example, say an organization created 5 different partner groups -
neonatal
,basic diapers
,period supplies
,adult incontinence
, and `sundries'. They would then go to their various partners and tag them with which group they belong to. Then they would tag items as belonging to different groups. Then when a partner makes a request they will only see which items have been tagged as available for them.Things to Consider
This will likely involve some changes on the partnerbase application as well.
Criteria for Completion
homeless shelters
andwomen's shelters
.The text was updated successfully, but these errors were encountered: