Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Date

 

Attendees

Goals

  • Updates on continuing development
  • Review, organize and add to work items


Focus points for this meeting

General update

Discussion items

TimeItemWhoNotes
Welcome
  • Greetings and salutations

General Info


Vacations

Vince -  -  
Diana  - 
Steven -  -  
Gary -  -  


Workflow - API Access RequestDiana Antova
  • WOW!! Soo many are getting processed! It's amazing!
  • Started Processing an API Access Request documentation targeting API Gateway Admins as the audience
  • (question): The API Access Request form asks for the Application Name, which is generally filled out as a normal human readable name. However this name is usually different than the actual 'application name' that is registered in the API Gateway (for example. Request "CS48 Project" is for Application "cs48test"). Do we want to setup a multiline input box that will ask for the exact name of all applications that are associated with the request? Sometimes requests will need to be split up into multiple apps (for cams).
    • We will add a field in the Admins Only section in the API Access Request form for the Gateway App Name. We will continue to ask developers to submit a new API Access request from for each gateway app to make reporting easier.
  • (question): A number of Student Affairs APIs (API Products) have an "Originating System" of 'SIS'. Do we want to change that name to 'Registrar'? Currently, the API Requests are by the data owner. And, potentially other data owners that are a part of the SIS (Admissions, FinAid) may also add APIs to the Gateway. Do we want to change the name current usage of SIS to be 'Register' (or whatever is the owning department) within our API Product definitions?
    • Steven and Diana to discuss the naming conventions for SIS applications

Developer Portal Migration to Drupal 8Ian Lessing (Unlicensed)

Motes: Drupal 8 Migration Notes

 Ian and Denise meeting on 4/30 to continue to work on the migration. In the last session they separated the site from the UCSB managed upstream. Will continue to update it thru composer.


HerokuKevin Wu

Reports and alertsDiana Antova 
  • Account usage reports in Gateway Diana Antova (APIGEE-210)
  • Error alerts in the Gateway (APIGEE-191)
  • Should we discuss opening our Google Analytics reports to a larger audience?
    • Maybe joining the UCSB organization
    • Is Google Data Studio interesting?

Student Developed Applications
  • GoGaucho Team: Hengyu Lui / Jimmy Lin
  • Professors: Chandra Krintz / Tobias Hollerrer

Workflow - Publish a New APIDiana Antova

Accounts for separated employees/student

DocumentationDiana Antova

Action items

  •  
















  • No labels