ubersystem
ubersystem copied to clipboard
magfest
As a Treasury DH, I would like uber to make my life easier.
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?
How about this?
Current formats
- Creed -> Article
- Canon -> Articles
- Catechism -> Catechism
- Confession -> ChaptersOfArticles
- HenrysCatechism -> CatechismOfCatechisms
Future formats
- ChapterCatechism -> CatechismOfArticles
How about this?
Current formats
- Creed -> Article
- Canon -> Articles
- Catechism -> Catechism
- Confession -> ChaptersConstructedOfArticles
- HenrysCatechism -> CatechismConstructedOfCatechisms
Future formats
- ChapterCatechism -> CatechismConstructedOfArticles
Current formats
- Creed -> Article
- Canon -> Articles
- Catechism -> Questions
- Confession -> ChaptersConstructedOfArticles
- HenrysCatechism -> QuestionsConstructedOfQuestions
Future formats
- ChapterCatechism -> QuestionsConstructedOfArticles
It seems that what you're looking for is a standard way of asserting different value classes (key names).
My background is in ontologies and standards for linked data, so maybe this suggestion is overkill, but it might help to have generic types that are reusable and whose meaning stays the same no matter where the information shows up. So, whether they show up in a creed or a catechism or a confession, it doesn't matter -- a proof gets the key "proof" and the value is the string literal, a chapter gets "chapter" as a key, section is "section", a question gets the key "question", a license gets "license", etc. A question with a number is just a unique element ("question") and it has an ID ("1").
Then assert that the JSON object is part_of / has_part the object. Viola. All 107 questions that are part_of the WSC are the WSC questions.
Too much?
We have a fairly defined structure (types) and the tests assert that this structure is followed. The issue here is have a predictable naming structure for different creed documents. We currently have:
CreedDocument<CreedContent>CreedDocument<CanonArticle[]>CreedDocument<ConfessionChapter[]>CreedDocument<CatechismQuestion[]>CreedDocument<HenrysCatechismQuestion[]>