Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| projects:event-manager [2026/06/15 16:23] – created kunsi | projects:event-manager [2026/07/26 22:17] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ###### |
| + | |||
| + | ---- dataentry project ---- | ||
| + | name : Event-Manager | ||
| + | git-url_url | ||
| + | project-description : C3VOC event logistics and planning | ||
| + | project-owners | ||
| + | project-member | ||
| + | project-status_ | ||
| + | ---- | ||
| **This is mostly a requirements list for a to-be-written tool.** | **This is mostly a requirements list for a to-be-written tool.** | ||
| - | The C3VOC event manager solves some always-occuring | + | The C3VOC event manager solves some always |
| What we want is: | What we want is: | ||
| Line 10: | Line 20: | ||
| * logistics information | * logistics information | ||
| - | ===== overview | + | |
| + | ## Requirements | ||
| + | |||
| + | #### View: overview | ||
| The overview should replace the preexisting case calendar and the event planning in the wiki. The idea is that all events get input into the manager software, which in turn provides the wiki with a list of events and a nice graphical overview. | The overview should replace the preexisting case calendar and the event planning in the wiki. The idea is that all events get input into the manager software, which in turn provides the wiki with a list of events and a nice graphical overview. | ||
| Line 22: | Line 35: | ||
| * state of the event (request, planning, confirmed, ...[TODO]) | * state of the event (request, planning, confirmed, ...[TODO]) | ||
| - | ===== event details | + | #### View: event details |
| Same information as in the overview, but also: | Same information as in the overview, but also: | ||
| Line 33: | Line 46: | ||
| Scheduling and production info: | Scheduling and production info: | ||
| * schedule url | * schedule url | ||
| - | * event slug (used for URLs and stuff) | + | * event acronym/slug (used for URLs and stuff) |
| For delivery and pickup, we also need this information: | For delivery and pickup, we also need this information: | ||
| Line 46: | Line 59: | ||
| * latest pickup date | * latest pickup date | ||
| * extra pickup instructions | * extra pickup instructions | ||
| + | |||
| + | Also, invoicing information: | ||
| + | * invoice address | ||
| + | * invoice e-mail | ||
| + | * Umsatzsteueridentifikationsnummer | ||
| This information needs to be login-gated because it contains personal data of people. The delivery and pickup information should be copy-able from a previous event to make it easier to use. If pickup info is empty, then delivery information should be used as pickup info as well. | This information needs to be login-gated because it contains personal data of people. The delivery and pickup information should be copy-able from a previous event to make it easier to use. If pickup info is empty, then delivery information should be used as pickup info as well. | ||
| + | Delivery-, pickup- and invoice details must not be made available to any logged-in user, only the c3voc contact and the people responsible for transport and invoicing should be able to view that. | ||
| + | |||
| + | We also need (atleast PDF, probably generic) file upload per event, so people can attach shipping documents etc. to an event. Upload of new documents shall be announced to the relevant people (aka e-mail to the contact person, message in the C3VOC logistics chat in Matrix and message to the folks at [[intern: | ||
| + | |||
| + | |||
| + | ## Analysis | ||
| + | |||
| + | … | ||