Fill in project details in the table below. Type /date to quickly add the target release date, /jira to link to Jira epics or issues, and @mention functional owners to keep everyone on the same page.

Target release 2.2 Epic Document status Document owner Deb Weigand Designer Deb Weigand Tech lead KevinPalis Developer(s) KevinPalis QA Deb Weigand

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.

GDM currently allows users to only extract system defined properties, which are commonly known meta information that are pre-defined in any instance of GDM. This means that users cannot extract custom defined properties that they have loaded data to.

Users will like to be able to extract meta information they have loaded to GDM, both system defined and custom ones.

In addition, there is a need for IDs to be extracted for various entities.

User Story:

As a GDM user, I want to be able to extract additional fields including various props and IDs.

• For sample.file
  • Props (both system and user defined)
    • germplasm props
    • dnasample props
    • project props
  • IDs:
    • germplasm_id
    • dnasample_id
    • dnarun_id
• 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

List project goals and the metrics you'll use to judge its success

Assumptions

List any assumptions you have about your users, technical constraints, or business goals (e.g., Most users will access this feature from a tablet)

Requirements

User interaction and design

Add mockups, diagrams, or visual designs related to these requirements. Type /image to upload a file.

Open Questions

Out of Scope

List the features discussed which are out of scope or might be revisited in a later release.