Template:Event/doc1: Difference between revisions
m (→Proposal 2) |
m (→Proposal 2) |
||
Line 29: | Line 29: | ||
'''milonga 7 cc desc''' | '''milonga 7 cc desc''' | ||
milonga <numeric weekday> <country code [alpha-2]> <description [ | milonga <numeric weekday> <country code [alpha-2]> <description [24char]> | ||
chars = 7+1 +1+1 +2+1 +24 = 37 | chars = 7+1 +1+1 +2+1 +24 = 37 | ||
e.g. milonga 3 de roter salon berlin | e.g. milonga 3 de roter salon berlin | ||
'''m7 cc desc''' | '''m7 cc desc''' | ||
m<numeric day of week> <country code [alpha-2]> <description [ | m<numeric day of week> <country code [alpha-2]> <description [24char]> | ||
chars = 2+1 +2+1 +32 = 30 //less good for search engines | chars = 2+1 +2+1 +32 = 30 //less good for search engines | ||
e.g. m3 de roter salon berlin | e.g. m3 de roter salon berlin | ||
'''7 milonga cc desc''' | '''7 milonga cc desc''' | ||
<numeric weekday> milonga <country code [alpha-2]> <description [ | <numeric weekday> milonga <country code [alpha-2]> <description [24char]> | ||
chars = 1+1 +7+1 +2+1 +32 = 37 | chars = 1+1 +7+1 +2+1 +32 = 37 | ||
e.g. 3 milonga de roter salon berlin | e.g. 3 milonga de roter salon berlin | ||
'''7 cc m desc''' | '''7 cc m desc''' | ||
<numeric weekday> milonga <country code [alpha-2]> <description [ | <numeric weekday> milonga <country code [alpha-2]> <description [24char]> | ||
chars = 1+1 +2+1 +1+1 +24 = 31 | chars = 1+1 +2+1 +1+1 +24 = 31 | ||
e.g. 3 de m roter salon berlin | e.g. 3 de m roter salon berlin |
Revision as of 2009-03-07T19:57:24
This is the documentation for creating an event of type milonga.
Proposal 1
Article title should be "Milonga [A-Za-z0-9]", i.e. start with the word Milonga in uppercase, followed by a space, followed by some description. The description can have maximum 32 characters.
|name = //if not filled uses article title |day = //1 = monday, 2 = tuesday, 3 = wednesday .... |week = //8 = every week, 6 = even week, 7 = odd week |time_start = //HH:MM local time |time_end = //HH:MM local time |country = |un_locode = |geo_lat = //decimal |geo_lon = //decimal |url = //other name: link? website?
to discuss
|status = //e.g. closed, or better closed = yes? |not = //dates where it does _not_ occur, //but maybe better handled via single events, //see add_event, where the description should //contain the milonga article name, or the wiki page id
Proposal 2
Stores more data in the title. Since page renaming is disabled only stable data shopuld 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.
milonga 7 cc desc milonga <numeric weekday> <country code [alpha-2]> <description [24char]> chars = 7+1 +1+1 +2+1 +24 = 37 e.g. milonga 3 de roter salon berlin
m7 cc desc m<numeric day of week> <country code [alpha-2]> <description [24char]> chars = 2+1 +2+1 +32 = 30 //less good for search engines e.g. m3 de roter salon berlin
7 milonga cc desc <numeric weekday> milonga <country code [alpha-2]> <description [24char]> chars = 1+1 +7+1 +2+1 +32 = 37 e.g. 3 milonga de roter salon berlin
7 cc m desc <numeric weekday> milonga <country code [alpha-2]> <description [24char]> chars = 1+1 +2+1 +1+1 +24 = 31 e.g. 3 de m roter salon berlin
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.
Seasonal milongas (outdoor) should have start year in the title and the end date in the template.
possible similiar notations tango.info/3m-38n40w-30km - milongas wednesday 30km around 38 N 40 W