diff --git a/variable-level-metadata-schema/docs/html-rendered-schemas/jsonschema-csvtemplate-fields.html b/variable-level-metadata-schema/docs/html-rendered-schemas/jsonschema-csvtemplate-fields.html index ab5f5e3..9d25853 100644 --- a/variable-level-metadata-schema/docs/html-rendered-schemas/jsonschema-csvtemplate-fields.html +++ b/variable-level-metadata-schema/docs/html-rendered-schemas/jsonschema-csvtemplate-fields.html @@ -1,4 +1,4 @@ - HEAL Variable Level Metadata Fields

HEAL Variable Level Metadata Fields

Type: object

!!! note "Highly encouraged"

Only name and description properties are required.
For categorical variables, constraints.enum and enumLabels (where applicable) properties are highly encouraged.
For studies using HEAL or other common data elements (CDEs), standardsMappings information is highly encouraged.
type and format properties may be particularly useful for some variable types (e.g. date-like variables)

Type: string

The version of the schema used in agreed upon convention of major.minor.path (e.g., 1.0.2)

NOTE: This is NOT for versioning of each indiviual data dictionary instance.
Rather, it is the
version of THIS schema document. See version property (below) if specifying the individual data dictionary instance
version.

If generating a vlmd document as a csv file, include this version in
every row/record to indicate this is a schema level property
(not applicable for the json version as this property is already at the schema/root level)

Must match regular expression: \d+\.\d+\.\d+
Examples:

"1.0.0"
+ HEAL Variable Level Metadata Fields 

HEAL Variable Level Metadata Fields

Type: object

!!! note "Highly encouraged"

  • Only name and description properties are required.
  • For categorical variables, constraints.enum and enumLabels (where applicable) properties are highly encouraged.
  • For studies using HEAL or other common data elements (CDEs), standardsMappings information is highly encouraged.
  • type and format properties may be particularly useful for some variable types (e.g. date-like variables)

Type: string

The version of the schema used in agreed upon convention of major.minor.path (e.g., 1.0.2)

NOTE: This is NOT for versioning of each indiviual data dictionary instance.
Rather, it is the
version of THIS schema document. See version property (below) if specifying the individual data dictionary instance
version.

If generating a vlmd document as a csv file, include this version in
every row/record to indicate this is a schema level property
(not applicable for the json version as this property is already at the schema/root level)

Must match regular expression: \d+\.\d+\.\d+
Examples:

"1.0.0"
 
"0.2.0"
 

Type: string

The section, form, survey instrument, set of measures or other broad category used
to group variables. Previously called "module."


Examples:

"Demographics"
 
"PROMIS"
@@ -24,4 +24,4 @@
 

Type: stringFormat: uri

The url that links out to the published, standardized mapping of a variable (e.g., common data element)


Example:

"https://evs.nci.nih.gov/ftp1/CDISC/SDTM/SDTM%20Terminology.html#CL.C74457.RACE"
 

Type: string

The source of the standardized variable. Note, this property is required if
an id is specified.


Example:

"CDISC"
 

Type: string

The id locating the individual mapping within the given source.
Note, the standardsMappings[0].source property is required if
this property is specified.


Example:

"C74457"
-
\ No newline at end of file +
\ No newline at end of file diff --git a/variable-level-metadata-schema/docs/html-rendered-schemas/jsonschema-jsontemplate-data-dictionary.html b/variable-level-metadata-schema/docs/html-rendered-schemas/jsonschema-jsontemplate-data-dictionary.html index 8b77d36..5a08ba0 100644 --- a/variable-level-metadata-schema/docs/html-rendered-schemas/jsonschema-jsontemplate-data-dictionary.html +++ b/variable-level-metadata-schema/docs/html-rendered-schemas/jsonschema-jsontemplate-data-dictionary.html @@ -4,7 +4,7 @@

Type: enum (of string)

An abbreviated name/acronym from a controlled vocabulary referencing the resource (e.g., program or repository)
containing the instrument, or a set of items which encompass a variable in this variable level metadata document (if at the root level or the document level)
or the individual variable (if at the field level).

Must be one of:

  • "heal-cde"

Type: string

Examples:

"Adult demographics"
 
"adult-demographics"
 

Type: string

A code or other string that identifies the instrument within the source.
This should always be from the source's formal, standardized identification system


Example:

"5141"
-

Type: array of object

Each item of this array must be:

Type: object

!!! note "Highly encouraged"

Only name and description properties are required.
For categorical variables, constraints.enum and enumLabels (where applicable) properties are highly encouraged.
For studies using HEAL or other common data elements (CDEs), standardsMappings information is highly encouraged.
type and format properties may be particularly useful for some variable types (e.g. date-like variables)

Type: string

The version of the schema used in agreed upon convention of major.minor.path (e.g., 1.0.2)

NOTE: This is NOT for versioning of each indiviual data dictionary instance.
Rather, it is the
version of THIS schema document. See version property (below) if specifying the individual data dictionary instance
version.

If generating a vlmd document as a csv file, include this version in
every row/record to indicate this is a schema level property
(not applicable for the json version as this property is already at the schema/root level)

Must match regular expression: \d+\.\d+\.\d+
Examples:

"1.0.0"
+

Type: array of object

Each item of this array must be:

Type: object

!!! note "Highly encouraged"

  • Only name and description properties are required.
  • For categorical variables, constraints.enum and enumLabels (where applicable) properties are highly encouraged.
  • For studies using HEAL or other common data elements (CDEs), standardsMappings information is highly encouraged.
  • type and format properties may be particularly useful for some variable types (e.g. date-like variables)

Type: string

The version of the schema used in agreed upon convention of major.minor.path (e.g., 1.0.2)

NOTE: This is NOT for versioning of each indiviual data dictionary instance.
Rather, it is the
version of THIS schema document. See version property (below) if specifying the individual data dictionary instance
version.

If generating a vlmd document as a csv file, include this version in
every row/record to indicate this is a schema level property
(not applicable for the json version as this property is already at the schema/root level)

Must match regular expression: \d+\.\d+\.\d+
Examples:

"1.0.0"
 
"0.2.0"
 

Type: string

The section, form, survey instrument, set of measures or other broad category used
to group variables. Previously called "module."


Examples:

"Demographics"
 
"PROMIS"
@@ -126,4 +126,4 @@
 

Type: object

A standardized item (ie field, variable etc) mapped to this individual variable.

Type: stringFormat: uri

The url that links out to the published, standardized mapping of a variable (e.g., common data element)


Example:

"https://evs.nci.nih.gov/ftp1/CDISC/SDTM/SDTM%20Terminology.html#CL.C74457.RACE"
 

Type: string

The source of the standardized variable. Note, this property is required if
an id is specified.


Example:

"CDISC"
 

Type: string

The id locating the individual mapping within the given source.
Note, the standardsMappings[0].source property is required if
this property is specified.


Example:

"C74457"
-
\ No newline at end of file + \ No newline at end of file diff --git a/variable-level-metadata-schema/docs/md-rendered-schemas/jsonschema-csvtemplate-fields.md b/variable-level-metadata-schema/docs/md-rendered-schemas/jsonschema-csvtemplate-fields.md index 099d479..a784c50 100644 --- a/variable-level-metadata-schema/docs/md-rendered-schemas/jsonschema-csvtemplate-fields.md +++ b/variable-level-metadata-schema/docs/md-rendered-schemas/jsonschema-csvtemplate-fields.md @@ -14,10 +14,10 @@ The aim of this HEAL metadata piece is to track and provide basic information ab !!! note "Highly encouraged" - Only `name` and `description` properties are required. - For categorical variables, `constraints.enum` and `enumLabels` (where applicable) properties are highly encouraged. - For studies using HEAL or other common data elements (CDEs), `standardsMappings` information is highly encouraged. - `type` and `format` properties may be particularly useful for some variable types (e.g. date-like variables) + - Only `name` and `description` properties are required. + - For categorical variables, `constraints.enum` and `enumLabels` (where applicable) properties are highly encouraged. + - For studies using HEAL or other common data elements (CDEs), `standardsMappings` information is highly encouraged. + - `type` and `format` properties may be particularly useful for some variable types (e.g. date-like variables) ## Properties (i.e., fields or variables) diff --git a/variable-level-metadata-schema/docs/md-rendered-schemas/jsonschema-jsontemplate-data-dictionary.md b/variable-level-metadata-schema/docs/md-rendered-schemas/jsonschema-jsontemplate-data-dictionary.md index daff87d..8ef83bd 100644 --- a/variable-level-metadata-schema/docs/md-rendered-schemas/jsonschema-jsontemplate-data-dictionary.md +++ b/variable-level-metadata-schema/docs/md-rendered-schemas/jsonschema-jsontemplate-data-dictionary.md @@ -41,10 +41,10 @@ A set of standardized instruments linked to all variables within the `fields` pr !!! note "Highly encouraged" - Only `name` and `description` properties are required. - For categorical variables, `constraints.enum` and `enumLabels` (where applicable) properties are highly encouraged. - For studies using HEAL or other common data elements (CDEs), `standardsMappings` information is highly encouraged. - `type` and `format` properties may be particularly useful for some variable types (e.g. date-like variables) + - Only `name` and `description` properties are required. + - For categorical variables, `constraints.enum` and `enumLabels` (where applicable) properties are highly encouraged. + - For studies using HEAL or other common data elements (CDEs), `standardsMappings` information is highly encouraged. + - `type` and `format` properties may be particularly useful for some variable types (e.g. date-like variables) ### Properties for each `fields` record diff --git a/variable-level-metadata-schema/schemas/frictionless/csvtemplate/fields.json b/variable-level-metadata-schema/schemas/frictionless/csvtemplate/fields.json index 011eb58..6b900b0 100644 --- a/variable-level-metadata-schema/schemas/frictionless/csvtemplate/fields.json +++ b/variable-level-metadata-schema/schemas/frictionless/csvtemplate/fields.json @@ -1,6 +1,6 @@ { "version": "0.2.0", - "description": "\n\n!!! note \"Highly encouraged\"\n\n Only `name` and `description` properties are required. \n For categorical variables, `constraints.enum` and `enumLabels` (where applicable) properties are highly encouraged. \n For studies using HEAL or other common data elements (CDEs), `standardsMappings` information is highly encouraged.\n `type` and `format` properties may be particularly useful for some variable types (e.g. date-like variables)\n", + "description": "\n\n!!! note \"Highly encouraged\"\n\n - Only `name` and `description` properties are required. \n - For categorical variables, `constraints.enum` and `enumLabels` (where applicable) properties are highly encouraged. \n - For studies using HEAL or other common data elements (CDEs), `standardsMappings` information is highly encouraged.\n - `type` and `format` properties may be particularly useful for some variable types (e.g. date-like variables)\n", "title": "HEAL Variable Level Metadata Fields", "fields": [ { @@ -67,18 +67,18 @@ "type": "string", "constraints": { "enum": [ - "time", + "duration", + "yearmonth", "geopoint", + "datetime", "any", "date", - "datetime", - "year", + "string", "number", "integer", - "duration", - "boolean", - "string", - "yearmonth" + "year", + "time", + "boolean" ] } }, diff --git a/variable-level-metadata-schema/schemas/jsonschema/csvtemplate/fields.json b/variable-level-metadata-schema/schemas/jsonschema/csvtemplate/fields.json index 62bd1e9..72b8bb1 100644 --- a/variable-level-metadata-schema/schemas/jsonschema/csvtemplate/fields.json +++ b/variable-level-metadata-schema/schemas/jsonschema/csvtemplate/fields.json @@ -1,7 +1,7 @@ { "version": "0.2.0", "title": "HEAL Variable Level Metadata Fields", - "description": "\n\n!!! note \"Highly encouraged\"\n\n Only `name` and `description` properties are required. \n For categorical variables, `constraints.enum` and `enumLabels` (where applicable) properties are highly encouraged. \n For studies using HEAL or other common data elements (CDEs), `standardsMappings` information is highly encouraged.\n `type` and `format` properties may be particularly useful for some variable types (e.g. date-like variables)\n", + "description": "\n\n!!! note \"Highly encouraged\"\n\n - Only `name` and `description` properties are required. \n - For categorical variables, `constraints.enum` and `enumLabels` (where applicable) properties are highly encouraged. \n - For studies using HEAL or other common data elements (CDEs), `standardsMappings` information is highly encouraged.\n - `type` and `format` properties may be particularly useful for some variable types (e.g. date-like variables)\n", "type": "object", "required": [ "name", diff --git a/variable-level-metadata-schema/schemas/jsonschema/data-dictionary.json b/variable-level-metadata-schema/schemas/jsonschema/data-dictionary.json index 5a490ab..979fbf1 100644 --- a/variable-level-metadata-schema/schemas/jsonschema/data-dictionary.json +++ b/variable-level-metadata-schema/schemas/jsonschema/data-dictionary.json @@ -82,7 +82,7 @@ "type": "array", "items": { "title": "HEAL Variable Level Metadata Fields", - "description": "\n\n!!! note \"Highly encouraged\"\n\n Only `name` and `description` properties are required. \n For categorical variables, `constraints.enum` and `enumLabels` (where applicable) properties are highly encouraged. \n For studies using HEAL or other common data elements (CDEs), `standardsMappings` information is highly encouraged.\n `type` and `format` properties may be particularly useful for some variable types (e.g. date-like variables)\n", + "description": "\n\n!!! note \"Highly encouraged\"\n\n - Only `name` and `description` properties are required. \n - For categorical variables, `constraints.enum` and `enumLabels` (where applicable) properties are highly encouraged. \n - For studies using HEAL or other common data elements (CDEs), `standardsMappings` information is highly encouraged.\n - `type` and `format` properties may be particularly useful for some variable types (e.g. date-like variables)\n", "type": "object", "required": [ "name",