This topic explains the editabile properties of datasets.

To edit dataset properties, go to the dataset grid view and click Manage, then click Edit Definition.

  • Name: Required. This name must be unique. It is used when identifying datasets during data upload.
  • Label: The name of the dataset shown to users. If no Label is provided, the Name is used.
  • Cohort Association: Datasets may be cohort specific, or associated with all cohorts.
  • Additional Key Column: If the dataset has more than one row per participant/visit, an additional key field must be provided to differentiate rows. There can be at most one row in the dataset for each combination of participant, visit, and key. See below for more information. Options:
    • None: No additional key.
    • Data Field: A user-managed key field.
    • Managed Field: A numeric or string field that is managed by the server to make each new entry unique. Numbers will be assigned auto-incrementing integer values, strings will be assigned globally unique identifiers (GUIDs).
  • Demographic Data: Whether this is a demographic dataset, which has only a single row per participant in the study.
  • Show In Overview: Check to show this dataset in the overview grid by default.
  • ID: Required. The unique, numerical identifier for your dataset. It is defined automatically during dataset creation and cannot be modified. The combination of container and dataset is the primary key.
  • Category: Assigning a category to a dataset will group it with similar datasets in the navigator and data browser.
  • Dataset Tag: An additional, flexible, way to categorize datasets. For instance, you might tag certain datasets as "Reference" for easy retrieval as a set across categories.
  • Description: An optional longer description of your dataset. The Description can only be specified when you Edit Dataset Properties, not at the time of dataset creation.

Details: Additional Key Columns

Some datasets may have more than one row for each participant/visit pairing. For example, a sample might be tested for neutralizing antibodies to several different virus strains. Each test (sample/date/virus combination) could then become a single unique row of a dataset. See sample table below. These data rows are not "legal" in a standard dataset because they both have the same participant/visit values. An additional key field is needed (such as VirusId in this example) to ensure a unique combination of participant/sequenceNum/key for each row.

ParticipantIdSequenceNum (=Visit)VirusIdValuePercent
12345101Virus1273127.87770%
12345101Virus228788.0280%

Such a "user managed" key is assigned using the Data Field pulldown, which will list the fields in the dataset.

Note: Demographic datasets are not eligible for additional keys. To set an additional key, you must uncheck the Demographic Data property first.

Using Time as an Additional Key

In a date-based or continuous study, an additional third key option is to use the Time (from Date/Time) portion of a datestamp field. In cases where multiple measurements happen on a given day or visit (tracking primate weight for example), the time portion of the date field can be used as an additional key without requiring duplication of this information in an additional column.

Related Topics

Discussion

previousnext
 
expand all collapse all