Hope College was recently featured as a case study by Localist, the platform that powers our new master web calendar. We were also recently asked by colleagues at another institution why we chose Localist and for more information about how we implemented it. We were happy to share!
Note: this post is a bit more detailed and technical than our usual posts.
Why we chose it
We primarily chose Localist as our front end web calendar platform because it allowed us to have the most control over the general look and feel of our calendar, allowing us to match very closely the look and feel of our new hope.edu site. We also chose it because it had the most user friendly features that promoted interactivity. Some features we really like:
- automatic de-duplicating
- “I’m Going” event check-ins
- comments, reviews, photos
- pending queue
- automatic Google map
- flexible tags
- featured events
- custom fields
- bulk upload events
- responsive design
- CSS override
- exporting to iCal, RSS, Google Calendar
- API access
- Google Analytics
- social media integration
- place pages
Back end, workflow, design
When we initially chose Localist, one of the things we liked was that they would connect to EMS, our room reservation system on campus. When we began the process of making the connection we quickly learned two things:
1) The EMS API is very limited and did not include all of the information we wanted from our events (for example, it didn’t pull the event details/description field).
2) Access to the EMS API was not something that was currently included in our EMS package.
So, we decided to change routes and talented folks in our CIT department developed a feed from EMS that once a day publishes a CSV file with all new events from EMS. The feed includes info such as event name, dates, times, buildings, locations/room, sponsoring department, description, etc. They also added a new question in the room reservation section of EMS, “Display on Public Calendar?” and in order for something to show up in the feed, the submitting user in EMS has to select ‘Yes’ to that question.
Once the feed existed, we added it to the Feeds section in our Localist account, which adds each event into our Pending Queue in Localist. Everyday a member of our team reviews the Pending Queue in Localist to review the events there, clean them up, add photos, tags, descriptions, hashtags, ticket costs, and any other pertinent information before publishing the event live on the web.
Another thing we had to “clean up” before we started was our list of buildings in EMS. We wanted the buildings to match our list of buildings in Localist so when something came through the feed it assigned itself to our Buildings or “Places” in Localist. So there was some work we had to do to clean that data up to match.
We’ve let the campus community know that they are welcome to contact us directly to let us know if they want anything added or changed to their event after the fact (more info, rescheduled date/time, custom photo, etc). Event changes do not get sent to us via EMS feed. However, CIT did create a “cancelled events” feed for us (outside of Localist, it’s an email alert) to let us know anytime an event gets cancelled in Localist. When we’re alerted of those, we check in Localist to see if the event exists and if so we remove it. The EMS to Localist feed is a one way street, so changes or cancellations in EMS have to be handled manually in Localist.
The submit via EMS process works for about 90-95% of our campus events. For our more major or off-campus events (Orientation, Homecoming, regional alumni events, etc) we work with those departments directly (via a sit down meeting or email) to create all of the events to their preference.
You can see how we communicate this to campus by visiting our department website and selecting the Events Calendar section.
We’ve been very pleased with the feedback we’ve heard on the new calendar and look forward to continuing to further develop it in new and exciting ways on our campus.