| Page Properties |
|---|
GDM 2| 3 | | Epic | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 3ed8d091-172c-31ee-8b1a-f688a0e72656 |
|---|
| key | GDM-170 |
|---|
|
|
|---|
| Document status | |
|---|
| Document owner | |
|---|
| Designer |
|
|---|
| Tech lead |
|
|---|
| Technical writers |
|
|---|
| QA |
|
|---|
|
Objective
To be able to append a dataset to an existing dataset so that extracts are associated with the expected dnarun IDs
Success metrics
| Goal | Metric |
|---|
| To be access the dataset wizard from a dataset page in the data loader by having an append button (this can be underneath the dataset wizard button) | Be able to overide a dataset being loaded to an existing dataset by clicking an 'append' button so that the dataset wizard is made available |
| To be able to append a dataset to an existing dataset using the dataset wizard in one of two directions, where' directions' described markers or samples (dnaruns) | two datasets with common samples or markers loaded to a single dataset name. |
| To be able to receive appropriate error messages if samples or markers associated with the new matrix are not contained within the existing matrix | If matrices can not be appropriately appended (either due to samples or markers not being contained within the first martrix) receive error message "some samples or markers are not contained within the first dataset and have been rejected, or "some samples or markers were already present in the first dataset and have been rejected" |
| To be able to extract data so that the two datasets to a single dataset name loaded look like a single dataset with dnaruns and markers aligned | Common markers and samples across the 2 datasets should be aligned in the extract |
Assumptions
A matching sample matches at: sample_name, sample_num, and dnarun_name combination
| View file |
|---|
| name | load 2 matrices.xlsx |
|---|
| height | 250 |
|---|
|
| View file |
|---|
| name | append diagrams.pptx |
|---|
| height | 250 |
|---|
|
Milestones
| Roadmap Planner |
|---|
| maplinks | |
|---|
| timeline | true |
|---|
| pagelinks | |
|---|
| source | %7B%22title%22%3A%22Roadmap%20Planner%22%2C%22timeline%22%3A%7B%22startDate%22%3A%222018-07-16%2000%3A00%3A00%22%2C%22endDate%22%3A%222019-06-16%2000%3A00%3A00%22%2C%22displayOption%22%3A%22MONTH%22%7D%2C%22lanes%22%3A%5B%7B%22title%22%3A%22Dashboard%22%2C%22color%22%3A%7B%22lane%22%3A%22%23f6c342%22%2C%22bar%22%3A%22%23fadb8e%22%2C%22text%22%3A%22%23594300%22%2C%22count%22%3A1%7D%2C%22bars%22%3A%5B%7B%22title%22%3A%22Feature%201%22%2C%22description%22%3A%22This%20is%20the%20first%20bar.%22%2C%22startDate%22%3A%222018-07-01%2000%3A00%3A00%22%2C%22duration%22%3A2%2C%22rowIndex%22%3A0%2C%22id%22%3A%22eeb2d902-e723-4ff0-a10d-43a5793089a4%22%2C%22pageLink%22%3A%7B%7D%7D%2C%7B%22title%22%3A%22Feature%202%22%2C%22description%22%3A%22This%20is%20the%20second%20bar.%22%2C%22startDate%22%3A%222018-09-02%2011%3A38%3A36%22%2C%22duration%22%3A2.297029702970297%2C%22rowIndex%22%3A1%2C%22id%22%3A%220e8f437c-39f1-4d70-b85b-3ca89fd57a00%22%2C%22pageLink%22%3A%7B%7D%7D%2C%7B%22rowIndex%22%3A0%2C%22startDate%22%3A%222018-11-15%2006%3A10%3A41%22%2C%22id%22%3A%2290251c8c-3b74-4d2b-b850-684ffd40514b%22%2C%22title%22%3A%22Feature%203%22%2C%22description%22%3A%22%22%2C%22duration%22%3A2.00990099009901%2C%22pageLink%22%3A%7B%7D%7D%2C%7B%22rowIndex%22%3A1%2C%22startDate%22%3A%222019-01-18%2019%3A14%3A51%22%2C%22id%22%3A%22d0529fe8-6c8c-45e8-8078-d75c2f063dd9%22%2C%22title%22%3A%22Feature%204%22%2C%22description%22%3A%22%22%2C%22duration%22%3A2.01980198019802%2C%22pageLink%22%3A%7B%7D%7D%5D%7D%2C%7B%22title%22%3A%22Notification%22%2C%22color%22%3A%7B%22lane%22%3A%22%233b7fc4%22%2C%22bar%22%3A%22%236c9fd3%22%2C%22text%22%3A%22%23ffffff%22%2C%22count%22%3A1%7D%2C%22bars%22%3A%5B%7B%22title%22%3A%22iOS%20App%22%2C%22description%22%3A%22This%20is%20the%20third%20bar.%22%2C%22startDate%22%3A%222018-07-13%2021%3A23%3A10%22%2C%22duration%22%3A2.5%2C%22rowIndex%22%3A0%2C%22id%22%3A%22dd93afcd-2704-4253-adb8-809a336cc5ba%22%2C%22pageLink%22%3A%7B%7D%7D%2C%7B%22rowIndex%22%3A0%2C%22startDate%22%3A%222018-10-10%2004%3A59%3A24%22%2C%22id%22%3A%228dc8bc2d-b7cb-44a8-b526-7d1ede51f690%22%2C%22title%22%3A%22Android%22%2C%22description%22%3A%22%22%2C%22duration%22%3A2.4752475247524752%2C%22pageLink%22%3A%7B%7D%7D%5D%7D%5D%2C%22markers%22%3A%5B%7B%22title%22%3A%22Milestone%201%22%2C%22markerDate%22%3A%222018-07-31%2016%3A38%3A01%22%7D%2C%7B%22markerDate%22%3A%222018-10-08%2001%3A25%3A32%22%2C%22title%22%3A%22Go%2FNo%20go%22%7D%2C%7B%22markerDate%22%3A%222018-12-31%2001%3A54%3A03%22%2C%22title%22%3A%22Milestone%202%22%7D%5D%7D |
|---|
| title | Roadmap%20Planner |
|---|
| hash | c013a8cf46e3276583f2ddb4893243e4 |
|---|
|
Requirements
| # | Requirement | User Story | Importance | Jira Issue | Notes |
|---|
| 1 | Need to be able to append a dataset to an existing dataset and have the dnaruns and markers align appropriately | - For large sequencing experiments the data is returned in separate files, usually separated by chromosome. Sometimes these are too big to load in one go and each chromosome will be loaded separately - currently to different datasets within the same experiment. Even though the dnarun names are the same for these different datasets, they are given a separate dataset dnarun_name ID and when extracted the data are not aligned under a common dnarun_name/sample name. This can be done by appending a dataset to an existing dataset
- Some vendors may only run 1 plate of samples at a time and return data sequentially. All plates would be run with the same set of markers. Plate one set of samples may be loaded to a dataset, and when plate 2 is returned the new data can be matched by markers and appending with the additional samples.
- Due to lack of availability of marker inventory, vendors may not be able to run all requested markers at once. They could run all samples against available markers, and then at a later stage run the same samples against the remaining markers when they become available. The second dataset can be appended to the first dataset by matching by samples and appending with the additional markers.
| High
|
|
|
| 2 | Access dataset wizard form dataset page in loader UI even if a dataset has been loaded by clicking on an 'Append' button | User cannot currently add a dataset to an existing dataset as the dataset wizard is locked in the loader UI | |
|
|
| 3 | Extracted data needs to be aligned to the appropriate dnarun_names and markers |
|
|
|
|
User interaction and design
append
Open Questions
| Question | Answer | Date Answered |
|---|
| If there is overlap in both sample and marker dimensions, how do we know which dimension the user is trying to update? | Josh suggested having an append markers to samples, or append samples to markers buttons so it is clear |
|
Out of Scope
We will not sort samples or markers to match the samples or markers in an existing dataset. Samples and markers need to be sorted in the same order that they were in in the first dataset that is being appended to.
We will not replace any existing data ie sample/marker combinations in the existing dataset. These data will be rejected with an appropriate error