We store the result of the Entity API's (HuBMAP or SenNet) /data-sankey endpoint response then apply the current filters onto that in memory
We modify the Entity API /data-sankey endpoint to accept a request body that contains filters and just rely on that new response to display the sankey visualization
Related to this card: https://github.com/x-atlas-consortia/data-ingest-board/issues/228
We want to add a button or link to the visualization section that will launch the data sankey (https://docs.sennetconsortium.org/data-sankey/ or https://docs.hubmapconsortium.org/data-sankey/index.html) but the sankey should reflect whatever filters the user currently has selected.
2 potential methods to handle this: