Page Comparison

IRR

• unclear scope for phase 2 and 3

• program review - how many dashboards? Who from IR can Galina work with?

• historically, BIA has gone after the data sources

  • investigate which ones are mapped to Program Review

• highest priorities these next 2 weeks: CLSD and Census

• Aymme has extracts that should cover majority of what IR needs

  • Jira Legacy
    server ITS PRO serverId ebe8394f-6d75-344c-8d9c-717cb778a1eb key SAHR-2355

  • this could be a template that IR can follow

  • Sama needs to conduct gap analysis after validation

• RACI

  • expectations from IR

  • Validations

• when BIA releases new field for IR, expectation is IR will test during the UAT period

  • Not just Galina, original requestor too

  • what are role expectations

  • present options (i.e. if only Galina test, then accept risk)

•  Mindy dig into program review docs and update OTL (add bug fix time, add reports for phase 3 into OTL)
•  Mindy rescope IRR for SLCM ; what add’l resources are needed if want all reports to be sourced from SAH
•  Mindy create doc - clear roles and responsibilities

Jira in RAH project

• project charter

  • PR records already have the fields from charter

  • some groups still use charter doc with their business teams

  • in future, fill out PR record even if there’s unknowns

• annual planning

  • what’s ADIS' bandwidth?

• impact to existing projects

  • IR?

  • unknown what integrations are needed

  • cost analysis?

  • 1 time cost for new project vs recurring costs

  • OCGA set up connector from Tableau to Jira

    • keeps breaking

    • blocks upgrade to Tableau (compliance issue)

    • should reside in RAH

  • IRB would be delayed

• pause enhancements for next 3 yrs?

  • lose funding for Andy

  • learning curve

• challenge

  • lack of BI workers (FACE team)

  • lack of bsa

• half of Sama is funded by external projects

•  Does Bill’s team have resource availability - Mindy
•  Mindy reply to OCGA on next steps (dependent on Concur, COI and C2 completing), IRB will be deprioritized

https://support.ucsd.edu/sn_customerservice_case.do?sysparm_tiny=1YCqZIIgZBUQCaOl9deV8fdkXWw9GfyI&sys_id=3d46e2f81b677c50b8d255b5604bcb50&sysparm_record_row=8

Legacy DW and SAH Sources

/wiki/spaces/SAHRS/pages/816644103

SAH

• ISIS

• Canvas

• ApplyUC

• ProSAM

• VAC

• Hops (db, not a source system)

• Slate Grad

• STLNK (db, not a source system)

• STUDENT_DB (db, not a source system)

• OGS (db, not a source system)

• HDH

• Kaltura

• EVC-SQL-SERVER (db, not a source system)

• Transact

• Accounts Receivable

• AEPNexus (in progress)

• Oasismatrix (in progress)

Legacy DW

• AR

• ISIS

• ProSAM

• ApplyUC

•  Mindy follow-up with Jen Hernandez if Greg Boyer can help us with legacy list

Kevin’s syncing with Invenio to create SOW

• tight timeline

• coordinating deployment with Bars team (UCSD, Merced, UW, and ASU)

• 4 Beta views is out in Cognos for testing

• need Cindy/Silvia approval on data groupings so can progress with SNOW form

• loading SIS tables

• UW is devising authentication plan on their jumphost

• config meeting w/Kenny scheduled to walk through config file, materialization process

• get to green

• CLSD is highest priority

• Galina is validating Instructor assignment bug fix

• Galina will push custom data source early next week so Olga can continue report rebuild

• Project close after occuspace view is released to prod in June

• waiting for Jennifer’s team to finish UAT (planning to finish in June)

• project close end of June

• DDC meetings have started

• meeting scheduled with Angela to discuss charter questions

backlog