Tango.info milonga: Difference between revisions

From tango.info wiki
Jump to navigation Jump to search
 
(25 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[category:events]]
[[Category:Tango.info]]
[[category:tango.info]]
  THIS IS A PROPOSAL - IT IS NOT IMPLEMENTED YET
  THIS IS A PROPOSAL - IT IS NOT IMPLEMENTED YET


This is for repeated events, single events should use [[add event]]
This is for repeated milongas, single milongas should use [[add event]]
 
See current example articles
https://tango.info/x/wiki/w/index.php?title=Special:WhatLinksHere/Template:milonga&hidelinks=1


==Primary Data Storage==
==Primary Data Storage==
===Article title===
===Article title===
Since page renaming is disabled 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]].
Since page renaming is disabled for regular users, only relativly stable data should go into the title. Location and day of week are ''typically'' stable. Milongas that are not stable in that respect should 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.
Other data which is harder to compress or typically less stable goes into [[template:milonga]]. Coordinates are typically stable but on article creation they may be unavailable.


* datetime
* datetime
** Weekday numbers according to [[ISO 8601]], 1 = monday ... 7 = sunday
** numeric
** Repetition numbers : see [[tango.info weekday repetition]]
*** Weekday numbers according to [[ISO 8601]], 1 = monday ... 7 = sunday
* summary - could go into the [[iCal]] summary field
**** Wednesday has 9 chars
*** Repetition numbers - either here or in template : see [[tango.info weekday repetition]]
** or use English names?
* location
* location
** in title - [[alpha-2 country code]] or [[ISO 3166-2]] subdivision code or [[UN/LOCODE]] city code
** in title - [[ISO 3166-1]] alpha-2 country code or [[ISO 3166-2]] subdivision code or [[UN/LOCODE]] city code
** in template - allow more specific, e.g. coordinates
** in template - allow more specific, e.g. coordinates
* event type - could go into the iCal category field
** alpha-1 code = m
** or use 'milonga'? better for search engines, easier to read
* summary - could go into the [[iCal]] summary field
TODO: The order of the elements is not decided yet. When-Where-What is used by [[tango.info one-time event]].
This scheme will be implemented. See [[:category:Milonga]]
'''Milonga Wed 135 21h00 ARBUE Canning'''
Other
Milonga Wednesday 135 21h00 ARBUE Canning
chars 7+1 +9+1 +5+1 +5+1 +24 = 54
'''7 cc milonga summary'''
<numeric weekday> <country code [alpha-2]> milonga <summary [24char]>
chars = 1+1 +2+1 +7+1 +24 = 37
e.g. 3 de milonga 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
'''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


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


  '''7 milonga cc summary'''
  '''m7cc summary'''
  <numeric weekday> milonga <country code [alpha-2]> <summary [24char]>
  m<numeric day of week> <country code [alpha-2]> <summary [24char]>
chars = 1+1 +7+1 +2+1 +24 = 37
  chars = 1+1+2+1 +24 = 29 //less good for search engines
e.g. 3 milonga de roter salon berlin
  e.g. m3de 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.
Seasonal milongas (outdoor) should have start year in the title and the end date in the template.


===Template:milonga===
===Template:event===
[[Template:milonga]] will have additional fields.
[[Template:event]] will have additional fields. They will be defined at [[Template:event/doc]]


===Text body===
===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==
== See also==
  possible similiar notations
  possible similiar notations
  tango.info/3m-38n40w-30km - milongas wednesday 30km around 38 N 40 W
  tango.info/3m-38n40w-30km - milongas wednesday 30km around 38 N 40 W

Latest revision as of 2013-06-11T22:17:36

THIS IS A PROPOSAL - IT IS NOT IMPLEMENTED YET

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

See current example articles https://tango.info/x/wiki/w/index.php?title=Special:WhatLinksHere/Template:milonga&hidelinks=1

Primary Data Storage

Article title

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

Other data which is harder to compress or typically less stable goes into template:milonga. Coordinates are typically stable but on article creation they may be unavailable.

  • datetime
    • numeric
    • or use English names?
  • location
    • in title - ISO 3166-1 alpha-2 country code or ISO 3166-2 subdivision code or UN/LOCODE city code
    • in template - allow more specific, e.g. coordinates
  • event type - could go into the iCal category field
    • alpha-1 code = m
    • or use 'milonga'? better for search engines, easier to read
  • summary - could go into the iCal summary field

TODO: The order of the elements is not decided yet. When-Where-What is used by tango.info one-time event. 

This scheme will be implemented. See category:Milonga 
Milonga Wed 135 21h00 ARBUE Canning

Other 

Milonga Wednesday 135 21h00 ARBUE Canning
chars 7+1 +9+1 +5+1 +5+1 +24 = 54

7 cc milonga summary
<numeric weekday> <country code [alpha-2]> milonga <summary [24char]>
chars = 1+1 +2+1 +7+1 +24 = 37
e.g. 3 de milonga 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

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

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 = 1+1+1 +2+1 +24 = 30 //less good for search engines
e.g. m3 de roter salon berlin

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

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

Template:event

Template:event will have additional fields. They will be defined at Template:event/doc

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
Retrieved from "https://tango.info/x/wiki/w/index.php?title=Tango.info_milonga&oldid=55893"