...
Collection metadata will be used with all guidance in this section and are organized with 1 set of metadata per domain.All collection metadata begin with a description of the domain.
| Jira |
|---|
| showSummary | false |
|---|
| server | Issue Tracker (JIRA) |
|---|
| serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
|---|
| key | TOBA-395 |
|---|
|
A metadata specification follows to describe data collection fields and their attributes. Assumptions for the domain are also provided to further guide implementation. Metadata specifications are structured to present 1 or more rows for each data collection field with columns to describe attributes for each field. More than 1 row will be present in a metadata specification when data collection for a field can be performed using different scenarios/options. Multiple data collection options may also be provided within single cell
within in a row for a field with each option separated by
semicolonsa semicolon.
| Jira |
|---|
| showSummary | false |
|---|
| server | Issue Tracker (JIRA) |
|---|
| serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
|---|
| key | TOBA-396 |
|---|
|
Assumptions are provided to further guideEach column in a metadata table provides guidance which focuses 1 or more of following aspects of data collection
| Jira |
|---|
| showSummary | false |
|---|
| server | Issue Tracker (JIRA) |
|---|
| serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
|---|
| key | TOBA-406 |
|---|
|
:
...