ebi-gene-expression-group / atlas-components Goto Github PK

Currently every filter change triggering REST calls for the other filter components to refresh and populate their values and also triggers to refresh the result list.
We could add a maximum 2 or 3 seconds of waiting time before executing/triggering the REST calls. That would make this component a bit more user-friendly and also it would limit the number of REST calls.

Then we can craft URLs better. See this comment #87 (comment).

Add a new column on the left in the experiment table to label the anndata/non-anndata experiments like baseline/differential in bulk.

Non-anndata experiments will display SC magnifying glass logo in the new column.

Anndata experiments will display a suitable icon, like A, in the new column.

To distinguish the experiment type, two options:

• add experiment type to the payload (backend)
• regex check if the accession is E-ANND- (frontend)

We need to change these two methods:

https://github.com/ebi-gene-expression-group/atlas-components/blob/9301396f596483e45946a16eb9c4cd7dd16e20af/packages/scxa-tsne-plot/src/TSnePlotView.js#L58

https://github.com/ebi-gene-expression-group/atlas-components/blob/9301396f596483e45946a16eb9c4cd7dd16e20af/packages/scxa-tsne-plot/src/TSnePlotView.js#L80

Do not process the URL text outside of URI (e.g.

Add a new column on the left in the search result to label the anndata/non-anndata experiments.

Non-anndata experiments will display SC magnifying glass logo in the new column.

Anndata experiments will display a suitable icon, like A, in the new column.

This story refers to the frontend implementation of the new experiment design logic. We need to change the way React router is populating the experiment page. Currently, all of the payload is delivered in one go but we will need to change that behavior and utilize new endpoints implemented on the backend for experiment design.

The expected behaviour is when a user clicks on the Experiment Design tab, a request is made to backend the experiment design controller and the experiment design table is populated. New controllers return the payload for experiment design in the same format as previously so we might not need to change how the data is parsed in the frontend component but we do need to handle edge cases like maintaining pagination functionality, and finding when the end of file has been reached.

Relevant back end PRs for controller information are scxa, gxa and web-core.