Tango.info event system - most disturbing

Maybe it is the best to start with

• a Wicket implementation for one time events in general and then extend to festivals and to repeated events
• IDs that use <4 char year of event addition to ti><6 char ti base 20, starting with xtfbbb and for 2012 starting with xtbbbb> and later add the use of country codes within the event codes for new events

Current system

Currently there are three work flows for adding events:

• one time event, type festival or marathon (in future allow child events)
  • work flow: https://tango.info/add/festival -> email to Tobias -> events.csv -> mysql tidb_all.tango_events and tidb_all.tango_events_artists
  • ID format: <year start><UN/LOCODE|or ti city code><one letter>, e.g.: https://tango.info/2011rumowm
  • last letter is chosen manually by Tobias and may relate to festivals name (m = milonguero nights)
  • sometimes a location has no UN/LOCODE, manually decide on a code
• one time event except for Festivals/Marathons and repeated event except for Milonga/Practica:
  • work flow: https://tango.info/add/event -> wiki -> hook on ArticleSave OR script at https://tango.info/eventmanager -> mysql tidb_all.tango_events
  • a location can be pre-selected via URL, https://tango.info/add/event/?geo=DEBER-CL
  • immediately visible
  • data only taken from article title, e.g. https://tango.info/wiki/2011-06-13_15h00--22h00_DEBER-RS_Milonga_Openair_-_Tango_Cafe_im_Radialsystem
  • the types Milonga/Practica/Lesson/Workshop/Concert/(none) have to be typed by hand, select box would be better
  • organizers cannot specify time via the form, they cannot modify the page title nor can they mark the event as canceled
  • ID format: <year when event was added><xt><wiki article number as tango.info base20>, e.g. : https://tango.info/2011xtcpcb
• repeated event, Milonga, Practica:
  • work flow: structured title in wiki, Tobias only -> hook on ArticleSave OR script at https://tango.info/eventmanager -> mysql tidb_all.tango_events
  • immediately visible
  • organizers can only edit via wiki, this is too complicated, and they can edit only the info that comes via parsing
  • announcements for specific dates not possible work around [1]
  • cannot be take off if it does not take place on a specific day
  • data taken from article title and some html parsing, e.g. https://tango.info/wiki/Milonga_Every_Tue_21h15_DEBER-CA
  • ID format: same as "one time event except Festival", e.g.: https://tango.info/2010xtcjkf

Desired

It would be nice to have this all working without wiki and without csv upload. Data should go directly to the DB. Logging of historic data would be nice, so one can see how the artists announced to come to an event or the start times have been changed by the organizer over time.

Desired for the ID /[0-9]{4}[a-z]{6}/: <YYYY - event start - 4 chars><cc - country code if possible - 2 chars><counter in ti base 20 - 4 chars>

• 2011-06: In the beginning the letter part could be a simple counter, avoiding coding country codes into the system. The year could be the time of creation, as in current wiki system. The Java codes could start with 2011xtfbbb. Current codes from the wiki system are at around 2011xtcpcb.
• Future: ID for one time event should start with the start year of the event. For repeated events it should be the year of when it was added to the system. The year can be followed by the country code for the primary location of the event. This allows for 20^4 = 160 000 events per country. This makes for easier reading of the code by people from one region. Nevertheless, if codes are used up, other ranges may be needed. But at least people from countries with few events have some benefit of short codes.