openpantry / open_pantry Goto Github PK

Must be able to edit a user's permissions upgrade/downgrade
This ability granted to Administrator

Use zip code to look up city and state in credit card form. reduces entry

Contact

• Google Translation
• Per Mondo
• Microsoft Translation services

If a user wanted to log in on their phone/home computer and change the number of household members or edit address etc, can they?

This needs answering:
Is it possible for users to create an account in advance and simply provide photo id/paperwork to verify in person?

Pros:

reduces in person sign up time
Is there a con to this?

When a client places an order it is possible to print out a ticket for fulfillment

The interface functions in a language and use flow that is accessible to aid devices, differing literacy levels and languages

At some point, a guest will place an order for an item that is not actually in stock. The volunteer fulfilling that portion of the order must be able to remove the items from the guests order and re-credit their account.
They should also be able to remove that item from inventory until its quantity can be rectified to prevent further orders.

Acceptance Criteria

• When a staff member enters a guest number. If there's a placed order for that day, a button will appear that says, "Modify Order"
• The following screen will be a list of the items in the order and their quantity.
• The Staff member can reduce the amount of an item, or all of something.
• If they do so, a question will pop up asking if that item is no longer in stock.
  • On confirmation, it will ask for a passkey (This will be a number that we designate that only the staff member in charge knows to prevent something being removed simply because the staff member couldn't find it).
• value of noms will be credited back to order number

In donation checkout, modify the form so that we use single text box credit card information with masking.

The user should be able to see what they have reserved and the noms available to them still.

Acceptance Criteria

• There is a button on the ordering page with a shopping cart icon.
• When they click it, a pane/slide out or a modal pops up.
• This modal will list the items they have reserved, each item's value in noms and and the total of each category.
• There will be a "Finish" button.

Guests receive an order that they made.

We have over 90% drop off on volunteer page.
This needs tender love and care

There will be multiple versions of this software running on different tablets simultaneously. Different users will be making different orders and therefore should not affect each other byond stock totals diminishing upon finalization.

Acceptance Criteria

• Independent instances on different hardware can be in progress simultaneously
• Credit deductions in one instance do not affect the credits of another instance.

Construct new page

A guest will be given a ticket and a form to fill out when they arrive. These tickets will be used to determine order of service and to ensure we give the correct package to the person who ordered.

Acceptance Criteria

• On Start screen there is a field to enter the guests number.
• An alert shows the number entered and asks if this is correct.
• If there is not an order associated with that number, the staff member can select, "begin new order"
  • On confirmation it goes to language screen.

Fields: Names, Address, Phone Number, Email, okay to text? prefer contact email/text/mail, language preferences email/password SSO?
Link to other accounts designated to allow pick up

Package is somehow linked to person so that a different user does not pick up someone else's food package
Possibilities are ID verification or ticket.

• Barcode of package scanned
• Check's UPC/USDA db for presence of item.
• If not present, requests information regarding, item, package size and classification (if known)
• If present updates database with quantity.
• Returns positive confirmation.

API allows modifications to user account data.

A live updating database of all inventory with stock locations which can have items added or subtracted.

Guest can delete an item/adjust quantity this quantity is released back into the general inventory

Acceptance Criteria

• A guest can reduce the amount of an item that is in their order.
• When they do so that quantity is released back into the available invnetory

Make sure that the pages incorporate ARIA accessibility features.

User accounts are created and stored in a database. Information is updatable and relational. ie family members can link their accounts and pool resources. Children under a certain age (What do St john's bread and life and West side coalition use?) are on their parents account.

This will allow a user to edit their personal information.

If they change required information (address, name, contact information, people associated, must reverify)

We have a pretty poor funnel for donations. Something like 76% of people reaching our donate page get lost along the way.

AC:

• A user has one level of permissions.
• Permissions allow behavior as described below

Levels:
Each subsequent level includes prior permissions.

• Guest*
  • Can edit own information
  • Can order a package of food.
• Administrative-
  • Can edit all features of users and database.
  • Can checkout large quantities of food.
  • Can rectify inventory.
  • Can edit/cancel an order.
  • Can clock in/out
  • Activity logged
  • Can add food to inventory.

When an ordering page, a guest can select a quantity of an item and place it in their cart.

Acceptance Criteria

• A guest can select a quantity of an item to reserve.
• If the guest has sufficient credits and the item is still in stock, that quantity of the item is removed from inventory. And the credits are deducted from their total for that category.

As a Requirement to EFAP, we must be able to give someone a package of food without them creating a user account.
Questions:

• How do we prevent guests from coming and demanding packages in addition to their registered package? (Ideas: only twice a month for anonymous packages,
• [ ]

The new site will have:
XX Pages

• Main/Landing
• I'm Hungry and want to Eat
• Donation
• Volunteer
• Campaigns
• About
• In the Media
• Blog

Guests will be able to see a list of items that are available to them, and their available credits (noms) so that they can order

Acceptance Criteria

• When a guest reaches the ordering pages they will be presented with a list of items that they can choose from in one category (grains, protein, vegetables) with the size, number remaining and the credit value of the item.
• The noms (credits) available to the guest for that category are shown at the top.

A guest will be able to read the tablet in their language

Acceptance Criteria

• The first screen will be a language selection page.
• Upon selection, all guest-oriented pages (food lists, and shopping cart, notices, etc) will be in that user's language
• Staff-facing pages will be in English at least initially.
• Languages must include
  • Yiddish
  • Spanish
  • Russian
  • Uzbek
  • Mandarin (both Traditional and Simple)
  • Cantonese (both Traditional and Simple)
  • Arabic
  • Urdu
  • Hindi
  • French
  • Creyole

Clinet interface final design completed based on use flow

We give out food according to the myplate ratios.

Items will be organized by the following categories; Fruits & Vegetables, Grains, Proteins, Miscellaneous, in the future (Complete Meals)
Each will have a distinct set of noms (our term for credits)

Acceptance Criteria

• There will be multiple tabs
• Items will be categorized by one or more tabs
• If an item is available in more than one tab, either type of noms (credits) can be used to procure it.
• Only items in stock will be shown.

There will be a holding space in which a quantity of items that are confirmed in stock by database can be removed from the general resource pool and allocated to a user's account. Credits will be deducted but can be added back if item deleted.

Once checkout button clicked, ticket printed,
someone fulfills order, if an item on ticket is not available when staff attempts to fill an order, administrator can remove.

Ways items added:
User selects a quantity and adds to cart.
Administrator adds an item to all carts.

Ways items removed
User Deletes
User adjusts quantity
Administrator deletes
Administrator adjusts permitted quantity.
Log out
Inactivity for 5+ minutes empties cart.

Submit a questionnaire to patrons of food pantry.

Acceptance Criteria:

The system will store specific information about a user.
Ticket is done when you can write to the database, does not include any front-end.

A client can securely place an order, It is fulfilled and delivered to them.

An item can be placed in a shopping cart, credits are deducted from their account.

The current Masbia Site needs a lot of TLC. New version needs to be designed in order to improve usability and conversion for both donations and volunteer forms

When a guest click's the "finish" button it is considered complete from their end. And a graphic appears indicating they should hand it back to the staff member.

Acceptance Criteria

• Clicking the button gives a verification dialogue

AC:

• A user has one level of permissions.
• Permissions allow behavior as described below

Levels:
Each subsequent level includes prior permissions.

• Guest - mvp
  • Can edit own information
  • Can order a package of food.
• Volunteer
  • Can clock in/out
  • Activity logged
  • Can add food to inventory.
• Order Fulfillment
  • Can edit/cancel an order.
• Local Branch Staff
  • Can checkout large quantities of food.
  • Can rectify inventory.
• Administrative- mvp
  • Can edit all features of users and database.