This page provides insight into the process of how TSS data gets into SAH. To support system performance, data is not pulled directly from source system tables. Instead, intermediary views are used to reduce load and ensure both the source system and receiving systems operate efficiently.

This approach is used by Activity Hubs when gathering data from Oracle and now for TSS. While it introduces an additional layer that requires quality assurance prior to release, it supports improved performance and scalability in the long term.

Open

Step 1: Load ISIS data into TSS

The TSS team loads ISIS data into TSS using data integration tools and custom scripts. Scripts are code written to move large amounts of data from one server to another based on a set of rules included in the code.

Step 2: Create TSS Views

TSS intermediary views are created on the TSS server in order to organize data in an easy to move manner and isolate the production server from any impact data integration may have. UCSD has hired a vendor to support this effort so that UCSD subject matter experts can focus on TSS.

Pros: View prevent TSS production from being negatively impacted by data integration queries. Views simplify data movement out of TSS as they are topic specific and allow data integration developers to focus only on the topics they need, instead of searching all of TSS. Views provide the minimum about of data, keeping the data sets smaller and as manageable as possible.

Cons: It takes time to create views. It takes time to put the views through extensive QA in order to ensure they are mapping the correct data from TSS production into the View. Any code changes between TSS QA and TSS Prod often require a view code change.

Step 3: Load TSS data into SAH Activity Table

BIA pulls data from the TSS views into our drop location, the SAH Activities Table.

Step 4: Route data through SAH Views

BIA spent the last 12+ months preparing SAH to be able to ingest new data into the existing SAH structure. Custom code was made more flexible and more efficient. This is the where the most complex and time-consuming efforts are made.

Step 5: Make TSS data available in Cognos, Tableau and Column Groups

Any new fields added to SAH FCVs are also required to be added to Cognos, Tableau and/or Column Groups. The BIA team has monthly process they follow in order to ensure Cognos and Tableau match.