Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EPIC - NIH specific tables exporting #1862

Open
leandroradusky opened this issue Jan 24, 2023 — with Manas.Tech Commit · 2 comments
Open

EPIC - NIH specific tables exporting #1862

leandroradusky opened this issue Jan 24, 2023 — with Manas.Tech Commit · 2 comments
Labels
Epic This task describes the overall expected behaviour for a specific feature

Comments

Copy link
Contributor

leandroradusky commented Jan 24, 2023

Is the awardee who will export these files from the system, there will be a new button next to the actual Download charts as SVG & Download PDF on the reports page, named Download NIH tables or similar. They will have to upload them afterwards in a place that is out of our reach.

There will be three tables (csv format) to be exported:

  1. One with one row per sample, aggregating data from the sample, it's batch etc;
  2. One with one row per sample, containing information about the results obtained by the awardee on their machines;
  3. One with general results of the whole panel's test (sensitivity, specificity, LOD, etc.)

Some data we don't have it within CDx, especially on table 2) (name of the protocol, units of the readout, technology used, etc.) and we will just have to warn the awardee before downloading that some data needs to be manually fulfilled by them.

The batches entity within CDx is missing some data for these tables to be complete, if we're implementing this feature, this columns will need to be added to batches (PANGO_lineage, WHO_label, etc). This missing info differs from the last bullet point since this is data not available for the awardee: the batches info belongs to the University.

They have all the batches information on a spreadsheet: if we add these columns, when we implement the data migration we will have to map these columns for the existing batches taking this spreadsheet as reference for the first time (or alternatively, they will have to go batch by batch defining it for the existent batches, but I mentioned that this one-time migration can be done). For new batches they will define the full information.

@leandroradusky leandroradusky changed the title EPIC - NIH-specific tables exporting [epic] NIH-specific tables exporting Jan 24, 2023
@leandroradusky leandroradusky changed the title [epic] NIH-specific tables exporting EPIC - NIH specific tables exporting Jan 24, 2023
@leandroradusky leandroradusky added the Epic This task describes the overall expected behaviour for a specific feature label Jan 24, 2023
@diegoliberman
Copy link
Contributor

They have all the batches information on a spreadsheet: if we add these columns, when we implement the data migration we will have to map these columns for the existing batches taking this spreadsheet as reference for the first time (or alternatively, they will have to go batch by batch defining it for the existent batches, but I mentioned that this one-time migration can be done). For new batches they will define the full information.

@leandroradusky did you ask how many batches they have today? If there are just a few, I think I'd suggest for them to manually update them.

@leandroradusky
Copy link
Contributor Author

I didn't ask, but when I had the call with them I briefly saw the spreadsheet and it is in the order of ~25-30.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic This task describes the overall expected behaviour for a specific feature
Projects
None yet
Development

No branches or pull requests

2 participants