You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Events have treasury departments. Event management software should recognize and support this.
Features (in no particular order):
Have a page where departments that need cash can set up their schedules, and choose which cash box profile best fits their needs from a (radio button) list of said profiles.
Schedule is first delivery time for each day, end time for each day, and interval in hours.
Might need a radio button for departments which only need one cash box per event or per day, or the above profile.
Have a page where Department heads can select which of their staffers (or already existing roles) can sign for cash boxes. This needs to be a new cross-department role. This is the part where I expect to most need help.
Config file needs to include which departments even get cash to begin with. Per conversation with Vicki, have a checkbox for this in the DB.
Use the above data to generate:
the ledger spreadsheet file for the event (this is easy)
generate the correct number of signing sheets for the event
generate lists of who is allowed to sign
generate locations? (is which room which department is in stored in Uber/Reggie anywhere?)
generate the list of who is allowed in the treasury room
Have a "monopoly$" add-on for the above (for mpoints), which doesn't have to be included.
A page for departments to put in event mpoint requests, with entry fields for each denomination each day.
Preferably this automatically deducts from the department's budget for the event, with the latter stored in configuration. Mpoint budgets under discussion.
Again, have department heads able to select which of their staffers can sign for mpoints, with this as a role for all departments receiving mpoints.
Use this to generate the correct number of mpoint signing sheets, and appropriate pages in the ledger.
I can handle most of this; in particular, the generation of other files and materials is a solved problem. I don't anticipate the UI portions of this being excessively annoying.
Are there any good resources for how to use the API for this?
The text was updated successfully, but these errors were encountered:
Everything I know about the API is here: https://staging-west.reggie.magfest.org/api/reference (this is a staging server, so if you don't already know you can access the admin section with email [email protected] and password magfest). It looks like we'd need to add API calls specifically for the dept head checklist, which sounds like a solid feature to have in general.
Events have treasury departments. Event management software should recognize and support this.
Features (in no particular order):
Have a page where Department heads can select which of their staffers (or already existing roles) can sign for cash boxes. This needs to be a new cross-department role. This is the part where I expect to most need help.
Config file needs to include which departments even get cash to begin with.Per conversation with Vicki, have a checkbox for this in the DB.Use the above data to generate:
generate locations? (is which room which department is in stored in Uber/Reggie anywhere?)Have a "monopoly$" add-on for the above (for mpoints), which doesn't have to be included.
A page for departments to put in event mpoint requests, with entry fields for each denomination each day.
Preferably this automatically deducts from the department's budget for the event, with the latter stored in configuration.Mpoint budgets under discussion.Again, have department heads able to select which of their staffers can sign for mpoints, with this as a role for all departments receiving mpoints.
Use this to generate the correct number of mpoint signing sheets, and appropriate pages in the ledger.
I can handle most of this; in particular, the generation of other files and materials is a solved problem. I don't anticipate the UI portions of this being excessively annoying.
Are there any good resources for how to use the API for this?
The text was updated successfully, but these errors were encountered: