Page Comparison

Developer Portal Account Approval

• Verify a valid ucsb affiliation.
• Verify student or employee affiliation.
• Approve/deny account.
• Add to google groups.

https://developer.ucsb.edu/docs/approving-accounts

https://developer.ucsb.edu/docs/accounts/developer-portal

API Access Requests

• Review API access requests
• Request access approval form submission.
• Review provided information on access request form is sufficient.
• Route requests through the workflow.
• Meet with the developer to understand the need and the best way to serve their need.
• Review technical information on API access requests, including security information.
• Approve API access request form.
• Approve API access request in gateway. 

https://developer.ucsb.edu/docs/applications/application-approval-request

https://developer.ucsb.edu/docs/gateway-admin/processing-api-access-request

• Review API publishing requests.
• Route request through the workflow.
• Review that API meets the development standards.
• Publish the API in the gateway.
• Create API documentation in developer portal to make it available for access requests.

• Provide guidance on LDAP account creation
• API use guidelines for developers
• Security guidelines

https://developer.ucsb.edu/docs/accounts/ldap-accounts

https://developer.ucsb.edu/getting-started

https://developer.ucsb.edu/creating-your-first-app

https://developer.ucsb.edu/trying-out-apis

https://developer.ucsb.edu/docs/applications/testing-applications

https://developer.ucsb.edu/docs/security/overview

https://developer.ucsb.edu/docs/security/application-security-review

Student Development Support

• Provide guidelines to students on application development.
• Review security implementation for apps using APIs that require approval.
• Perform periodic code review for apps using APIs that require approval.

• Review API access requests.
• Approve/deny API access requests.
• Review API Publishing Requests.
• Approve/deny API publishing requests.

https://developer.ucsb.edu/business-api-access-request-approver

Each API Publishing Request form contains the name(s) of people that are allowed to approve the publishing of an API and access requests.

• Receive requests from customers for new APIs.
• Determine system of source.
• Work with developers to request the APIs.
• Provide guidance on API development.

• Use the Drupal platform to maintain the developer portal.
• Add/edit pages.
• Create workflows and rules.
• Setup automatic emails.

• Apply Drupal patches.
• Apply Apigee patches.

• Make sure all publishing requests have been filled and are in the correct workflow state
• Make sure all access requests have been filled and are in the correct workflow state

• Create new slack commands for gateway operations  automation.

• Uptime Robot integration.

• API event tracking in Splunk.
• Splunk reports and dashboards.

• Support for historical application inactivity database.
• User account cleanup.

• Provide development support for all SIS&T APIs published in Apigee. 
• Fix bugs.
• Modify APIs as requested by users.

Each API has a corresponding API Publishing request, where the developer(s) and approver(s) are listed.

https://developer.ucsb.edu/api-publishing-requests

• Provide development support for all ARIT APIs published in Apigee. 
• Fix bugs.
• Modify APIs as requested by users.

Each API has a corresponding API Publishing request, where the developer(s) and approver(s) are listed.

https://developer.ucsb.edu/api-publishing-requests

• Provide development support for all ETS APIs published in Apigee. 
• Fix bugs.
• Modify APIs as requested by users.

Each API has a corresponding API Publishing request, where the developer(s) and approver(s) are listed.

https://developer.ucsb.edu/api-publishing-requests

• Schedule weekly meetings
• Prepare agendas
• Issue and sprint tracking 
• Project planning

The team meets 3 times a month for 1.5 hours each meeting. 

Additional time is spent on project work outside of meetings as necessary.