Tango.info milonga

THIS IS A PROPOSAL - IT IS NOT IMPLEMENTED YET

This is for repeated milongas, single milongas should use add event

Primary Data Storage

Article title

Since page renaming is disabled for regular users, only stable data should go into title. Location and day of week are typically stable. Milongas that are not stable in that respect could use single event registration: add event.

Other data which is harder to compress and maybe less stable goes into template:milonga. Coordinates are typically stable but on article creation there may be errors.

• datetime
  • Weekday numbers according to ISO 8601, 1 = monday ... 7 = sunday
  • Repetition numbers - either here or in template : see tango.info weekday repetition
• summary - could go into the iCal summary field
• location
  • in title - alpha-2 country code or ISO 3166-2 subdivision code or UN/LOCODE city code
  • in template - allow more specific, e.g. coordinates

milonga 7 cc summary
milonga <numeric weekday> <country code [alpha-2]> <summary [24char]>
chars = 7+1 +1+1 +2+1 +24 = 37
e.g. milonga 3 de roter salon berlin

m7 cc summary
m<numeric day of week> <country code [alpha-2]> <summary [24char]>
chars = 2+1 +2+1 +24 = 30 //less good for search engines
e.g. m3 de roter salon berlin

7 milonga cc summary
<numeric weekday> milonga <country code [alpha-2]> <summary [24char]>
chars = 1+1 +7+1 +2+1 +24 = 37
e.g. 3 milonga de roter salon berlin

7 cc m summary
<numeric weekday> milonga <country code [alpha-2]> <summary [24char]>
chars = 1+1 +2+1 +1+1 +24 = 31
e.g. 3 de m roter salon berlin

Seasonal milongas (outdoor) should have start year in the title and the end date in the template.

Template:milonga

Template:milonga will have additional fields.

Text body

Free text, or maybe a table which has data for specific dates

Secondary Data Storage

There will be a meta table, filled with processed data from the title and template.

See also

possible similiar notations
tango.info/3m-38n40w-30km - milongas wednesday 30km around 38 N 40 W