You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Status 2026-07-10: All code merged (#1594, #1596, #1602) and live on staging (staging-on). Prod is untouched (prod-off). This is a GAP row in the feature-flag inventory — staging-on with no owning rollout issue. This issue owns the prod flip.
What it gates
AVAILABLE_TECHNOLOGIES_SECTION gates the "Available technologies" section on the public scholar profile: a compact row (sitting under Funding and Clinical trials) listing licensable inventions from the WCM Center for Technology Licensing (CTL) public portfolio, attributed to each scholar by the CWID in the VIVO inventor link CTL prints beside each PI. Each row shows CTL's reference/docket number, the title, a link to the public technology detail page, patent status, and — scoped to CTL's own publications pane — the related PubMed papers.
It is presence-gated and fails safe: with the flag off the profile payload returns an empty technologies list regardless of table contents, so the ETL seed can land in prod before the flag flips without exposing anything. The section also hides for any scholar with no technologies.
Current per-env state
Wired per-env in the CDK app stack: staging = on, prod = off. Single app-container copy (no ETL-stack copy).
Prod: flag off, table not yet populated, weekly ETL schedule not yet deployed.
Before the prod flip
CTL attribution / contact sign-off — the exit criterion in the inventory and the real blocker. CTL must confirm the inventor attributions, and there is an open data-quality ask back to them: ~60 of ~279 portfolio pages carry no VIVO inventor link (some are current faculty). CTL should add links for inventors still here and repoint every VIVO inventor link at Scholars once VIVO retires. The VIVO href is the attribution key — PMIDs are never used to attribute (CTL's linked papers average ~3.2 co-authors, so a PMID would credit every co-author with the invention).
Deploy the prod ETL stack so the weekly technologies refresh is scheduled.
Populate the prod table — run the technologies ETL once as a one-off task, or wait for the first weekly run.
Flip the flag to on for prod in the CDK app stack, then deploy the prod App stack. A prod App deploy releases everything accumulated on master, not just this flag (23 commits as of 2026-07-10), so run the pre-deploy drift report and cdk diff and review it first.
AVAILABLE_TECHNOLOGIES_SECTION = on in both envs, verified in the deployed prod app configuration.
Inventory GAP row updated to point at this issue / marked converged.
Verification after the flip
Load a prod scholar profile known to hold CTL technologies and confirm the "Available technologies" row renders with the correct titles, CTL detail links, patent status, and (in the publications pane) PubMed links — attributed to the right scholar via the VIVO link, not by PMID.
Confirm a scholar with no technologies shows no section (presence-gating holds).
Confirm the row sits under Funding and Clinical trials as a compact row, not cards.
What it gates
AVAILABLE_TECHNOLOGIES_SECTIONgates the "Available technologies" section on the public scholar profile: a compact row (sitting under Funding and Clinical trials) listing licensable inventions from the WCM Center for Technology Licensing (CTL) public portfolio, attributed to each scholar by the CWID in the VIVO inventor link CTL prints beside each PI. Each row shows CTL's reference/docket number, the title, a link to the public technology detail page, patent status, and — scoped to CTL's own publications pane — the related PubMed papers.It is presence-gated and fails safe: with the flag off the profile payload returns an empty technologies list regardless of table contents, so the ETL seed can land in prod before the flag flips without exposing anything. The section also hides for any scholar with no technologies.
Current per-env state
Before the prod flip
onfor prod in the CDK app stack, then deploy the prod App stack. A prod App deploy releases everything accumulated on master, not just this flag (23 commits as of 2026-07-10), so run the pre-deploy drift report andcdk diffand review it first.Exit criteria
AVAILABLE_TECHNOLOGIES_SECTION= on in both envs, verified in the deployed prod app configuration.Verification after the flip
Refs #1594, #1596, #1602, #1440 (GAP-flag owning issue), #475 (prod App deploy ships accumulated drift).