CoreModelsGuides
cBioPortal
Govern the four comment rows that are the schema of your study.
- Zero to first audit: putting a cBioPortal study's clinical schema under governanceQuickstart · 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.
- Every cBioPortal route, every role: the CoreModels HTTP surface for study governanceAPI · Ask the API what it can do for cBioPortal before you write a line of client code:
- Handing a cBioPortal study to an agent: governance over MCPMCP · "Check whether the study files on this branch still match what we govern, and tell me what changed."
- One character, one broken study: automating cBioPortal drift checks in CIAutomation · Here is a pull request diff from a study repository:
- Following one clinical attribute all the way into the graphDeep dive · Take a single column out of a cBioPortal patient staging file:
Start building
14-day free trial. Builder $49/mo after the trial. Cancel any time.