Confirm all import options are working as expected, make table of what sources support what features

[r-ferrier]

https://www.notion.so/gfsc/Kim-s-timeline-for-completion-12-3-24-d0e8ef7a03c44ba08e56d4477e3fea5d?pvs=4#866368f2339f483fa02cb409a1303e6e

[kimadactyl]

q from honor today was "what happens to the url field in ical?" just to record this

[ivan-kocienski-gfsc]

Having gone through all our supported sources I have mapped which fields we are pulling for each and how they map on to our event model.

field name →	uid	summary	description	dtstart	dtend	address	are_spaces_available	footer	publisher_url	online_address
Eventbrite	id	name.text	description.text	start.local	end.local	venue			url	url
ical	uid	summary	description	dtstart	dtend	location				x_google_conference
meetup	id	name	description	Time + utc_offset	Dtstart + duration	venue			link	link
squarespace	id	title	body	startDate	endDate				url
ticketsolve	id	name	description	opening_time_iso			status	url
ld+json	url	name	description	start_date	end_date	location.address
xml (manchester uni)	ns:id	ns:title	ns:description	(yes)	(yes)

[kimadactyl]

fantastic work ivan!

immediate thoughts:

• can we fill in any more blanks? (for e.g. is there really no address field for squarespace? does ticketsolve have no end date?)
• should room number be a sep field on our event model? (feel this is the one thing not clearly represented here)
• how can we maintain this going forwards? (can it be autogenerated or do we need a note to update it every time we tweak it somewhere?)
• the idea of "footer" was to give more context about where the event is coming from and link to it if appropriate - is this still the most appropriate place to give that info and the right name for the field?
• small note rows and cols are back to front on this (columns should be metadata, rows are data)

perhaps a new ticket, but on my mind:

• is event image a thing we can support if the source has it?

[kimadactyl]

oh and also does this answer honor's q, e.g. what happens to the URL field here?

[ivan-kocienski-gfsc]

fantastic work ivan!

immediate thoughts:

• can we fill in any more blanks? (for e.g. is there really no address field for squarespace? does ticketsolve have no end date?)

I think that'd be a fair chunk of work: we'd have to go through each source and figure out which fields best matches up with our columns.

• should room number be a sep field on our event model? (feel this is the one thing not clearly represented here)

Maybe but do all the sources support room numbers? The code doesn't really have a concept of a room number and when such a strategy is selected on the calendar it just jiggles around the fields in the address model.

• how can we maintain this going forwards? (can it be autogenerated or do we need a note to update it every time we tweak it somewhere?)

Has to be manually done.

• the idea of "footer" was to give more context about where the event is coming from and link to it if appropriate - is this still the most appropriate place to give that info and the right name for the field?

Can't really say but it feels like this was put in for some specific source at some point but is rarely used. Just checked on my local prod snapshot and it is never used. As no one is using it I would drop it.

• small note rows and cols are back to front on this (columns should be metadata, rows are data)

done.

perhaps a new ticket, but on my mind:

• is event image a thing we can support if the source has it?

Yes but how do we display that on the front end?

[kimadactyl]

Maybe but do all the sources support room numbers? The code doesn't really have a concept of a room number and when such a strategy is selected on the calendar it just jiggles around the fields in the address model.

No so the idea of the option is that people can use the location field to store a room number. This is for places like community centres who have a Outlook calendar and just want to put "big meeting room" in the location field for example.

Answers are all reasonable and need spinning into new tickets I think?

[katjam]

Closing as research part is done.