Tango.info event system - most disturbing

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: http://m.tango.info/add/festival -> email to Tobias -> events.csv -> mysql tidb_all.tango_events and tidb_all.tango_events_artists
  • ID format: <year start><unlocode|or ti city code><one letter>, e.g.: http://www.tango.info/2011rumowm
  • BAD last letter is chosen manually by Tobias and may relate to festivals name (m = milonguero nights)
  • BAD sometimes a location has no UN/LOCODE
• one time event and repeated event except for Milonga/Practica:
  • work flow: http://m.tango.info/add/event -> wiki -> hook on ArticleSave OR script at https://www.tango.info/eventmanager -> mysql tidb_all.tango_events
  • GOOD a location can be pre-selected via URL, http://m.tango.info/add/event/?geo=DEBER-CL
  • GOOD immediately visible
  • data only taken from article title, e.g. http://www.tango.info/wiki/2011-06-13_15h00--22h00_DEBER-RS_Milonga_Openair_-_Tango_Cafe_im_Radialsystem
  • BAD the types Milonga/Practica/Lesson have to be typed by hand, select box would be better
  • BAD 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 http://www.tango.info/wiki/tango.info_base20>, e.g. : http://www.tango.info/2011xtcpcb
• repeated event, Milonga, Practica:
  • work flow: structured title in wiki, Tobias only -> hook on ArticleSave OR script at https://www.tango.info/eventmanager -> mysql tidb_all.tango_events
  • GOOD immediately visible
  • BAD organizers can only edit via wiki, this is too complicated, and they can edit only the info that comes via parsing
  • BAD announcements for specific dates not possible work around [1]
  • BAD 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. http://www.tango.info/wiki/Milonga_Every_Tue_21h15_DEBER-CA
  • ID format: same as "one time event, all other types", e.g.: http://www.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><ti base 20 - 4 chars>

• 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.