Request from Caitlin.
There is an API provided by Campuslabs per instance. We can either outsource our data to the api calls or support two way creation.
Pros/Cons
API only event support
Pros
- No authentication
- We are not trying to be an authoritative source on event data
- Always up to date with CL
Cons
- If CL is replaced with something else, the future Web chair will have to change the API code
- Scraping the Event creation on site
- Less reason to make custom features for the event pages
Two-Way Synchronization
Pros
- Very easy for the user to create an event
Cons
- Auditing the events on each pull
- Need to design a mechanism to store CL authentication credentials
- Same replacement issue as the other option
There could also be a case made for allowing users to create events on the IFC site for more targeted engagement. Just because we aren't a data authority on events doesn't mean that we cannot create any data.
Request from Caitlin.
There is an API provided by Campuslabs per instance. We can either outsource our data to the api calls or support two way creation.
Pros/Cons
API only event support
Pros
Cons
Two-Way Synchronization
Pros
Cons
There could also be a case made for allowing users to create events on the IFC site for more targeted engagement. Just because we aren't a data authority on events doesn't mean that we cannot create any data.