Open MillenniumFalconMechanic opened 1 year ago
Hi @MillenniumFalconMechanic! Should the new Atlases column be visible by default, or should it be hidden?
Also, since the filters on the mock don't match the current groups present on the dev site, what categoryGroup
should the Atlas
filter fall under?
Should the new Atlases column be visible by default, or should it be hidden?
what
categoryGroup
should theAtlas
filter fall under
Hi @jpaten, thank you for these q's! I have updated the task description above.
Hi @frano-m, can you add what is blocking this on the ticket? Thanks!
termFacets.tissueAtlas
is missing version information:
Version information is however included in hits.projects.tissueAtlas
:
Need
Add an
Atlas
filter andAtlas
column to the project index page.Approach
See mocks:
termFacets.tissueAtlas
in the/projects
response from Azul.hits.projects.tissueAtlas
in theprojects
response from Azul; display as${tissueAtlas.atlas} ${tissueAtlas.version}
.Atlas
andBiological Network
to this group.Altas
(notAtlases
in current branch).${atlas} ${version}
values pulled fromtissueAtlas
.filters={"tissueAtlas":{"is":[{"atlas": "Lung", "version": "v1.0"}]}}
(and not the standardfilters={"tissueAtlas":{"is":["Lung"]}}
). For example, this request.Notes
jonah/3341-hca-dx-filter-by-atlas
branch with corresponding draft PR. (See Slack.)