Page Properties | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Objective
Client's Goal: as per GR-136 (Jira server):
GOBii-GDM has been designed to allow breeding programs define their own meta information they would like to store without having to make modifications to database schema. These meta information are referred to as property fields or simply properties.
...
- For sample.file
- Props (both system and user defined)
- germplasm props
- dnasample props
- project props
- IDs:
- germplasm_id
- dnasample_id
- dnarun_id
- Props (both system and user defined)
- For marker.file:
- marker props (both system and user defined)
- IDs:
- marker_id
- linkage_group_id
- Headers for props fields in the files should be prefixed with the main entity table name. e.g. trial_name in dnasample props should have a header "dnasample_trial_name" in sample.file
- Dataset.hmp.txt will contain all the props fields, both system and user defined
Acceptance Criteria:
- 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
Requirements
...
...
As a GDM user, I want to be able to extract additional fields including various props and IDs.
For sample.file
...
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
...
- germplasm props
- dnasample props
- project props
...
- germplasm_id
- dnasample_id
- dnarun_id
...
Status | ||||
---|---|---|---|---|
|
...
As a GDM user, I want to be able to extract additional fields including various props and IDs.
For marker.file:
- marker props (both system and user defined)
- IDs:
- marker_id
- linkage_group_id
- Headers for props fields in marker.file should be prefixed with the main entity table name. e.g. probe1 in dnasample props should have a header "marker_probe1" in marker.file
...
As a GDM user, I want to be able to extract additional props fields and see them in Dataset.hmp.txt
...
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 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
User interaction and design
Open Questions
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 | ||||
---|---|---|---|---|
|