What’s Happening with API's and the Enterprise Data Warehouse?

April 16, 2018

Current State Background

The Enterprise Data Warehouse (EDW) provides timely, user-friendly, and accurate data for UC Berkeley’s data analysis and reporting needs.  Analytic tools such as CalAnswers are one of the primary EDW consumers on Campus to benefit from the EDW analysis and reporting functions.  Currently, many operational systems on Campus such as Cal 1 Card also interact with the EDW to extract data.  While the EDW provides operational systems access, this function deviates from the EDW core goals – to serve as an analytical data store vs. an operational data store.

Future State Opportunity

As a step towards providing the EDW team a path back to its core reporting and analytic function, operational applications need to consider alternative methods to obtain employee demographic and job data. 

Looking ahead to UCPath, applications that connect to the Enterprise Data Warehouse (EDW) should consider using the Employee API(link is external)(link is external) as an alternative to the EDW as a source for HR data.

  • Once UCPath is operational, data concerning employment, jobs and positions will only be available to UC Berkeley via the DDODS (Data Dissemination Data Store).
  • The data in the EDW sourced from UCB On-Premise HCM system will become obsolete over time and only be used as read only access to archived data.
  • The UCB HCM datasource to EDW is slated for decommission once UCPath is implemented on Campus.
  • API based integrations will continue to replace much of the file exchange and database views currently used on Campus. 

API Central Evolution

With the introduction of API Central(link is external)(link is external) and the Integration Hub (iHUB) as a resource for system integration needs using service oriented API technology, the Employee API has provided a viable solution for operational data access as an alternative to the EDW.

The Employee API on UC Berkeley’s API Central is evolving with UCPath.  Campus developers can leverage the next generation of the existing Employee API to obtain employee demographic and job data from a reliable and secure environment.

The EIS (Enterprise Integration Services) team is currently engaged with various partners to gather requirements for the next revision of the Employee API.  For example, the EDW team is partnering with the EIS team to develop a long term plan to transition targeted application accounts to using API-based solutions. Stay tuned to the UCPath Tech Talk page for more details on when and how to consume HR data and implement the Employee API.  An opportunity to work with the EIS team to shape and provide feedback on the Employee API is coming soon.