2018-12-06 Student Application Development Support

• Greetings

• Slides: GoGaucho Presentation

• Current functionality

  • Dining Menus

  • Class Schedule

  • Campus Maps

• On the roadmap

  • Registration Information (pass time reminders)

  • Campus Events

  • Real-time Buss Map

• Security Implementation

  • Login screen to get the student ucsbnetid and password

  • Login to GOLD with the student credentials

  • Screen scrape the class schedule screen and present it to the student in a mobile app

• Technologies used

  • iOS and Android apps

  • Heroku for server-side development

• Other
  • The students have registered a student organization with about 20 people - iOS developers, Android developers, back-end developers, marketing person, and project managers.
  • They have a professor sponsor their app development - Tobias Hollerer -Professor of Computer Science Department holl@cs.ucsb.edu 

UCSB AppDev team support for GoGaucho

• What we can offer?

  • Oversight of the technologies and security of the apps

    • We have been in communication with the students, reviewed their implementation and identified several security improvements

    • Will begin regular meetings with the students after Dec 11.

  • Provide APIs and better security implementation

    • We can provide the necessary data and security mechanisms to remove the need for screen scraping 

    • Google oAuth for authenticating the student which will be transitioned to the campus oAuth when it becomes available

    • The Student basic API was released today to allow them to get the perm from the ucsbnetid

    • Class schedule API is on the roadmap to replace the need for screen scraping the student schedule

    • Provide other APIs as needed - dining menus, events, etc. The dining menus API already exists and we are in conversations with Public Affairs and Associated Students to provide an events API.

  • Be the conduit between UCSB and the students.

• Use of campus branding
  • Is the name GoGaucho OK with UCSB policy?
• Use of student data
  • Can we leave the screen scraping on for now until we can provide a better option?
  • Students will be testing the Google oAuth in December. 
  • Class Schedule API will be released in January.
• Legal documents to sign  
  • Data security agreement?
  • What protections the Student Code of Conduct give us?
• Who takes responsibility if there is a data breach?
  • With the screen scraping
  • With the UCSB APIs
• Can we create a badge that the app is approved by UCSB?
• Can we add language to the app to let students know that this is not an official UCSB app?
• How do we support the next student development team that comes up with a similar app?