====== Event-Manager ======

---- dataentry project ----
name                : Event-Manager
git-url_url         : 
project-description : C3VOC event logistics and planning 
project-owners      :  
project-member      : 
project-status_     : idea 
----


**This is mostly a requirements list for a to-be-written tool.**

The C3VOC event manager solves some always occurring issues with event logistics and planning.

What we want is:
  * overview of what events are upcoming
  * overview of how many flight cases are assigned to each event
  * logistics information


== 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 important bits here are:
  * event name
  * event location (city and country)
  * how many rooms are there
  * how many cases are assigned (and, if available, which ones)
  * duration of the event
  * state of the event (request, planning, confirmed, ...[TODO])

==== View: event details

Same information as in the overview, but also:
  * c3voc contact
  * event address
  * begin and end of event
  * begin of buildup and end of teardown
  * event contact (name, e-mail, phone number)

Scheduling and production info:
  * schedule url
  * event acronym/slug (used for URLs and stuff)

For delivery and pickup, we also need this information:
  * delivery address
  * delivery contact (name, e-mail, phone number)
  * earliest delivery date
  * latest delivery date
  * extra delivery instructions
  * pickup address
  * pickup contact (name, e-mail, phone number)
  * earliest pickup date
  * latest pickup date
  * 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.

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:lager-wiesbaden|Lager Wiesbaden]] via Google Chat).


== Analysis 

…