Closed austenem closed 4 weeks ago
@austenem Would it be possible to use the assay_display_name instead of "External Process"? Acknowledging that is not what's specified in the ticket, displaying the analysis performed would be more consistent with what's shown for other dataset types.
@austenem Would it be possible to use the assay_display_name instead of "External Process"? Acknowledging that is not what's specified in the ticket, displaying the analysis performed would be more consistent with what's shown for other dataset types.
That makes sense and seems like a useful addition. There isn't an assay_display_name
present in the soft assay response, but there are dataset-type
and description
fields that both contain the relevant label for this EPIC. I chose to use the dataset-type
because it appears unique to the EPIC processing type.
The description
is the same as assay_display_name
.
Summary
Displays EPIC datasets as being generated via external processing in dataset relationship diagrams. Previously, segmentation mask datasets were being shown as being generated via "Image Pyramid" processing due to their
vitessce-hints
.Design Documentation/Original Tickets
CAT-964 Jira ticket
Testing
Verified using a segmentation mask EPIC on dev: https://portal.dev.hubmapconsortium.org/browse/dataset/22901da5f080b219a514e38381acbb0e
Screenshots/Video
Dev:
Local:
Checklist
CHANGELOG-your-feature-name-here.md
is present in the root directory, describing the change(s) in full sentences.