Mercurial > hg > rsof
comparison 7vt/Reopening/notes.txt @ 192:86ffef4ee862
Tentative design for priority-to-newcomers
| author | Henry Thompson <ht@markup.co.uk> |
|---|---|
| date | Sat, 22 Aug 2020 15:39:04 +0100 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 191:ad86c5087951 | 192:86ffef4ee862 |
|---|---|
| 1 Trial of odoo now running at | |
| 2 http://markup.co.uk:8069/event | |
| 3 | |
| 4 website menu field is for individual event page... | |
| 5 | |
| 6 No obvious support for a recurring event | |
| 7 | |
| 8 Edit this | |
| 9 /usr/lib/python3/dist-packages/odoo/addons/website_event/views/event_templates.xml | |
| 10 to e.g. change 'Register' to 'Request place(s)' | |
| 11 | |
| 12 Hmm. Message goes to registrant, but not to admin... | |
| 13 | |
| 14 Need to find sources... | |
| 15 What would it take to do a priority-to-newcomers queuing system for | |
| 16 7vt MfW? | |
| 17 1) Database with tables | |
| 18 a) adult, with id, name, email (key), household (fk), headOfHousehold (bool) | |
| 19 b) household, with id, num adults, num children | |
| 20 c) child, with id, name (key1), parent1 (fk), parent2 (fk), household (key2) | |
| 21 d) meeting, with id, date, start, end | |
| 22 e) roomUse, with id, event (fk), room, numAvail (int), numHeldBack (int) | |
| 23 f) request, with id, event (fk), household (fk), numAdults, allOrNone (bool), numChildren, timestamp | |
| 24 g) booking, with id, request (fk), room (fk), accepted (int), turnedUp (int) | |
| 25 2) Actions/forms | |
| 26 a) Register a household | |
| 27 b) Edit a household | |
| 28 c) Request a booking | |
| 29 d) Show requests/bookings (with expected status for requests, | |
| 30 e.g. currently nth of m for room | |
| 31 e) Cancel a request/booking | |
| 32 f) Make bookings and notify head of household for all requests, | |
| 33 including position on waiting list if not accepted w/o | |
| 34 qualification | |
| 35 g) Notify new winner(s), new waiting list positions, on cancellation | |
| 36 | |
| 37 Doesn't as proposed allow for different categories of children, | |
| 38 i.e. this really only works for meeting room use for All Age, not | |
| 39 breakout rooms yet. | |
| 40 | |
| 41 Do we want to require an acknowledgement? | |
| 42 | |
| 43 Waiting list are allowed to turn up, possibly be admitted at 10 past | |
| 44 to empty places from heldBack and no-shows. | |
| 45 | |
| 46 Priority based on | |
| 47 1) inverse number of previous attendances | |
| 48 a) with no-shows counting double? | |
| 49 b) with some relief depending on how long ago? | |
| 50 2) time of request | |
| 51 | |
| 52 I.e. compute a score based on previous attendance, then sort by that | |
| 53 score, lowest first, and within requests with the same scores, by | |
| 54 request time, fill room(s) from the top down. If adding a | |
| 55 larger-than-one household won't fit, if no children and not allOrNone, | |
| 56 accept as many adults as possible. If there's another room, move | |
| 57 remnant if any there, otherwise move to waiting list, along with | |
| 58 everyone thereafter, in order. | |
| 59 | |
| 60 No groups including children on waiting list? |