Events-adding ease Pt 2 (after initial site work in #973 done)

[amandavisconti]

Follow up on #973 for further needed work:

Jeremy:

• Check if new setup closes Events that start on one day and end on another aren't displayed on /events list after start date #1136 (close that ticket, if so)
• @jeremyboggs?: See if there's a way on /events to show today's+upcoming events at top of page, followed by a section of "recent events" containing past events from this term only (might need two API pulls?) #1175
• @jeremyboggs?: Style /events-archive so that description text from Fall 2024 events and after (ie Spring 2025, Summer 2025, etc) is included, but doesn't clog page (e.g. is there an accessible way to hide it behind uncollapse arrows, so it's on the page and doesn't need new markdown file per past event, but only visible if you click to see it?) #1174

Amanda

• @amandavisconti has scheduled themselves to do a manual copy of LibCal events to /_past-events at the end of spring, summer, and fall terms each year. Only copy: Event title, Speaker/instructor, Event date, Event Time (LM requested!), Event description/body text. (I.e. no location, reg info, images). #1168
• re:doubled categories, once libcal live on site: I can’t see where to set whether something is calendar-specific vs. system wide. When you create an event, it lets you choose either. So I guess instead of editing further events, I can set up a test event just on system-wide-SLab-category and one on just-calendar-specific-Slab-category, and if both are pulled into our feed it doesn’t matter. UPDATE: unneeded as code pulls both into SLab site.
• @amandavisconti look into automating past-term => SLab events archive more (eg CSV export=> display from CSV in folder's data?). See Ammon's setup here #1169
• Update documentation on SLub /events/archiving-events page once this work completed

[jeremyboggs]

Style /events-archive so that description text from Fall 2024 events onward is included, but doesn't clog page (e.g. is there an accessible way to hide it behind uncollapse arrows, so it's on the page and doesn't need new markdown file per past event, but only visible if you click to see it?)

The events archive has a links that go to the past event's page, which includes the description. I'd suggest just keeping that instead of trying to display the text for each event on this page, even in a hidden/collapsible way?

[amandavisconti]

Style /events-archive so that description text from Fall 2024 events onward is included, but doesn't clog page (e.g. is there an accessible way to hide it behind uncollapse arrows, so it's on the page and doesn't need new markdown file per past event, but only visible if you click to see it?)

The events archive has a links that go to the past event's page, which includes the description. I'd suggest just keeping that instead of trying to display the text for each event on this page, even in a hidden/collapsible way?

Let me check with Laura—I think we might be interested in having that descriptive text on our site somewhere, but there are only ways to do that (e.g. biannual post collecting events from past term). We also wanted a Slab-held record in case someone deletes the LibCal past events (e.g. a non-SLab person tidying things), though just exporting and holding that as a CSV in our GDrive covers for that concern.

[amandavisconti]

Record of initial past-term event archiving, first time doing it:

1. Now we're near the end of Spring 2025 term, I exported events from LibCal for 1/1-6/6/2025 as a CSV. Go to LibCal > UVA Public Library Events > Event Explorer; change to "no" "show registration responses" (we do not want to keep a record outside LibCal of that personal data!); search the dates of the full term; click "export data"; upload to Gsheet.
2. I stored a copy in the SLab Drive under Events/Events data archive, Spring 2025-current. One tab is protected from editing and has full export (including registration data); a second tab is just the subset of data we need for the site. (CCing @lam2c so she sees this info!). From the second tab, removed postponed/to be rescheduled events so they don't appear in website archive page list.
3. I updated the past-events page template to pull in Spring 2025 events from an include file (to keep the events.html file clean/wieldy), stored in _includes/_content-includes/_past-events/2025-events as single .md files per term (includes have to go in the includes folder, is why I didn't store these in the collections/events folder; we may be able to create a symlink in the future so people looking for this file in /events directory can find it more easily?)
4. We'll need to update this to iterate over such files, in the future, rather than hard code to include YEAR-events/TERM-events.md for each such file we add
5. Ordered data in reverse chronological order, changed start date column to correct output format, concatenated columns with needed markdown formatting, copy/pasted to md file. Exported data we want to display (event title, link to event registration/details page on LibCal, event date) from CSV to md file, checked displayed and links correctly (yes!).

This all works great. Noting I do get a warning in the command line, Liquid Warning: Liquid syntax error (line 11): Expected end_of_string but found dash in "{{ 2025-events | markdownify }}" in pages/events/events-archive.html That I couldn't sleuth. Changing the 2025-events variable to 2025events just moves the warning to something else ("ID instead of expected end of string").

Note I followed our past display pattern for past events (title linked to event page, date); because the event page is now on LibCal, the descriptive data does not appear on SLab’s website—it won’t bring folks to SLab’s website on a web search, and if removed from LibCal won’t be publicly accessible online (we do have our private Gsheet record of it though). I added a task to consider making a “Spring 2025 events review” blog post that would contain all that event-description data and thus make it part of our site's permanent and searchable content, but not sure if I’ll get to it—someone else is welcome to take it!