cBioPortal
Govern the four comment rows that are the schema of your study.
Quickstart · Get it working.
Zero to first audit: putting a cBioPortal study's clinical schema under governance
The clinical schema of a cBioPortal study does not live in a database, a catalog, or an API. It lives in the first five lines of two tab-separated text files that a curator maintains by hand. Those five lines decide whether an attribute passes portal validation, what it is called in the UI, whether it is a number or a string, and how prominently it is displayed. They are also, in most study repositories, the least reviewed lines in the project.
API · Drive it from the Integration API.
Every cBioPortal route, every role: the CoreModels HTTP surface for study governance
Ask the API what it can do for cBioPortal before you write a line of client code:
MCP · Drive it from an agent.
Handing a cBioPortal study to an agent: governance over MCP
"Check whether the study files on this branch still match what we govern, and tell me what changed."
Automation · Put it in CI.
One character, one broken study: automating cBioPortal drift checks in CI
Here is a pull request diff from a study repository:
Deep dive · Understand what it does.
Following one clinical attribute all the way into the graph
Take a single column out of a cBioPortal patient staging file:
Why this matters
The case for cBioPortal — the problem it fixes and what changes when it is fixed — is on coremodels.io.
Read the cBioPortal guides →