Event JSON

[glenrobson]

Josh and I started discussing what the back end JSON should be to drive the events page:

https://preview.iiif.io/root/wireframe/news-and-events/

We currently have:

• calendar.json - this is updated once a day and gets the data from the IIIF calendar. It contains the meetings within the next 7 days and also the time and date for the next meeting of each group like 3d or D4H
• eventbrite.json - this is updated when eventbrite is edited. It contains all IIIF eventbrite events so training and annual conferences. Currently this is used on the training site to generate the link at the top to the latest training: https://training.iiif.io/iiif-online-workshop/index.html
• Google Sheets: generated from the Newsletter google form

@mnyrop could you let me know what data you would need for the website and I can look at combining the difference data sources into a single JSON for your use.

[mnyrop]

Notes (WiP):

{
  "label": "IIIF Outreach",
  "type": "call", // ["call", "event", "workshop", "conference"] ...?
  "description": "Zoom link: https://stanford.zoom.us/j/97934431714?pwd=UFBkUGZDaHZqaDcvK2ZsVE1MZys5UT09",
  "links": [
    {
      "label": "Google Calendar",
      "link": "https://www.google.com/calendar/event?eid=XzY5MGpjZ3BrOG9wamViYTI2c3EzYWI5azg5MmtjYjlvODRyNDJiYTY3NHBqMGhpMjc1MzM2ZGhrNm9fMjAyMTA5MjhUMTUwMDAwWiAxaG5tNWg4Nm45NG9yZTB2bm9vMTg4dGVyOEBn"
    }
  ],
  "time": {
    "start": {
      "dateTime": "2021-09-28T08:00:00-07:00",
      "timeZone": "Europe/London"
    },
    "end": {
      "dateTime": "2021-09-28T09:00:00-07:00",
      "timeZone": "Europe/London"
    }
  },
  "location": {
    "type": "remote", // ["remote", "irl", "hybrid"]
    "label": "Zoom", // Could say physical location
    "link": "https://stanford.zoom.us/j/97934431714?pwd=UFBkUGZDaHZqaDcvK2ZsVE1MZys5UT09" // could be google maps link
  }
},

[glenrobson]

Transferring conversation from Slack:

"Josh Hadro and Meg O'Hearn, Marii and I have just caught up on the event data for the upcoming events page and came across a few questions.

For the 4 (or 6) events on the first page, is it OK to do the first 4 events chronologically? This would be easiest to implement but would mean events like the fall working meeting won't appear until the week before it starts. Do we need to think of a way of 'sticking' certain events so they appear in the top 4 or do we prioritise eventbrite events? For the View All, do we stick with a weeks worth of calls and then any events in eventbrite and the newsletter spreadsheet?"

[glenrobson]

Josh's suggestions:

[glenrobson]

My proposal:

Featured events

Configured in the website (which we could manually highlight conferences / training / external events)

Upcoming calls

from the calendar.json shows the next 4 calls

View all

Chronologically ordered events from eventbrite + spreadsheet + calls in new events.json file

[glenrobson]

Just putting together the events.json and following the example you gave above. I came across the following questions:

• Do you need the timezone if I can provide full dates like: 2021-11-16T16:00:00Z
• Location link might be missing if its an eventbrite event because you have to register before you can see it.
• Location also missing from spreadsheet event but we could add this.

Event types:

• conference, training, community_call, community_event

Location types:

• online, physical

[glenrobson]

I've put together the following json file showing matching your layout with events from EventBrite, Calendar and a Google Spreadsheet:

https://iiif.io/events.json

It updates every day.

I've also left the different sources of data as separate files in case you only need one type:

• events.json events aggregated and ordered by most recent date.
• calendar.json IIIF Community calls
• eventbrite.json IIIF Eventbrite Events
• community_events.json events submitted by the IIIF community to the newsletter form:

Let me know if this looks OK.

[mnyrop]

(in progress note to self: https://preview.iiif.io/root/news-and-events-redo/get-involved/ also includes an "Upcoming Events" section to consider)

[glenrobson]

Questions from slack:

Questions I have include:

• How does it look?
• Do you still want this to be powered dynamically by Javascript pulling from the live JSON file?
  • Pro: immediate updates
  • Con: harder to maintain code, doesn't include testing so can break site render
  • Alternative: Have GH action run a cron 2x daily to Curl the JSON file, test it, and redeploy the site
    • pro: safer against errors
    • con: computationally a bit wasteful, not immediate display (edited)

[glenrobson]

Regarding the live JSON file. For the different headings on the news and events page:

• Featured IIIF Events - lets take this from the events data file
• Upcoming Community group meetings - I think this should be from the Javascript

On the View all events page:

• All Upcoming Events - lets generate this from Javascript
• Past Featured Events - lets take this from a new data file

I'm meeting with Josh this morning but I'm happy to take on the work above. I can see all of the templates you've provided and I can fit the javascript around what you've done.

[glenrobson]

I think this is done now. The work appears in the following locations:

• Front page: https://beta.iiif.io/ (from events.yml data file)
• News & events page: https://beta.iiif.io/news-and-events/
  • Featured from events.yml file
  • Community calls from calendar.json
  • View all events: https://beta.iiif.io/events/
  • Upcoming events from events.json which is all training and events in community google form / spreadsheet. Note it looks like we already made the decision to not include community calls in the events.json
  • Previous events comes from pastevents.yml in the theme.