Facebook integration

https://developers.facebook.com/docs/graph-api/reference/event/

uid     = identifikace
stats   = statistiky
meta    = to co je dulezite pro uzivatele (n)
log     = dodatečné informace které ma smysl logovat
deep    = data pro analytiku / tracking / personalizaci
report  = data pro tvorbu reportu z proběhnuté akce


uid         id - The event ID
stats       attending_count - Number of people attending the event
co to je?   category - The category of the event
meta        cover - Cover picture
stats       declined_count - Number of people who declined the event
meta        description - Long-form description
meta        end_time - End time, if one has been set
meta        event_times - Array of times of a multi-instance event
stats       interested_count - Number of people interested in the event
meta        is_canceled - Whether or not the event has been marked as canceled
log         is_page_owned - Whether the event is created by page or not
stats       maybe_count - Number of people who maybe going to the event
meta        name - Event name
stats       noreply_count - Number of people who did not reply to the event
log         owner - The profile that created the event
log         parent_group - The group the event belongs to
meta        place - Event Place information
meta        start_time - Start time
meta        ticket_uri - The link users can visit to buy a ticket to this event
meta        ticket_uri_start_sales_time - Time when tickets go on sale
log         ticketing_privacy_uri - URI to seller's privacy policy for ticket purchases
log         ticketing_terms_uri - URI to seller's terms of service for ticket purchases
meta        timezone - Timezone
meta/log    type - enum {private, public, group, community} The type of the event
uid         updated_time - datetime

log         admins - Users that are admins of the event
deep        attending - Users attending the event. Requires an access token of an Admin of the Event
deep        declined - Users who declined the event invitation. Requires an access token of an Admin of the Event
deep        interested - Users interested in the event. Requires an access token of an Admin of the Event
report      comments - Comments on the event. Requires an access token of an Admin of the Event
report      live_videos - Live videos published to the event. Requires an access token of an Admin of the Event
deep        maybe - Users who replied "maybe" to the event invitation. Requires an access token of an Admin of the Event
deep        noreply - Users who have not replied to the event invitation. Requires an access token of an Admin of the Event
report      photos - Photos published to the event. Requires an access token of an Admin of the Event
co to je?   picture - Profile picture
log         roles - List of profiles having roles on the event. Requires an access token of an Admin of the Event
report      feed - The feed of posts (including status updates) and links published to this event's wall.

Storage example of a timepixel. This might work if all fb events share the same access token (they probably wont). So here we'll have to either store with each fbevent data its own access token (i.e. by putting the access token within data.fbevents.data), or by insisting, that each timepixel can have only a single fb event (Seems reasonable but on the user interface, this would still require the possibility to add multiple fb events. If more then 1 fb events would be added, a timepixel would have to split into subpixels, each having a unique fb event). We might also force one main fb event but allow additional sub fbevents, which might be used just to get the bigger picture (my hunch feels good with this sofar - if we'd go this way, we'd have to add a flag to the data array item identifying the main event)

{
	"data": {
		"classification": "event",
		"...": "...",
		"fbevents": {
			"data": [{
				"uid": "facebook-id-of-the-event",
				"...": "..."
			}],
			"access-token": "t+czJ5Ej2PXT1ncltASZOVsmiUJR2E8vMK"
		}
	}
}