Page Properties | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- Extract output sample.file contains the props, both system and user defined, and the various IDs (as listed above)
- Extract output marker.file contains the props, both system and user defined, and the various IDs (as listed above)
- Extract output Dataset.hmp.txt contains all the props fields, both system and user defined
Success metrics
...
Assumptions
...
Notes from meeting Wed 11/20:
Kevin had a question as to conflicts if a property has the same name in both system and user defined
Nomenclature - We may need to prefix user defined props with something in order to remove any conflicts with system defined props
Liz does not want any names changed that are currently in the extract now to prevent downstream QC analysis to fail
Append to the end, the remaining system props and after that, the dynamic user property list
List any assumptions you have about your users, technical constraints, or business goals (e.g., Most users will access this feature from a tablet)Assumptions
Issues in Epic
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
Question | Answer | Date Answered |
---|---|---|
Should the following properties be extracted:
| yes to project props, no to mapset and platform props | |
What samples fields should be included in Hapmap file? | all props fields should be included |
...
View file | ||||
---|---|---|---|---|
|
View file | ||||
---|---|---|---|---|
|