Permissions to only allow Logged In users to see some API Documentation (APIGEE-117)
Steven Maglio will contact Denise and see if she can put it back so it's grouped. And ask if she can work with the css to make it easier to read and emphasis the APIs over the groupings.
Need reporting that will display in developer.ucsb.edu
Need annual clean up times
Get operational on GCP
Kevin Wu will determine if this is the platform we want to use and will figure out the annual costs if we. We will use this to put together a flex card request.
Brought up by Ann Crawford with the following questions:
How do we request a use case for an API
What is the work flow? Possible status are : received, rejected (with reason ie duplicate), closed ( with deploy date), in test, in code
How do we search what's in the works?
Who will mange requests?
Specific use case from Ann Crawford:
Here is the API use case that I sent to housing for the photos.
Our use case is to get all new or changed photos for Type graduate or undergraduate with the perm (university ID)
New photos are perms we don't have a photo in the student health database.
Changed photos are those where the saved photo hash <> current photo hash for a given perm. Currently the sproc returns a hash of the photo so we can compare and save, along with a perm (university ID), Type, first name, last name. We don't use the first name or last name but it is good for testing.
Need to use API Key in public code (Javascript). It can get stolen so we need extra lockdown. That should be referrer domain name set upin API App. Or some other complex auth system, but it always needs to include the domain. (This should be Security Workgroup's job )
