From - "Curriculm APIs feel slow". Our previous conversations around this discovered that the Curriculum APIs was being called regularly in order to have accurate Available Seat information for classes during Scheduling periods. Seth had asked if the GoGaucho Team could reduce the number of calls to the API outside or Pass Times, and during Pass Times to limit the number of calls to 2 times per hour. (Seth also mentioned that he would implement 30-minute caching on the Registrar side, so even if there were many calls, they would not affect the performance of the Registrar systems and instead would receive a cached result.)
@Jimmy - This is mostly used by the web app, there emails are ... (Jimmy will send an email after the meeting with their info)
Diana Antova - Let's add that info into the App Registration / Access Request Form
Steven Maglio / Diana Antova / Seth Northrop - Maybe we could create a separate application for the Web app. Could you ask the Web team to put in a new Access Request form?
@Jimmy - Yeap
@Shiheng - We are currently doing regular scanning of all the classes to update the backend databases. For the most part, we don't need to update all the classes, just updates for the availability/space counts.
Seth Northrop - That's a ticket, but it is competing against other priorities. It's really hard to prioritize against the immediate needs (COVID-19 is also having a impact). There was also more pressure to get this in place due to performance issues that were happening on the system. With some recent reconfigurations/updates those performance issues have reduced, so the pressure is reduced.
@Shiheng - We use the Curriculum Search API to do these calls. And, there is something like 2000 courses, so the calls will last about an hour (Seth - maybe 25 minutes) to go through them all.
@Shiheng - We are moving the database to DigitalOcean, so the IP addresses that the calls are coming from may be changing.
Who are going to be the leads of the project after graduation this year?
Henry's gonna be leaving
Shiheng - I'm currently doing the backend, and the web was introduced through me.
Seth - Maybe we can get an email with the decision.
@Jimmy - Yeap
Do you have any needs on your mind?
@Jimmy - Not Right Now
@Shiheng - About the Curriculum API - Sometimes the data has nulls, sometimes it has spaces, so it can feel inconsistent. The documentation on developer.ucsb.edu can be confusing.
Example - Course ID - The description says 13 characters, but it's not always 13 characters (Steven Maglio - Right Trim).
@Shiheng - Student Privacy - Is it okay for students to record Student Schedule data.
Seth Northrop - No, the data should only be accessible to the student who owns the data. The way the agreement works right now is that GoGaucho acts as an intermediary to provide the data to the student who owns it.
@Shiheng - OAuth - Student currently logs in through Google OAuth; is there an idea of when that might turn over to a UCSB provided service?
Steven Maglio - We don't have a concrete plan for when that transition/capability will be complete/available. The Identity Teams are trying to figure out there roadmap right now.
@Jimmy - Mobile app hasn't had too much work on it recently.
UCSB Improvements & Timeline
UCSB Team GoGaucho Team
From - "Curriculum APIs feel slow".
Does the Registrar's Curriculum endpoint have the 30-minute caching in place?
Seth Northrop - No. We push caching on the Lookups. I can talk to Anthony about implementing this. It should be fine.
There were plans to implement another endpoint specifically for this need. (the Availability Count for a Class) Hows that going?
Seth Northrop - That's a ticket, but it is competing against other priorities. It's really hard to prioritize against the immediate needs (COVID-19 is also having a impact). There was also more pressure to get this in place due to performance issues that were happening on the system. With some recent reconfigurations/updates those performance issues have reduced, so the pressure is reduced.
Curriculum performance has come up in other venues, are there any other changes being planned for?
Seth Northrop - The Curriculum blocking issue is getting close to being resolved, due to implementations of the caching and endpoint from above.
