-
Notifications
You must be signed in to change notification settings - Fork 28
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #296 from cidgoh/example-data-0-15-4
example data for 0.15.4 release
- Loading branch information
Showing
14 changed files
with
51 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# CanCOGeN Example Input Data | ||
This directory contains example input/test data for the Canadian COVID Genomics Network (CanCOGeN) DataHarmonizer application template: `CanCOGeN Covid-19`. This data is appropriate for testing up to the version appended to the end of the file name, for example: | ||
|
||
- `validTestData_0-15-4.csv` is _valid_ for version `0.15.4` of the DataHarmonizer. | ||
|
||
## Valid Test Data | ||
|
||
Demonstrates _valid_ example input, from controlled vocabulary and date formats to free text strings, for all minimal metadata fields and some recommended/enhanced metadata fields. | ||
|
||
## Invalid Test Data | ||
|
||
Demonstrates _invalid_ example input, from controlled vocabulary and date formats, for all minimal metadata fields and some recommended/enhanced metadata fields. After validating, empty cells that require input appear dark red while invalid cell contents appear light red. | ||
|
||
There are special validation rules for some fields, for example: | ||
|
||
- There cannot be duplicates of the database identifier `specimen collector sample ID` field. When duplicates occur the corresponding cells will be flagged light red: | ||
|
||
> ![invalidData_specimenCollectorSampleID.png](/images/invalid/invalidData_specimenCollectorSampleID.png?raw=true) | ||
- Sample collection date cannot be before SARS-CoV-2 sampling began even when formatted using the appropriate ISO 8601 standard format "YYYY-MM-DD": | ||
|
||
> ![invalidData_sampleCollectionDate.png](/images/invalid/invalidData_sampleCollectionDate.png?raw=true) |
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.