Bug Report: inconsistent behavior with downloading table tsv for sets Completed
Hi Terra team,
Clicking the `DOWNLOAD TABLE TSV` button in Terra yields two different results depending on if entities are checked or not.
The first, seemingly correct, scenario is clicking the download button with no entities selected. This downloads a zip file containing two files:
- `(sample, participant, or pair)_set_entity.tsv`, which has the entity name and
- `(sample, participant, or pair)_set_membership.tsv`, which a column with the set name and another column with members for _all_ sets of that entity type.
The second, seemingly incorrect, scenario is checking at least one entity from a set page in the data model and then clicking `DOWNLOAD TABLE TSV`. This results in just a single file called `(sample, participant, or pair)_set.tsv` and contains the name(s) of selected sets in one column and the number of members in the other.
This was definitely working as expected at least a couple weeks ago and this behavior has been confirmed by a few people.
Comments
8 comments
Hi Brendan,
I think I have understood this bug report but I just wanted to make sure! I have downloaded TSV from my sample_set table without selecting any entities:
and the resulting .tsv files look like this:
When I select a single row from my sample_set table:
I see the following .tsv file:
The above is not the expected behavior.
Please confirm if this is what you are experiencing!
Sushma
Hi Sushma,
Exactly! Thank you so much for replicating the behavior, I should have included screenshots.
Great, thanks for confirming. I have made a bug report and will report back to you on this thread once this issue has been fixed!
Thank you!
Hello Brendan,
This issue has been resolved by the team. Please confirm that you are no longer seeing this issue.
Sushma
Hi Sushma,
Thanks for looking into it, it seems that the feature is half working. The output for a selected set now outputs all columns at the set level, along with a column named after the entity type populated by the number of members of that set. This is great and is equivalent to the `{type}_set_entity.tsv` output; however, the other output of set membership is not produced.
Could the team get this feature back to full strength? Thank you so much!
Brendan,
Thanks for catching that - we have moved the ticket back into queue to be updated. Will report back once it has been completed.
Thank you in general and for being so responsive, Sushma!
Please sign in to leave a comment.