Tango.info event
Elements
If an element name is the same as a field name in tango.info iCal, then its possible values are restricted by the iCal definition.
Name | RFC5545 section | Values | Usage in tango.info |
---|---|---|---|
categories | 3.8.1.2 | milonga,festival,lesson ... | active |
class | 3.8.1.3 | considered | |
status | 3.8.1.11 | confirmed,cancelled | active |
summary | 3.8.1.12 | varchar(255) // -> tango.info event name | active |
comment | 3.8.1.4 | varchar(500) | active |
description | 3.8.1.5 | considered as standalone, currently for festivals this value is generated | |
geo | 3.8.1.6 | derived from location? | |
location | 3.8.1.7 | split into several fields, e.g. country | |
attendee | 3.8.4.1 | table: event_attendee contains artists | |
partstat | 3.8.4.1 ATTENDEE | accepted, declined, tentative | considered |
contact | 3.8.4.2 | <text> | considered |
organizer | 3.8.4.3 | considered | |
exdate | 3.8.5.1 | active | |
rdate | 3.8.5.2 | considered | |
freq | 3.8.5.3 RRULE | YEARLY, MONTHLY, WEEKLY | active |
interval | 3.8.5.3 RRULE | if interval=1, then empty. Only other value in tango.info currently: 2 | active |
byday | 3.8.5.3 RRULE | MO,TU,WE,TH,FR,SA,SU, 1MO,1TU,..,2MO,..,3MO,..,4MO, 5MO, -1MO,..,-1SU | active |
until | 3.8.5.3 RRULE | considered |