cseg-michigan / chez-betty Goto Github PK

e.g. this shouldn't 501

http://chezbetty.zakird.com/admin/transactions/50

We shouldn't leave large piles of cash sitting around

Instead of clearing out a whole row, there there should be a "-1" button allowing users to buy one less of something (e.g. I accidentally scanned 6 Nutrigrain bars when I'm only buying 5).

Or more specifically, it should use this: http://docs.sqlalchemy.org/en/rel_0_9/core/types.html#sqlalchemy.types.Numeric

This needs to be fixed before we deploy, it will be impossible to fix later.

If someone does something silly and ignores the plainly written directions (now, what kind of person would do that?) and scans a barcode first, they can no longer swipe an MCard.

Because we're bad at them

But Square has no payments API. Assigning to @ewust to fix.

For example, when the cash box is emptied, it generates two transactions, one for actual cash -> chezbetty, one for missing cash -> lost, but this is really one event and it would be desirable to link them visually.

Trigger-happy folks should be given an "undo purchase" option on the purchase complete page. This should return them to the purchase page populated with their already selected items.

At least one user has paid to the QR code shown, and then added their deposit manually (before the page redirected, apparently), which creates a "false" deposit to cash box.

Perhaps "pay with bitcoins" or the bitcoin accepted here logo should link to a separate page that doesn't list the pin-pad? Or we could just add instructions to the deposit page? Or maybe a big "OR" between the two boxes.

The enter key doesn't work. In firefox or chrome. Confirmed by @zakird. Holy crap is that annoying.

So CB can generate a shopping list (or some day auto place an order)

Tried Branden and Noah and both failed.

Periodically, CB should pay off its losses from its profits. Should add an admin ability to create a transaction from chezbetty -> loss. Will also need an admin page @bradjc .

we should be able to remove money from CB -> CSEG via administrative interface. Backend support has been added.

Swiping a new mcard fails with 'not enabled' the first time a brand new user swipes.

As happened in #49, a mistaken deposit into the cashbox (without actually putting any money in) needs to be undone by an admin. An adjustment can work, but the cashbox will still appear short when we empty it.

Is there a good way to rollback a user's false deposit for them?

The scrollbar is basically unusable. We should add big "Up/Down" buttons for the pages that need them [ideally this would happen automatically when the scrollbar is shown, but that could be tricky. At the least, these should be on the items page and possibly the About page].

Add buttons for "swipe mcard" and "scan products x,y,z" for use when demoing the system without any of the associated hardware.

We should have a [daily?] DB backup or something somehow.

Yes, most of the traffic will be from the CB terminal, but I'd be curious if we get hits / traffic from anywhere else

Shouldn't money go from chez betty to store?

The virtual accounts/cash accounts could use some explanation or example transactions explaining how money moves through the system

Currently, a transaction of negative money from cashbox to lost is generated. That doesn't really map what's happening that well. It should a transaction of positive money from lost to cashbox. The next transaction after that should be the money from the cashbox to chezbetty.

(Yes, the net result is the same. Yes, this is a still a problem.)

Need a way to adjust chezbetty's accounts, e.g. if we get seed money from the department when we make our initial purchase we shouldn't start out deeply in debt.

Needs an admin page and backend support, but can't assign two people to one issue.

• The line in "cash transactions" labeled lost doesn't ever change.
• The lost account isn't updated when inventory is checked and adjusted. (In fact, running inventory doesn't generate any visible transaction) I now realize why that isn't a thing.

It's confusing that the sum of user "transaction history" != Account Balance.

1. Mirror everything except the cash boxes between the two account sides. So basically all transactions get duplicated to keep the accounts in sync.
2. We ditch making the virtual accounts track anything and basically only keep track of transactions with type "lost" and the user accounts and don't worry about the virtual "chez betty" account. This way we can see how much inventory we've lost and how much money we are keeping for users without keeping a bunch of other records that mean much more in the cash accounts.

Thoughts?

It occurs to me that we need more accounts.

Cash accounts

• donations: for misc money coming in to cb
• bitcoinbox: for holding money until we cash out bitcoins
• cseg: for taking money out of cb and into other cseg things

Virtual accounts

• store: need to remove this account. It doesn't reflect anything

Need pages to move money from donations to cb and from cb to cseg. Also lost to/from cb in case of weirdness somewhere

Now these pages aren't strictly necessary but it's worth it to have clearer data