feat(b2b_analytics): expose sso_organization_id on the mv_b2b_* views

[blarghmatey]

Why

ol-analytics-api is moving to key organizations on the Keycloak org UUID (sso_organization_id) — the one identifier stable across the JWT, MITx Online, and StarRocks (see mitodl/ol-analytics-api#13 and the identifier analysis on mitodl/hq#11845). The b2b_analytics MVs only carried organization_key (the mitx org_key, e.g. MIT504), so the API's WHERE sso_organization_id = %s filter had nothing to match.

What

Add sso_organization_id (from dim_organization) to all six mv_b2b_* views:

• Four already join dim_organization (org.…) — one select + group by column each: mv_b2b_contract_utilization, mv_b2b_enrollment_completion_funnel, mv_b2b_program_funnel, mv_b2b_mit_admin_contract_health.
• Two read the raw organization_administration_report with no org join, so they gain a LEFT JOIN dim_organization ON organization_key AND platform='mitxonline' (columns qualified with oar. per convention): mv_b2b_monthly_engagement_trend, mv_b2b_content_engagement_depth. sso_organization_id is null for free-text organization_keys that don't resolve to a known org — expected, since those orgs have no Keycloak identity and aren't reachable via the UUID path.

distributed_by stays organization_key (proven layout; redistributing to sso_organization_id is a separate optimization). New column documented in _b2b_analytics__models.yml.

Deploy note

Definition change, so the async MVs are recreated + re-refreshed by the Dagster refresh_starrocks_analytics_mvs asset. Data-side half of the org-UUID work; ol-analytics-api #13 and the mitxonline manager-endpoint filter are the other two pieces.

Validation

• sqlfluff lint + fix clean on all six models.
• dbt parse (starrocks target) clean; all six mv_b2b_* manifest nodes carry sso_organization_id.

🤖 Generated with Claude Code

[github-actions]

🔎 ol-dbt impact — column-level blast radius

0 breaking, 0 warning, 6 info across 6 changed model(s).

Details

• ℹ️ mv_b2b_content_engagement_depth — sso_organization_id → 0 downstream model(s)
• ℹ️ mv_b2b_contract_utilization — sso_organization_id → 0 downstream model(s)
• ℹ️ mv_b2b_enrollment_completion_funnel — sso_organization_id → 0 downstream model(s)
• ℹ️ mv_b2b_mit_admin_contract_health — sso_organization_id → 0 downstream model(s)
• ℹ️ mv_b2b_monthly_engagement_trend — sso_organization_id → 0 downstream model(s)
• ℹ️ mv_b2b_program_funnel — sso_organization_id → 0 downstream model(s)

_{Posted by ol-dbt impact (annotate-only — does not block merge).}

[Copilot]

Pull request overview

Expose sso_organization_id (Keycloak org UUID) on the b2b_analytics StarRocks materialized views so ol-analytics-api can key/filters organizations using a stable identifier across JWT, MITx Online, and StarRocks.

Changes:

• Added sso_organization_id to the SELECT + GROUP BY of four existing mv_b2b_* views that already join dim_organization.
• Added a LEFT JOIN dim_organization (mitxonline-only) to two organization_administration_report-based views to expose sso_organization_id where resolvable.
• Documented the new column in src/ol_dbt/models/b2b_analytics/_b2b_analytics__models.yml.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/ol_dbt/models/b2b_analytics/mv_b2b_program_funnel.sql	Adds sso_organization_id to program funnel MV output and grouping.
src/ol_dbt/models/b2b_analytics/mv_b2b_monthly_engagement_trend.sql	Adds dim_organization join to expose sso_organization_id for monthly engagement rollups.
src/ol_dbt/models/b2b_analytics/mv_b2b_mit_admin_contract_health.sql	Adds sso_organization_id to MIT admin contract health MV output and grouping.
src/ol_dbt/models/b2b_analytics/mv_b2b_enrollment_completion_funnel.sql	Adds sso_organization_id to enrollment/completion funnel MV output and grouping.
src/ol_dbt/models/b2b_analytics/mv_b2b_contract_utilization.sql	Adds sso_organization_id to contract utilization MV output and grouping.
src/ol_dbt/models/b2b_analytics/mv_b2b_content_engagement_depth.sql	Adds dim_organization join to expose sso_organization_id for course_run engagement depth rollups.
src/ol_dbt/models/b2b_analytics/_b2b_analytics__models.yml	Documents sso_organization_id on all six MVs.

Comments suppressed due to low confidence (1)

src/ol_dbt/models/b2b_analytics/_b2b_analytics__models.yml:101

• The description states this MV is filtered to a confirmed (non-fallback) organization_key, but the SQL only filters organization_key is not null. Because reporting.organization_administration_report populates organization_key via coalesce(..., org_field.organization), fallback/free-text org keys can be present and will result in null sso_organization_id. Update the description to match the actual behavior.

  - name: sso_organization_id
    description: >
      Keycloak organization UUID (dim_organization.sso_organization_id) -- the
      identifier the ol-analytics-api filters organizations on. Null for
      organization_keys that don't resolve to a mitxonline org.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.