Donor entity: Available Files card

[rosibaj]

Goal

To build the available files card that will provide easy access to different types of files for this donor.

Data source: a new donor centric index

Blocked until we have a donor centric index.

Zeplin: https://zpl.io/2937nPY

Expected outcomes

• [ ] 1. All Data Categories are listed in the first column (includes DNA and RNA data categories but we will likely just have DNA for now)
• [ ] 2. The experimental strategies are the available columns: for DNA: WGS and WXS and for RNA: RNA-seq So clicking on the first 5for Sequencing Reads + WGS would link to the file repo, applying those two filters in the, along with the donor ID
• [ ] 3. Totals at the bottom in case a user wants to access all files of a specific exp strategy type (links to file repository with the appropriate filters)
• [ ] 4. Move the manifest button to the top titlebar as shown in mockup and change label to "File Manifest". Use the same style as the "Clinical Data" download button. This should download the manifest of all files for this donor (as it would from the file repo)
• [ ] 5. View all links to the file repository listing all the files for this donor, so the file repo filtered on this donor ID.
• [ ] 6. moved to https://github.com/icgc-argo/platform-ui/issues/2244

[akachru-github]

Clinical API should be updated with the logic to provide a value like "NA". Business logic should not be added to the FE to interpret a return like "NULL" for example. @joneubank , @mistryrn , @demariadaniel to connect on this to agree how this will work.

[akachru-github]

As first step:

• Read what we get and render in the table.
• To complete this, identify mandatory fields that will be displayed regardless of data. @edsu7 can help with identifying these.

[Buwujiu]

Question for @edsu7 @lindaxiang : The mockup shows less Data Category than what's on argo qa right now: Do we want to have all the data categories on the file cards?

[lindaxiang]

@Buwujiu , Data Categories in QA are a bit messy. In Prod, we should not have that many categories, maybe we can make the info on file cards to be consistent with facet in the file repository.

[Buwujiu]

@Buwujiu , Data Categories in QA are a bit messy. In Prod, we should not have that many categories, maybe we can make the info on file cards to be consistent with facet in the file repository.

@lindaxiang do you mean we should have a fixed list of Data Category on the available file cards? would this. be easier for users?

[lindaxiang]

@Buwujiu no, I meant the dynamic list of Data Categories are preferable. But if it is hard to implement, we can use a fixed list. And we will need to update it whenever new Category is added.

[Buwujiu]

@Buwujiu no, I meant the dynamic list of Data Categories are preferable.

@lindaxiang is it possible that a donor might not have files in data categories? Say we have 8 categories in total, but some donors might only have files in 5 of those categories?