food-oasis
food-oasis copied to clipboard
hackforla
Design a self-service system for pantries to verify/update their own info
LOOKING FOR NEW VOLUNTEERS TO TAKE OVER THIS PROJECT
Overview
As a Pantry and/or Hot Meal location, I want to be able to update my own listing so that I don't have to field calls from Food Oasis.
Details
Some organizations that we have called to validate listings have indicated that if we had a web interface they would update the listing themselves and that they have to answer a lot of calls, so it would be preferable.
Dependent Issues #376 Implement Organization Audit UI #379 Improve Client-Side Validation of Hours #683 Implement Client-Side Validation of Phone Number and Email
Action Items
- [x] Research plan to investigate how best to work with orgs and implement this feature in a way that works for them
- [x] Consent forms
- [x] Competitive analysis: Google and Yelp, in the Figma file
- [x] Sketch a pilot process flow for sending emails, handling verifications, and corrections.
- [x] We have a prototype in Figma. Another possibility would be Keynote (free on Apple devices), which is actually an amazing augmented slideshow tool, with hotspots and hypercards.
- [x] Review with existing data validator admins to see if the process makes sense.
- [x] Jelena reviewed it with @itserindean (Jan 3 2023) and incorporated her comments.
- [ ] Review of the self-service status flag flow.
- [ ] Do a limited pilot version to validate the idea and find bugs: a low-effort ‘mechanical turk’ of an automated system where it’s actually humans behind the scenes sending emails, doing validations, etc.
- [ ] Edit mock-up with changes.
- [ ] Review flow on prototype Mockup email reminder, in the Figma file
- [ ] Design: UI design a full version
- [ ] Engineering: build and test pilot version
- [ ] User test with Admin Volunteer
- [ ] Build full version
- [ ] Create a new issue for the prototype for Data Entry Volunteer (Allows the volunteer to send personalized emails to organizations. Review "P1: Email reminder")
Feasibility
We have email addresses on file for many pantries and meal programs.
How it might work
Rather than having volunteers poll for listing updates, we could send a periodic reminder to those email addresses with a link to their listing, asking them to validate and correct their info, potentially saving many person-hours on our end, as well as raising visibility of the listing on their end.
The email could contain a special link that lets the recipient view and, if necessary, submit corrections for a listing, and perhaps prioritize/mark these specific changes for the Food Oasis admins to review before publishing. If the system works so well that we can validate certain email addresses as claiming a listing, perhaps changes may even be automatic.
If necessary, this link could be time-bounded (expires after a couple of weeks) to prevent abuse.
If we can build this as a module, this type of data validation flow might be useful for other open-source projects as well.
Consider preemptively contacting emails associated with each location and point recipients to a listing for them to confirm it. If they confirm via a link, or with the correct email address, then corrections are given priority.
Benefits to FOLA
Having the food pantries and hot meal locations update their own listings might improve data quality and depth while reducing the need for validation volunteers.
Artifacts created for this issue
- P1: Email reminder 12/02/21
- P2: Email reminder 12/29/21
- Figma (UX designs)
- Miro: Self-service status flag (logic flowchart)
Attaching PDF with the mock-up discussed during the team meeting. Notes and comments added in the pdf.
I've completed the changes suggested during our meeting on 12/02/2021. Prototype moved to Figma and links to documents added on issue description. To review: I would like to discuss the message modal on page 2: For V1, should we create a feature to allow the admin to edit the message or should we just show a preview?
@gigicobos I rewrote the issue to be clearer about what the purpose of the issue is and the title. I also added a link to the figma
Issue #1131 must be completed before work can continue on this issue.
Moved to Icebox as per my chat with Bryan. This fits into a medium to long term milestone.
@sei1122 Assigned to you as per the conversation in the fola Slack channel, and the reprioritization as as per @rylantalerico
@sei1122 What is your time estimate on this issue, given what has already been checked off in the Overview? Do you think you can get this done within the next 2 weeks?
I am adding the heuristics issues to the Prioritized Backlog as it is a priority for the Impact Sprints 2022, so I want to get an idea of when you might be able to pick up your next issue.
And keep in mind we are looking to add more UI-UX people to the project so don't get too overwhelmed at the number of issues that are being moved to the Backlog column, or by all of my questions about the UI-UX issues :).
This issue takes more than 2 weeks. I need to talk about how far it is done, validate the design, and may need user testing too.
I can take Heuristic issues first if it is the priority. Let me know which issue I should work on
@rylantalerico FYI, as per Seiko's comment above and Heuristics being an Impact Sprints 2022 priority, I am moving this to the Prioritized Backlog. I'd like to get as many of the Heuristics issues handled by the end of August as possible, and then we can revisit this one as a priority in early September.
@jelenaUX @cheesarah I assigned this issue to you as per UX Research Map of Content/ Index
@GigiUxR I'd like to be looped into this as the issue progresses. And if the issue needs more hands, John H might be interested in contributing.
Hi @GigiUxR @staceyrebekahscott @cheesarah as per @fancyham request I am adding a link to some competitive research on a similar self-updating feature from Google -- now all stored in a dedicated file in the Org Research Folder: https://docs.google.com/document/u/0/d/152kjzbXma59_85G9hseZ5AHETb-M7nt4yZAAgyldd7M/edit
@yiminng and I were discussing that it might be helpful if this were broken into 2 separate issues, one about the email reminder and one about the organization self-update interface. Upon further investigation i see that this is an Epic issue to track all the parts of this experience so we probably just need a dependent issue about the email reminder.
@fancyham @sei1122 @GigiUxR @staceyrebekahscott - any objections or am i missing something in my understanding?
I would defer to the UX Research team to see if a separate issue is necessary, or if they can track progress within this one.
It's definitely two parts so I think a split makes sense.
The email self-service flow could certainly work with the current free-form text 'suggestion/correction' interface with minor changes, and that would work as an MVP (minimum viable product).
Making a better 'edit my listing' screen is optional though very nice to have, but it shouldn't be a blocker, and so could be a separate issue.
Even that updated 'suggest edits' form could be done as an MVP as well. (for example, they can view their current listing, and if they want to submit a change, they press a button to reveal a text field that they enter their changes. Upon submitting, the freeform text field(s) could be aggregated into a single text-only suggestion, which is entered into our current 'suggest a correction' flow)