v3.2.0

There are three major changes in v3.2.0. All are backend only changes (frontend of these features is under development):

Importer, backend & REST API support for both old and new style structural variant data. In the old format one would put fusion's in the mutations table. In the new format there's a specific structural variant table and a separate case list for structural variants. As a deployer for cBioPortal one currently does not have to make any changes to the data files. The old format will continue to be supported. The frontend for the new fusion format is still in development (for more info see RFC31_b).
Importer, backend & REST API support for Generic Assay data. This is for matrix style data where a sample has a value for some "entity". Generic Assays allow one to support all kinds of data, e.g. a drug with a particular response value for a sample, or a mutational signature and the exposure rate in that sample. For more info see RFC51. The current implementation only supports the backend side. There is no generic frontend layer yet. Treatment data has been converted to Generic Assay data and corresponding frontend changes have been made.
Importer, backend & Rest API support for allele specific copy number data, cancer cell fraction estimates as well as additional free text annotation in JSON format. This is to support data from e.g. Facets. See cBioPortal/cbioportal#6540 for more information.

🗄 Database Migration

Add Generic Assay related tables
Convert Treatment Response Data to Generic Assay
Add fusion profiles for studies that have mutations of type FUSION in the mutation table
Add support for allele specific copy number data, cancer cell fraction estimates as well as additional free text annotation in JSON format for mutations (see: cBioPortal/cbioportal#6540).