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 4 Next »

Date

Attendees

Goals

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

Discussion items

TimeItemWhoNotes
Welcome
  • Greetings and salutations

General Info
  • Vince Nievares
    • Will be on vacation  -  (Phillipines)
  • UC Path
    • August and September is going to have UC Path as the priority



Action Items From Previous MeetingSteven Maglio



API Access Expected UsageFormer user (Deleted)
  • Expected Usage Text and Legal-ize (Terms of Service)
  • What do we do with separated employees
  • Use Scheduled Task to send Email asking for more information on new Access Requests
    • Need to include asking for Form to be filled out
    • Need to include list of API Products being asked for
    • Should include a line asking if a face to face meeting would be better

UC PathDiana Antova
  • Determine APIs that will be affected by UC Path System outages
    • Employees - Employee Map
    • Academics - Quarter Calendar
    • Students - Lookups
    • Students - Registrations
    • Students - Academic Programs (Major/ Minor)
    • Students - Students
  • Determine how to notify customers when outages occur
    • Use the system to lookup information on apps and developers that use the above programs
    • Will send a generic email to all developers of the system. The email should highlight which APIs will be impacted.

API Proxy StandardsSteven Maglio
  • Drop Minor Versions as a requirement
  • Write standard approach for departments that want to use Minor versions; using the approach is also optional.

API Roadmap
  • Added API Roadmap section to the Campus Web API Roamap.
    • Add your APIs!
    • FAQ/developer.ucsb.edu has been updated with a link to the Confluence space

Developer Portal Front Page Updates
  • In About Section
    • Diana Antova - Add page about winning the Sautter Award
    • Diana Antova - If Diana thinks its a good idea to add it to the main page, then she will work with Denise to do so
  • On front page
    • Ian Lessing (Unlicensed) - Will figure out how to add a message warning that there will be an outage of many APIs during the UC Path go line (9/16-9/17)

Portal - API Docs only Visible to Registered UsersIan Lessing (Unlicensed)
  • 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.



Workflow - Publish a New API

Ian Lessing (Unlicensed)

  • Dev Portal Documentation - How To Use Workflow (APIGEE-119)



@apibot - Powershell Conversion & HostingKevin Wu
  • Working on Kevin's Computer (node 8.9.X) (APIGEE-105 & APIGEE-101)
  • Apigee Authorization Module (AuthApigee)
  • Replacement Functionality Progress Update
    • apps 
      • apps (no|approved|revoked|pending|all)
      • apps (approve|revoke) email developerApp
      • apps (approve|revoke) email developerApp apiProduct
      • apps search
      • apps users?
    • devs
      • devs created <days=1>
    • targetserver
    • companies
      • Kevin Wu will implement?
      • Need to build requirements
      • Need to build use cases
      • Need reporting that will display in developer.ucsb.edu
      • Need annual clean up times
  • Get operational on GCP
    • Kevin Wu has determined that GCP is not the right platform for the bot because of the difficulty in setting it up.
    • Kevin Wu tried out Heroku and found it really easy to work with. He wants to know if we can use this?
      • Kevin Wu will write-up a request form and submit it to Matt Hall/Elise Meyer.



Access Request WorkflowDiana Antova



Portal - Apigee Companies Add-OnIan Lessing (Unlicensed)Steven Maglio



New API Request Workflow in PortalDiana Antova
  • 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.
11:00 AM - 11:30 AMAPI VersioningSteven Maglio



API Keys in Public CodeFormer user (Deleted)
  • 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 )

Pantheon Training Follow-Up

 

Steven Maglio
  •  1 - 5 pm - Pantheon Overview, Terminus Overview and Demo, Performance & Going Live
  •  1 - 5 pm - Custom Upstream Development
  • What did people learn?

DocumentationFormer user (Deleted)
  • Docs on Portal site need some updates and fine tuning. I can work on those and edit them with a "technical writing" style. 
  • Data Access Requests should be done thru docusign, and we should standardize it for all UCSB depts.

Companies / Teams Feature

Action items

  •  



  • No labels