: 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.
: 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
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.
: 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).