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 3 Current »

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

Vacations

Diana  - 
Gary -  -  


Swagger Responses Not ShowingIan Lessing (Unlicensed)



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.

 Denise had to reschedule due to UCTech commitment. Will meet on 5/8.

Denise S. & Ian L. had a working session on 5/14 and have another scheduled for 5/17.  Got setup with development environments utilizing Lando which utilizes Docker underneath.

 Ian and Denise met on Tuesday. Next meeting is next week on the 5th. Setup is similar as the UC Tech site where multiple developers are contributing to the development. 

 Using Lando (Dev with Lando - using Docker to create the same setup as Pantheon) to do local development. Will give others access. Ian and Denise will document it as well.

 Denise S. & Ian L. had working sessions on 7/8, 7/9, and 7/12. Next week they will be at UCTech. APIGEE-216

 Denise S. & Ian L. meet last Friday, , to look at some new information from Apigee. They have documentation on their site showing support for Drupal 8.

The way it reads, they have a template Drupal 8 site with the Apigee modules pre-installed. It is also based around Composer.

But, Steven and Ian are concerned about Composer being more work than we can take on. There is a conversation going on with Denise about this.

 Have not met with Denise during this last week. Started making a matrix comparing the different options.

 No updates


Reports and alertsDiana Antova 
  • christian.montecino (Unlicensed) Google analytics api usage reports - there is an issue with recording API usage. it does not match the gateway data. (APIGEE-189) Christian will start logging into a text file the API execution to compare with google analytics. 

  • Christian asked the Loggly cloud service provider rep to create a report for us to compare with the Google analytics report. 

  • The free account is expiring and Christian requested and extension. 

  • First we will compare Loggly usage to Google analytics. Then we will move the functionality to Splunk. 

  •  The apigee portal reports more requests than what we see in analytics. But, loggly events show a matching number to what apigee is showing. Christian will continue to look into why it isn't recording the information.

Student Developed Applications
  • GoGaucho Team: Hengyu Lui / Jimmy Lin
  • Professors: Chandra Krintz / Tobias Hollerrer
  • GoGaucho Improvements
      • Good news. The iOS application had the username/password form removed from the application and it no longer retrieves students data which has been screen scraped from GOLD.
      • Jimmy (the Android Developer) is going to add a security token to the Heroku endpoint and will be upgrading the Android application to use it before we next meet.
      • Henry (iOS) will update the iOS application to use the secured Heroku endpoint before the end of the summer.
  • Next meeting on  

Photos APIsDiana Antova
  • In progress, Farah Tahmasbi working on the API switch. (APIGEE-141)
    • Potentially deploying  
  • There will be a need to use campus photos in Campus Groups


Accounts for separated employees/student

DocumentationDiana Antova

Housing ServicesDiana Antova

 Graduate Division has put in a API Publishing Request. We've added Melanie Hoven as the Business Approver and she should be able sign-off the request pretty soon. The Graduate Division API is going to need to go through some development iterations before it will be posted.


Employee APIDiana Antova
  • Library looking to get Employee/Staff information so that they can get employee information when a user logs into the ALMA system.
    • Currently, they are getting a dump of employees that they upload into this system. Getting this info in real-time would be a big improvement.
  • Kevin Wu and Adam Sottosanti have been developing this and they are currently testing it through the API Gateway
    • Steven Maglio Will work with Kevin on naming conventions in the creation of the proxy et al.
  • Jeremy Hobbs (from CalPoly) is the replacement for Ana Fiddler, and he will be potentially driving this project from the Library side. Angela Chikowero is probably also driving this too.

 Kevin is continuing to work with Kam Kunimoto/Adam Sottosanti on developing the endpoint. A new endpoint is being asked for; one that returns all the employees/jobs. 


General Data Usage AgreementKevin Wu
  • Sam Horowitz gave Kevin a heads up that in the IT Council that they are having conversation about developing an overall campus Expected Data Usage policy for how we use data between our departments. It's sort of like if we are the provider passing data to a consumer, then the consumer bears some responsibility for safe guarding the data and using it responsibly. If they share that data with another party, then they are responsible for the 3rd party's appropriate usage of the data.

Private Department Courses Extract API RetirementSteven Maglio

The Registrar's Office has completed enough APIs that it's possible to replace the functionality of the private Department Courses Extract API with 

The Registrar's Office is currently working on a Student Gender Pronoun project which will probably affect the private Department Courses Extract API and the Student Basic Student Info API. That project is set to wrap up in mid-September (before students return). Since there will be communication with API customers of the update to the APIs, it might be best to start the conversation about deprecating the private Department Courses Extract API after the completion of the Gender Pronoun project. This would give us 2 months to think about what's the best way to communicate a deprecation.

Action items

  •  
















  • No labels