diff --git a/hdr_schemata/models/HDRUK/2.1.2/schema.json b/hdr_schemata/models/HDRUK/2.1.2/schema.json
index 83fcbfd..f849a31 100644
--- a/hdr_schemata/models/HDRUK/2.1.2/schema.json
+++ b/hdr_schemata/models/HDRUK/2.1.2/schema.json
@@ -1923,7 +1923,7 @@
"issued": {
"description": "Datetime stamp of when this metadata version was initially issued",
"format": "date-time",
- "title": "Metadata Issued Datetime',",
+ "title": "Metadata Issued Datetime",
"type": "string"
},
"modified": {
diff --git a/hdr_schemata/models/HDRUK/2.1.3/schema.json b/hdr_schemata/models/HDRUK/2.1.3/schema.json
index df830c7..d5cc01d 100644
--- a/hdr_schemata/models/HDRUK/2.1.3/schema.json
+++ b/hdr_schemata/models/HDRUK/2.1.3/schema.json
@@ -1707,7 +1707,7 @@
}
],
"description": "Please indicate the frequency of distribution release. If a dataset is distributed regularly please choose a distribution release periodicity from the constrained list and indicate the next release date. When the release date becomes historical, a new release date will be calculated based on the publishing periodicity. If a dataset has been published and will remain static please indicate that it is static and indicated when it was released. If a dataset is released on an irregular basis or \u201con-demand\u201d please indicate that it is Irregular and leave release date as null. If a dataset can be published in real-time or near-real-time please indicate that it is continuous and leave release date as null. Notes: see https://www.dublincore.org/specifications/dublin-core/collection-description/frequency/",
- "guidance": "'- Please indicate the frequency of publishing.\\n- If a dataset is published regularly please choose a publishing periodicity from the constrained list and indicate the next release date.\\n- When the release date becomes historical, a new release date will be calculated based on the publishing periodicity.\\n- If a dataset has been published and will remain static please indicate that it is static and indicate when it was released.\\n- If a dataset is released on an irregular basis or \u201con-demand\u201d please indicate that it is Irregular and leave release date as null.\\n- If a dataset can be published in real-time or near-real-time please indicate that it is continuous and leave release date as null.\\n- Notes: see \\n- **Static**: Dataset published once.\\n- **Irregular**: Dataset published at uneven intervals.\\n- **Continuous**: Dataset published without interruption.\\n- **Biennial**: Dataset published every two years.\\n- **Annual**: Dataset published occurs once a year.\\n- **Biannual**: Dataset published twice a year.\\n- **Quarterly**: Dataset published every three months.\\n- **Bimonthly**: Dataset published every two months.\\n- **Monthly**: Dataset published once a month.\\n- **Biweekly**: Dataset published every two weeks.\\n- **Weekly**: Dataset published once a week.\\n- **Twice weekly**: Dataset published twice a week.\\n- **Daily**: Dataset published once a day.\\n- **Other**: Dataset published using other interval.',",
+ "guidance": "Please indicate the frequency of publishing.\\n- If a dataset is published regularly please choose a publishing periodicity from the constrained list and indicate the next release date.\\n- When the release date becomes historical, a new release date will be calculated based on the publishing periodicity.\\n- If a dataset has been published and will remain static please indicate that it is static and indicate when it was released.\\n- If a dataset is released on an irregular basis or \u201con-demand\u201d please indicate that it is Irregular and leave release date as null.\\n- If a dataset can be published in real-time or near-real-time please indicate that it is continuous and leave release date as null.\\n- Notes: see https://www.dublincore.org/specifications/dublin-core/collection-description/frequency/.\\n\\n Options:\\n- **Static**: Dataset published once.\\n- **Irregular**: Dataset published at uneven intervals.\\n- **Continuous**: Dataset published without interruption.\\n- **Biennial**: Dataset published every two years.\\n- **Annual**: Dataset published occurs once a year.\\n- **Biannual**: Dataset published twice a year.\\n- **Quarterly**: Dataset published every three months.\\n- **Bimonthly**: Dataset published every two months.\\n- **Monthly**: Dataset published once a month.\\n- **Biweekly**: Dataset published every two weeks.\\n- **Weekly**: Dataset published once a week.\\n- **Twice weekly**: Dataset published twice a week.\\n- **Daily**: Dataset published once a day.\\n- **Other**: Dataset published using other interval.",
"title": "Publishing Frequency"
}
},
@@ -1925,7 +1925,7 @@
"issued": {
"description": "Datetime stamp of when this metadata version was initially issued",
"format": "date-time",
- "title": "Metadata Issued Datetime',",
+ "title": "Metadata Issued Datetime",
"type": "string"
},
"modified": {
diff --git a/hdr_schemata/models/HDRUK/2.2.0/schema.json b/hdr_schemata/models/HDRUK/2.2.0/schema.json
index d43ab10..5c90046 100644
--- a/hdr_schemata/models/HDRUK/2.2.0/schema.json
+++ b/hdr_schemata/models/HDRUK/2.2.0/schema.json
@@ -2306,7 +2306,7 @@
"issued": {
"description": "Datetime stamp of when this metadata version was initially issued",
"format": "date-time",
- "title": "Metadata Issued Datetime',",
+ "title": "Metadata Issued Datetime",
"type": "string"
},
"modified": {
diff --git a/hdr_schemata/models/HDRUK/2.2.1/schema.json b/hdr_schemata/models/HDRUK/2.2.1/schema.json
index d94ec30..34c490e 100644
--- a/hdr_schemata/models/HDRUK/2.2.1/schema.json
+++ b/hdr_schemata/models/HDRUK/2.2.1/schema.json
@@ -947,7 +947,7 @@
"examples": [
"LOCAL,NHS DATA DICTIONARY"
],
- "guidance": "'- List standardised data models that the dataset has been stored in or transformed to, such as OMOP or FHIR.\\n- If the data is only available in a local format, please make that explicit. If you are using a standard that has not been included in the list, please use \u201cother\u201d and contact support desk to ask for an addition.\\n- **HL7 FHIR**: \\n- **HL7 V2**: \\n- **HL7 CDA**: \\n- **HL7 CCOW**: \\n- **DICOM**: \\n- **I2B2**: \\n- **IHE**: \\n- **OMOP**: \\n- **openEHR**: \\n- **Sentinel**: \\n- **PCORnet**: \\n- **CDISC**: \\n- **Local**: In-house developed data model\\n- **Other**: Other standardised data model\\n- **NHS Data Dictionary**: \\n- **NHS Scotland Data Dictionary**: \\n- **NHS Wales Data Dictionary**: ',",
+ "guidance": "- List standardised data models that the dataset has been stored in or transformed to, such as OMOP or FHIR.\\n- If the data is only available in a local format, please make that explicit. If you are using a standard that has not been included in the list, please use \u201cother\u201d and contact support desk to ask for an addition.\\n- **HL7 FHIR**: .\\n- **HL7 V2**: .\\n- **HL7 CDA**: .\\n- **HL7 CCOW**: .\\n- **DICOM**: .\\n- **I2B2**: .\\n- **IHE**: .\\n- **OMOP**: .\\n- **openEHR**: .\\n- **Sentinel**: .\\n- **PCORnet**: .\\n- **CDISC**: .\\n- **Local**: In-house developed data model.\\n- **Other**: Other standardised data model.\\n- **NHS Data Dictionary**: .\\n- **NHS Scotland Data Dictionary**: .\\n- **NHS Wales Data Dictionary**: .",
"title": "Alignment with standardised data models"
},
"language": {
@@ -1342,8 +1342,8 @@
"$ref": "#/$defs/MeasuredProperty"
}
],
- "description": "Descibe the property used to measure each observation.",
- "guidance": "The default value is 'COUNT' (e.g. the count of persons who are in the cohort)",
+ "description": "Descriptive term for the observation property measured. For example, people, procedures, x-rays, or diagnosis of type 1 diabetes. This could also be a specific SNOMED CT term.",
+ "guidance": "Descriptive term for the observation property measured.",
"title": "Measured property"
}
},
@@ -1476,7 +1476,7 @@
],
"default": null,
"description": "Please indicate the purpose(s) that the dataset was collected.",
- "guidance": "-**Research cohort**: Data collected for a defined group of people.\\n- **Study**: Data collected for a specific research study.\\n- **Disease registry**: Data collected as part of a disease registry.\\n- **Trial**: Data collected for as part of a clinical trial.\\n- **Care**: Data collected as part of routine clinical care.\\n- **Audit**: Data collected as part of an audit programme\\n- **Administrative**: Data collected for administrative and management information purposes\\n- **Financial**: Data collected either for payments or for billing\\n- **Other**: Data collected for other purpose',",
+ "guidance": "- **Research cohort**: Data collected for a defined group of people.\\n- **Study**: Data collected for a specific research study.\\n- **Disease registry**: Data collected as part of a disease registry.\\n- **Trial**: Data collected for as part of a clinical trial.\\n- **Care**: Data collected as part of routine clinical care.\\n- **Audit**: Data collected as part of an audit programme.\\n- **Administrative**: Data collected for administrative and management information purposes.\\n- **Financial**: Data collected either for payments or for billing.\\n- **Statutory**: ...........\\n- **Other**: Data collected for other purpose.",
"title": "Purpose of dataset collection"
},
"source": {
@@ -1493,7 +1493,7 @@
],
"default": null,
"description": "Please indicate the source of the data extraction.",
- "guidance": "- **EPR**: Data Extracted from Electronic Patient Record\\n- **Electronic survey**: Data has been extracted from electronic surveys\\n- **LIMS**: Data has been extracted from a laboratory information management system\\n- **Paper-based**: Data has been extracted from paper forms\\n- **Free text NLP**: Data has been extracted from unstructured freetext using natural language processing\\n- **Machine generated**: Data has been machine generated i.e. imaging\\n- **Other**: Data has been extracted by other means',",
+ "guidance": " - **EPR**: Data Extracted from Electronic Patient Record.\\n- **Electronic survey**: Data has been extracted from electronic surveys.\\n- **LIMS**: Data has been extracted from a laboratory information management system.\\n- **Paper-based**: Data has been extracted from paper forms.\\n- **Free text NLP**: Data has been extracted from unstructured freetext using natural language processing.\\n- **Machine generated**: Data has been machine generated i.e. imaging.\\n- **Other**: Data has been extracted by other means.",
"title": "Source of data extraction"
},
"collectionSituation": {
@@ -1561,7 +1561,7 @@
}
],
"default": null,
- "description": "Coverate by origin (geographical and situations).",
+ "description": "Coverage by origin (geographical and situations).",
"title": "Origin Coverage"
},
"temporal": {
@@ -2346,7 +2346,7 @@
"issued": {
"description": "Datetime stamp of when this metadata version was initially issued",
"format": "date-time",
- "title": "Metadata Issued Datetime',",
+ "title": "Metadata Issued Datetime",
"type": "string"
},
"modified": {
@@ -2424,7 +2424,7 @@
"title": "Enrichment and Linkage"
},
"observations": {
- "description": "Multiple observations about the dataset may be provided and users are expected to provide at least one observation \n(1..*). We will be supporting the schema.org observation model (https://schema.org/Observation) with default values. Users will be encouraged to provide their own statistical populations as the project progresses. \nExample: \n <b> Statistical Population 1 \n </b> type: StatisticalPopulation populationType: Persons numConstraints: 0 \n <b> Statistical Population 2 </b> type: StatisticalPopulation populationType: Events numConstraints: 0 <b> Statistical Population 3 </b> type: StatisticalPopulation populationType: Findings numConstraints: 0 typeOf: Observation observedNode: <b> Statistical Population 1 </b> measuredProperty: count measuredValue: 32937 observationDate: \u201c2017\u201d\"\n",
+ "description": "This section provides an overview of observations of your dataset linked to specific points in time. Multiple observations about the dataset are encouraged to be provided, including multiple observations of the same property at different timepoints. At least one observation is required.",
"items": {
"$ref": "#/$defs/Observation"
},
diff --git a/hdr_schemata/models/HDRUK/3.0.0/schema.json b/hdr_schemata/models/HDRUK/3.0.0/schema.json
index 36120c2..54d3ca3 100644
--- a/hdr_schemata/models/HDRUK/3.0.0/schema.json
+++ b/hdr_schemata/models/HDRUK/3.0.0/schema.json
@@ -23,7 +23,7 @@
}
],
"description": "Please provide details for the data access rights.",
- "guidance": "The URL of a webpage where the data access request process and/or guidance is provided. If there is more than one access process i.e. industry vs academic please provide both.- If such a resource or the underlying process doesn\u2019t exist, please provide \u201cIn Progress\u201d, until both the process and the documentation are ready.',",
+ "guidance": "The URL of a webpage where the data access request process and/or guidance is provided. If there is more than one access process i.e. industry vs academic please provide both separated by a comma.- If such a resource or the underlying process doesn\u2019t exist, please provide \u201cIn Progress\u201d, until both the process and the documentation are ready.",
"title": "Access rights"
},
"accessServiceCategory": {
@@ -67,11 +67,11 @@
}
],
"default": null,
- "description": "Please provide a brief description of the data access services that are available including: environment that is currently available to researchers;additional consultancy and services;any indication of costs associated. If no environment is currently available, please indicate the current plans and timelines when and how data will be made available to researchers Note: This value will be used as default access environment for all datasets submitted by the organisation. However, there will be the opportunity to overwrite this value for each dataset.",
+ "description": "Please provide a brief description of the data access services that are available including: environment that is currently available to researchers; additional consultancy and services; any indication of costs associated. If no environment is currently available, please indicate the current plans and timelines when and how data will be made available to researchers Note: This value will be used as default access environment for all datasets submitted by the organisation. However, there will be the opportunity to overwrite this value for each dataset.",
"examples": [
"https://cnfl.extge.co.uk/display/GERE/Research+Environment+User+Guide"
],
- "guidance": "Please provide a brief description of the data access services that are available including:- environment that is currently available to researchers- additional consultancy and services- any indication of costs associatedIf no environment is currently available, please indicate the current plans and timelines when and how data will be made available to researchers.Note: This value will be used as default access environment for all datasets submitted by the organisation. However, there will be the opportunity to overwrite this value for each dataset.',",
+ "guidance": "Please provide a brief description of the data access services that are available including:- environment that is currently available to researchers- additional consultancy and services- any indication of costs associated If no environment is currently available, please indicate the current plans and timelines when and how data will be made available to researchers. Note: This value will be used as default access environment for all datasets submitted by the organisation. However, there will be the opportunity to overwrite this value for each dataset.",
"title": "Access service description"
},
"accessRequestCost": {
@@ -85,7 +85,7 @@
],
"default": null,
"description": "Please provide link(s) to a webpage or description detailing the service or cost model for processing data access requests.",
- "guidance": "This information should cover the costs and/or services available to different audiences (i.e. academic, commercial, non-UK, etc.).",
+ "guidance": "This information should cover the costs and/or services available to different audiences (i.e. academic, commercial, non-UK, etc.). This can be in the form of text or a URL.",
"title": "Access request cost"
},
"deliveryLeadTime": {
@@ -99,7 +99,7 @@
],
"default": null,
"description": "Please provide an indication of the typical processing times based on the types of requests typically received.",
- "guidance": "Less than 1 week: Access request process typically processed in less than a week- 1-2 weeks: Access request process typically processed in one to two weeks- 2-4 weeks: Access request process typically processed in two to four weeks- 1-2 months: Access request process typically processed in one to two months- 2-6 months: Access request process typically processed in two to six months- More than 6 months: Access request process typically processed in more than six months- Variable: Access request lead time is variable- Not applicable: Access request process duration is not applicable- Other: If the typical timeframe does not fit into the broad ranges i.e. lightweight application vs linked data application, please choose \u201cOther\u201d and indicate the typical timeframe within the description for the dataset.',",
+ "guidance": "Less than 1 week: Access request process typically processed in less than a week.- 1-2 weeks: Access request process typically processed in one to two weeks.- 2-4 weeks: Access request process typically processed in two to four weeks.- 1-2 months: Access request process typically processed in one to two months.- 2-6 months: Access request process typically processed in two to six months.- More than 6 months: Access request process typically processed in more than six months.- Variable: Access request lead time is variable.- Not applicable: Access request process duration is not applicable.- Other: If the typical timeframe does not fit into the broad ranges i.e. lightweight application vs linked data application, please choose \u201cOther\u201d and indicate the typical timeframe within the description for the dataset.",
"title": "Time to dataset access"
},
"jurisdiction": {
@@ -118,7 +118,7 @@
}
],
"description": "Please use country code from ISO 3166-1 country codes and the associated ISO 3166-2 for regions, cities, states etc. for the country/state under whose laws the data subjects' data is collected, processed and stored.",
- "guidance": "\"- GB-ENG: England- GB-NIR: Northern Ireland- GB-SCT: Scotland- GB-WLS: Wales [Cymru GB-CYM]- GB-EAW: England and Wales- GB-GBN: Great Britain- AF: Afghanistan- AL: Albania- DZ: Algeria- AD: Andorra- AO: Angola- AG: Antigua and Barbuda- AR: Argentina- AM: Armenia- AU: Australia- AT: Austria- AZ: Azerbaijan- BS: Bahamas- BH: Bahrain- BD: Bangladesh- BB: Barbados- BY: Belarus- BE: Belgium- BZ: Belize- BJ: Benin- BT: Bhutan- BO: Bolivia (Plurinational State of)- BA: Bosnia and Herzegovina- BW: Botswana- BR: Brazil- BN: Brunei Darussalam- BG: Bulgaria- BF: Burkina Faso- BI: Burundi- CV: Cabo Verde- KH: Cambodia- CM: Cameroon- CA: Canada- CF: Central African Republic- TD: Chad- CL: Chile- CN: China- CO: Colombia- KM: Comoros- CG: Congo- CD: Congo, Democratic Republic of the- CR: Costa Rica- CI: C\u00f4te d'Ivoire- HR: Croatia- CU: Cuba- CY: Cyprus- CZ: Czechia- DK: Denmark- DJ: Djibouti- DM: Dominica- DO: Dominican Republic- EC: Ecuador- EG: Egypt- SV: El Salvador- GQ: Equatorial Guinea- ER: Eritrea- EE: Estonia- SZ: Eswatini- ET: Ethiopia- FJ: Fiji- FI: Finland- FR: France- GA: Gabon- GM: Gambia- GE: Georgia- DE: Germany- GH: Ghana- GR: Greece- GD: Grenada- GT: Guatemala- GN: Guinea- GW: Guinea-Bissau- GY: Guyana- HT: Haiti- VA: Holy See- HN: Honduras- HU: Hungary- IS: Iceland- IN: India- ID: Indonesia- IR: Iran (Islamic Republic of)- IQ: Iraq- IE: Ireland- IL: Israel- IT: Italy- JM: Jamaica- JP: Japan- JO: Jordan- KZ: Kazakhstan- KE: Kenya- KI: Kiribati- KP: Korea (Democratic People's Republic of)- KR: Korea, Republic of- KW: Kuwait- KG: Kyrgyzstan- LA: Lao People's Democratic Republic- LV: Latvia- LB: Lebanon- LS: Lesotho- LR: Liberia- LY: Libya- LI: Liechtenstein- LT: Lithuania- LU: Luxembourg- MG: Madagascar- MW: Malawi- MY: Malaysia- MV: Maldives- ML: Mali- MT: Malta- MH: Marshall Islands- MR: Mauritania- MU: Mauritius- MX: Mexico- FM: Micronesia (Federated States of)- MD: Moldova, Republic of- MC: Monaco- MN: Mongolia- ME: Montenegro- MA: Morocco- MZ: Mozambique- MM: Myanmar- NA: Namibia- NR: Nauru- NP: Nepal- NL: Netherlands- NZ: New Zealand- NI: Nicaragua- NE: Niger- NG: Nigeria- MK: North Macedonia- NO: Norway- OM: Oman- PK: Pakistan- PW: Palau- PA: Panama- PG: Papua New Guinea- PY: Paraguay- PE: Peru- PH: Philippines- PL: Poland- PT: Portugal- QA: Qatar- RO: Romania- RU: Russian Federation- RW: Rwanda- KN: Saint Kitts and Nevis- LC: Saint Lucia- VC: Saint Vincent and the Grenadines- WS: Samoa- SM: San Marino- ST: Sao Tome and Principe- SA: Saudi Arabia- SN: Senegal- RS: Serbia- SC: Seychelles- SL: Sierra Leone- SG: Singapore- SK: Slovakia- SI: Slovenia- SB: Solomon Islands- SO: Somalia- ZA: South Africa- SS: South Sudan- ES: Spain- LK: Sri Lanka- SD: Sudan- SR: Suriname- SE: Sweden- CH: Switzerland- SY: Syrian Arab Republic- TJ: Tajikistan- TZ: Tanzania, United Republic of- TH: Thailand- TL: Timor-Leste- TG: Togo- TO: Tonga- TT: Trinidad and Tobago- TN: Tunisia- TR: Turkey- TM: Turkmenistan- TV: Tuvalu- UG: Uganda- UA: Ukraine- AE: United Arab Emirates- GB: United Kingdom of Great Britain and Northern Ireland- US: United States of America- UY: Uruguay- UZ: Uzbekistan- VU: Vanuatu- VE: Venezuela (Bolivarian Republic of)- VN: Viet Nam- YE: Yemen- ZM: Zambia- ZW: Zimbabwe\",",
+ "guidance": "A full list of country codes can be found here (alpha-2 column): https://www.iso.org/obp/ui/#search/code/",
"title": "Jurisdiction"
},
"dataController": {
@@ -131,7 +131,10 @@
}
],
"description": "Data Controller means a person/entity who (either alone or jointly or in common with other persons/entities) determines the purposes for which and the way any Data Subject data, specifically personal data or are to be processed.",
- "guidance": "Data Controller means a person/entity who (either alone or jointly or in common with other persons/entities) determines the purposes for which and the way any Data Subject data, specifically personal data or are to be processed.- Notes: For most organisations this will be the same as the publisher of the dataset. If this is not the case, please indicate that there is a different controller.- If there is a different controller please complete the Data Processor attribute to indicate that the publisher is a Processor rather than the data controller.- In some cases, there may be multiple data controllers i.e. GP data. If this is the case please indicate the fact in a free-text field and describe the data sharing arrangement or a link to it, so that this can be understood by research users.- Example: NHS DIGITAL',",
+ "examples": [
+ "NHS England"
+ ],
+ "guidance": "Data Controller means a person/entity who (either alone or jointly or in common with other persons/entities) determines the purposes for which and the way any Data Subject data, specifically personal data or are to be processed.- Notes: For most organisations this will be the same as the Data Custodian of the dataset. If this is not the case, please indicate that there is a different controller.- If there is a different controller please complete the Data Processor attribute to indicate if the Data Custodian is a Processor rather than the Data Controller.- In some cases, there may be multiple Data Controllers i.e. GP data. If this is the case, please indicate the fact in a free-text field and describe the data sharing arrangement or a link to it, so that this can be understood by research users.- Example: NHS England'",
"title": "Data Controller"
},
"dataProcessor": {
@@ -145,7 +148,11 @@
],
"default": null,
"description": "A Data Processor, in relation to any Data Subject data, specifically personal data, means any person/entity (other than an employee of the data controller) who processes the data on behalf of the data controller.",
- "guidance": "A Data Processor, in relation to any Data Subject data, specifically personal data, means any person/entity (other than an employee of the data controller) who processes the data on behalf of the data controller.- Notes: Required to complete if the Publisher is the Data Processor rather than the data controller.- If the Publisher is also the Data Controller please provide \u201cNot Applicable\u201d.- Examples:- Not Applicable- SAIL',",
+ "examples": [
+ "Not Applicable",
+ "SAIL"
+ ],
+ "guidance": "A Data Processor, in relation to any Data Subject data, specifically personal data, means any person/entity (other than an employee of the data controller) who processes the data on behalf of the data controller.- Notes: Required to complete if the Data Custodian is the Data Processor rather than the Data Controller.- If the Publisher is also the Data Controller please provide \u201cNot Applicable\u201d.- Examples: Not Applicable, SAIL",
"title": "Data Processor"
}
},
@@ -304,11 +311,11 @@
}
],
"default": null,
- "description": "The geographical area covered by the dataset. It is recommended that links are to entries in a well-maintained gazetteer such as https://www.geonames.org/ or https://what3words.com/daring.lion.race.",
+ "description": "The geographical area covered by the dataset. It is recommended that links are to entries in one of the recommended standards:- For locations in the UK: ONS standards- For locations in other countries: ISO 3166-1 & ISO 3166-2",
"examples": [
"https://www.geonames.org/2635167/united-kingdom-of-great-britain-and-northern-ireland.html"
],
- "guidance": "'- The geographical area covered by the dataset.- Please provide a valid location.- For locations in the UK, this location should conform to ONS standards.- For locations in other countries we use ISO 3166-1 & ISO 3166-2.',",
+ "guidance": "The geographical area covered by the dataset.- Please provide a valid location.- For locations in the UK, this location should conform to ONS standards.- For locations in other countries we use ISO 3166-1 & ISO 3166-2.",
"title": "Geographic coverage"
},
"typicalAgeRangeMin": {
@@ -356,13 +363,16 @@
],
"default": null,
"description": "The URL where a Researcher can learn more about the completeness of the dataset.",
- "guidance": "If your organisation has a publicly available site which contains information on the completeness of a dataset, add that URL here.- Example: https://bhfdatasciencecentre.org/dashboard/'",
+ "examples": [
+ "https://bhfdatasciencecentre.org/dashboard/"
+ ],
+ "guidance": "If your organisation has a publicly available site which contains information on the completeness of a dataset, add that URL here.Example: https://bhfdatasciencecentre.org/dashboard/",
"title": "Dataset coverage/completeness/quality"
},
"materialType": {
"default": "None/not available",
"description": "The type of biospecimen saved from a biological entity.",
- "guidance": "\"Indicate the specimen type, can be several values from the list below: \"\" '- Availability of physical samples associated with the dataset.- If samples are available, please indicate the types of samples that are available.- More than one type may be provided.- If samples are not yet available, please provide \u201cAvailability to be confirmed\u201d.- If samples are not available, then please provide \u201cNot available\u201d.- Not available: Samples associated with the dataset are not available- Bone marrow: Bone marrow samples associated with the data are available- Cancer cell lines: Cancer cell line samples associated with the data are available- CDNA/MRNA: CDNA/MRNA samples associated with the data are available- Core biopsy: Core biopsy samples associated with the data are available- DNA: DNA samples associated with the data are available- Entire body organ: Entire body organ associated with the data are available- Faeces: Faeces samples associated with the data are available- Immortalized cell lines: Immortalized cell line samples associated with the data are available- Isolated pathogen: Isolated pathogen associated with the data are available- MicroRNA: MicroRNA samples associated with the data are available- Peripheral blood cells: Peripheral blood cell samples associated with the data are available- Plasma: Plasma samples associated with the data are available- PM Tissue: PM Tissue samples associated with the data are available- Primary cells: Primary cell samples associated with the data are available- RNA: RNA samples associated with the data are available- Saliva: Saliva samples associated with the data are available- Serum: Serum samples associated with the data are available- Swabs: Swab samples associated with the data are available- Tissue: Tissue samples associated with the data are available - Urine: Urine samples associated with the data are available- Whole blood: Whole blood samples associated with the data are available- Availability to be confirmed: Availability of samples is currently being confirmed- Other: Other types of sample available',\"\"\"",
+ "guidance": "Indicate the specimen type, can be several values from the list below:- Availability of physical samples associated with the dataset.- If samples are available, please indicate the types of samples that are available.- More than one type may be provided.- If samples are not yet available, please provide \u201cAvailability to be confirmed\u201d.- If samples are not available, then please provide \u201cNot available\u201d.- Not available: Samples associated with the dataset are not available.- Bone marrow: Bone marrow samples associated with the data are available.- Cancer cell lines: Cancer cell line samples associated with the data are available.- CDNA/MRNA: CDNA/MRNA samples associated with the data are available.- Core biopsy: Core biopsy samples associated with the data are available.- DNA: DNA samples associated with the data are available.- Entire body organ: Entire body organ associated with the data are available.- Faeces: Faeces samples associated with the data are available.- Immortalized cell lines: Immortalized cell line samples associated with the data are available.- Isolated pathogen: Isolated pathogen associated with the data are available.- MicroRNA: MicroRNA samples associated with the data are available.- Peripheral blood cells: Peripheral blood cell samples associated with the data are available.- Plasma: Plasma samples associated with the data are available.- PM Tissue: PM Tissue samples associated with the data are available.- Primary cells: Primary cell samples associated with the data are available.- RNA: RNA samples associated with the data are available.- Saliva: Saliva samples associated with the data are available.- Serum: Serum samples associated with the data are available.- Swabs: Swab samples associated with the data are available.- Tissue: Tissue samples associated with the data are available.- Urine: Urine samples associated with the data are available.- Whole blood: Whole blood samples associated with the data are available.- Availability to be confirmed: Availability of samples is currently being confirmed.- Other: Other types of sample available.",
"items": {
"$ref": "#/$defs/MaterialTypeCategoriesV2"
},
@@ -379,8 +389,8 @@
}
],
"default": "UNKNOWN",
- "description": "If known, what is the typical time span that a patient appears in the dataset (follow up period).",
- "guidance": "If known, please indicate the typical time span that a patient appears in the dataset (follow up period).- 0 - 6 MONTHS: Data typically available for a patient over a 0-6 month period- 6 - 12 MONTHS: Data typically available for a patient over a 6-12 month period- 1 - 10 YEARS: Data typically available for a patient over a 1-10 year period- > 10 YEARS: Data typically available for a patient for over a 10 year period- UNKNOWN: Timespan is Unknown- OTHER: Data available for a patient over another time period ',",
+ "description": "If known, what is the typical time span that a patient appears in the dataset (follow up period). In a prospective cohort study, after baseline information is collected, participants are followed \u201clongitudinally\u201d i.e. new information is collected about them for a period of time afterward. This is known as the \u201cfollow up period\u201d. What is the typical time span of follow up, e.g. 1 year, 5 years? If there are multiple cohorts in the dataset with varying follow up periods, please provide the longest follow up period.",
+ "guidance": "If known, please indicate the typical time span that a patient appears in the dataset (follow up period).-0 - 6 MONTHS: Data typically available for a patient over a 0-6 month period.-6 - 12 MONTHS: Data typically available for a patient over a 6-12 month period.-1 - 10 YEARS: Data typically available for a patient over a 1-10 year period.-> 10 YEARS: Data typically available for a patient for over a 10 year period.-CONTINUOUS: .......... -UNKNOWN: Timespan is Unknown.-OTHER: Data available for a patient over another time period.",
"title": "Follow-up"
},
"pathway": {
@@ -394,7 +404,7 @@
],
"default": null,
"description": "Please indicate if the dataset is representative of the patient pathway and any limitations the dataset may have with respect to pathway coverage. This could include if the dataset is from a single speciality or area, a single tier of care, linked across two tiers (e.g. primary and secondary care), or an integrated care record covering the whole patient pathway.",
- "guidance": "Please indicate if the dataset is representative of the patient pathway and any limitations the dataset may have with respect to pathway coverage.- This could include if the dataset is from a single speciality or area, a single tier of care, linked across two tiers (e.g. primary and secondary care), or an integrated care record covering the whole patient pathway.',",
+ "guidance": "Please indicate if the dataset is representative of the patient pathway and any limitations the dataset may have with respect to pathway coverage.- This could include if the dataset is from a single speciality or area, a single tier of care, linked across two tiers (e.g. primary and secondary care), or an integrated care record covering the whole patient pathway.",
"title": "Patient pathway description"
},
"gender": {
@@ -771,8 +781,8 @@
}
],
"default": null,
- "description": "A free-text description of the dataset. Gateway Feature: Keywords and text may be extracted out of the description and index for search.",
- "guidance": "An HTML account of the data that provides context and scope of the data, limited to 3000 characters, and/or a resolvable URL that describes the dataset.- Additional information can be recorded and included using media.',",
+ "description": "A free-text description of the dataset.A URL can also be provided as the description of the dataset.Gateway Feature: Keywords and text may be extracted out of the description and index for search.",
+ "guidance": "An HTML account of the data that provides context and scope of the data, limited to 3000 characters, and/or a resolvable URL that describes the dataset.- Additional information can be recorded and included using media.",
"title": "Description"
},
"associatedMedia": {
@@ -800,9 +810,9 @@
"default": null,
"description": "Please provide any media associated with the Gateway Organisation using a valid URI for the content. This is an opportunity to provide additional context that could be useful for researchers wanting to understand more about the dataset and its relevance to their research question. The following formats will be accepted .jpg, .png or .svg, .pdf, .xslx or .docx. Note: media asset can be hosted by the organisation or uploaded using the onboarding portal.",
"examples": [
- "PDF Document that describes study protocol"
+ "PDF document that describes study protocol - https://link.to/document.pdf"
],
- "guidance": "Please provide any media associated with the Gateway Organisation using a valid URL for the content.- This is an opportunity to provide additional context that could be useful for researchers wanting to understand more about the dataset and its relevance to their research question.- Note: media assets can be hosted by the organisation or uploaded using the onboarding portal.- Example: This could be a link to a PDF Document that describes methodology or further detail about the datasets, or a graph or chart that provides further context about the dataset.',",
+ "guidance": "Please provide any media associated with the Gateway Organisation using a valid URL for the content.- This is an opportunity to provide additional context that could be useful for researchers wanting to understand more about the dataset and its relevance to their research question.- Note: media assets can be hosted by the organisation or uploaded using the onboarding portal.Example: This could be a link to a PDF Document that describes methodology or further detail about the datasets, or a graph or chart that provides further context about the dataset.- If you are providing multiple links for associated media, we recommend that you separate these with a comma.",
"title": "Associated media"
},
"inPipeline": {
@@ -816,7 +826,7 @@
],
"default": "Not available",
"description": "Indicate whether this dataset is currently available for Researchers to request access.",
- "guidance": "This metadata field is only relevant to the NHS SDE Network datasets. If a dataset is in development and not yet available for Researchers to apply for access, select 'Not available'. If Researchers can currently apply for access to the dataset, select 'Available'.",
+ "guidance": "If a dataset is being prepared for sharing but not yet ready and available for researchers to apply for access, select 'Not available'. If Researchers can currently apply for access to the dataset, select 'Available'.",
"title": "Dataset pipeline status"
}
},
@@ -870,7 +880,7 @@
}
],
"default": null,
- "description": "If applicable, please provide DOIs or links to datasets from which data in this dataset can be derived or calculated.",
+ "description": "If applicable, please provide DOIs or links to datasets from which data in this dataset has been derived or calculated from.",
"title": "Derived from"
},
"isPartOf": {
@@ -887,6 +897,9 @@
],
"default": null,
"description": "This relationship indicates that the dataset is a component or subset of a broader collection of related datasets. For example, clinical trial data for a specific drug may be part of a larger database of pharmaceutical research data. Complete only if the dataset is part of a group or family of datasets i.e. Hospital Episode Statistics has several constituents. If your dataset is not part of a group, please enter \u201cNOT APPLICABLE\u201d Example: Hospital Episodes Statistics datasets (A&E, APC, OP, AC MSDS).",
+ "examples": [
+ "Hospital Episodes Statistics datasets (A&E, APC, OP, AC MSDS)"
+ ],
"title": "Is part of"
},
"linkableDatasets": {
@@ -935,7 +948,7 @@
],
"default": null,
"description": "Please provide link to any active projects that are using the dataset.",
- "guidance": "Please provide the website address(es) which document information related to active projects utilising the dataset.Please split your existing list of citations into separate fields.To add multiple entries, please click on '+' symbol to enter each separate website.Example: https://dataloch.org/insights/projects-delivered/data-driven-innovation-multi-morbidity-report-partner-gps",
+ "guidance": "Please provide the website address(es) which document information related to active projects utilising the dataset.- Please split your existing list of citations into separate fields.- To add multiple entries, please click on '+' symbol to enter each separate website.- Example: https://dataloch.org/insights/projects-delivered/data-driven-innovation-multi-morbidity-report-partner-gps",
"title": "Investigations"
},
"tools": {
@@ -952,7 +965,7 @@
],
"default": null,
"description": "Please provide the URL of any analysis tools or models that have been created for this dataset and are available for further use. Multiple tools may be provided. Note: We encourage users to adopt a model along the lines of https://www.ga4gh.org/news/tool-registry-service-api-enabling-an-interoperable-library-of-genomics-analysis-tools/",
- "guidance": "\"- Please provide the URL of any analysis tools or models that have been created for this dataset and are available for further use. - Multiple tools may be provided. - Note: We encourage users to adopt a model along the lines of https://www.ga4gh.org/news/tool-registry-service-api-enabling-an-interoperable-library-of-genomics-analysis-tools/\"",
+ "guidance": "Please provide the URL of any analysis tools or models that have been created for this dataset and are available for further use.- Multiple tools may be provided.- Note: We encourage users to adopt a model along the lines of https://www.ga4gh.org/news/tool-registry-service-api-enabling-an-interoperable-library-of-genomics-analysis-tools/",
"title": "Tools"
},
"publicationAboutDataset": {
@@ -969,7 +982,10 @@
],
"default": null,
"description": "DOIs for publications which describe the dataset.",
- "guidance": "Please provide the DOIs for publications which describe the dataset.Please split your existing list of citations into separate fields.To add multiple entries, please click on '+' symbol to enter each separate citation.Example: https://doi.org/10.1093/ije/dyab028",
+ "examples": [
+ "https://doi.org/10.1093/ije/dyab028"
+ ],
+ "guidance": "Please provide the DOIs for publications which describe the dataset.- Please split your existing list of citations into separate fields.- To add multiple entries, please click on '+' symbol to enter each separate citation.- Example: https://doi.org/10.1093/ije/dyab028",
"title": "Publication about the dataset"
},
"publicationUsingDataset": {
@@ -986,7 +1002,10 @@
],
"default": null,
"description": "DOIs for publications which use the dataset for analysis.",
- "guidance": "Please provide the DOIs for publications which have used the dataset in their analysis.Please split your existing list of citations into separate fields.To add multiple entries, please click on '+' symbol to enter each separate citation.Example: https://doi.org/10.1001/jamapediatrics.2016.3633.",
+ "examples": [
+ "https://doi.org/10.1001/jamapediatrics.2016.3633"
+ ],
+ "guidance": "Please provide the DOIs for publications which have used the dataset in their analysis.- Please split your existing list of citations into separate fields.- To add multiple entries, please click on '+' symbol to enter each separate citation.- Example: https://doi.org/10.1001/jamapediatrics.2016.3633",
"title": "Publication using the dataset"
}
},
@@ -1016,7 +1035,7 @@
"properties": {
"vocabularyEncodingScheme": {
"description": "List any relevant terminologies / ontologies / controlled vocabularies, such as ICD 10 Codes, NHS Data Dictionary National Codes or SNOMED CT International, that are being used by the dataset. If the controlled vocabularies are local standards, please make that explicit. If you are using a standard that has not been included in the list, please use \u201cother\u201d and contact support desk to ask for an addition. Notes: More than one vocabulary may be provided.",
- "guidance": "'- List any relevant terminologies / ontologies / controlled vocabularies, such as ICD 10 Codes, NHS Data Dictionary National Codes or SNOMED CT International, that are being used by the dataset.- If the controlled vocabularies are local standards, please make that explicit. If you are using a standard that has not been included in the list, please use \u201cother\u201d and contact support desk to ask for an addition.- Notes: More than one vocabulary may be provided.- Local: Local Coding Standard- OPCS4: https://www.datadictionary.nhs.uk/web_site_content/supporting_information/clinical_coding/opcs_classification_of_interventions_and_procedures.asp- READ: https://digital.nhs.uk/services/terminology-and-classifications/read-codes- SNOMED CT: http://www.snomed.org/- SNOMED RT: https://confluence.ihtsdotools.org/display/DOCGLOSS/SNOMED+RT- DM+D: https://digital.nhs.uk/data-and-information/information-standards/information-standards-and-data-collections-including-extractions/publications-and-notifications/standards-and-collections/scci0052-dictionary-of-medicines-and-devices-dm-d- NHS National Codes: https://www.datadictionary.nhs.uk/- ODS: https://digital.nhs.uk/services/organisation-data-service- LOINC: https://loinc.org/- ICD10: https://www.who.int/classifications/icd/icdonlineversions/en/- ICD10CM: https://www.cdc.gov/nchs/icd/icd10cm.htm- ICD10PCS: https://ec.europa.eu/eip/ageing/standards/healthcare/e-health/icd-10-pcs_en- ICD9CM: https://www.cdc.gov/nchs/icd/icd9cm.htm- ICD9: https://www.cdc.gov/nchs/icd/icd9.htm- ICDO3: https://www.who.int/classifications/icd/adaptations/oncology/en/- AMT: https://www.digitalhealth.gov.au/about-the-agency/tenders-and-offers/community-pharmacy-software-industry-partnership-offer/Webinar%20-%20Australian%20Medicines%20Terminology%20(AMT)%20and%20Implementation%20Options%2001032017.pdf- APC: https://www.acep.org/administration/reimbursement/reimbursement-faqs/apc-ambulatory-payment-classifications-faq/- ATC: https://www.whocc.no/atc_ddd_index/- CIEL: https://github.com/OpenConceptLab/ocl_web/wiki/CIEL- HPO: https://hpo.jax.org/app/- CPT4: https://www.cms.gov/Regulations-and-Guidance/Legislation/CLIA/Downloads/SubjecttoCLIA.pdf- DPD: https://health-products.canada.ca/dpd-bdpp/index-eng.jsp- DRG: http://www.euro.who.int/__data/assets/pdf_file/0004/162265/e96538.pdf- HEMONC: https://hemonc.org/wiki/Main_Page- JMDC: https://www.jmdc.co.jp/en/- KCD7: https://forums.ohdsi.org/t/adding-kcd7-code-korean-icd-10-to-the-omop-vocabulary/7576- MULTUM: https://www.cerner.com/solutions/drug-database- NAACCR: https://www.naaccr.org/- NDC: https://www.fda.gov/drugs/drug-approvals-and-databases/national-drug-code-directory- NDFRT <:https://www.nlm.nih.gov/research/umls/sourcereleasedocs/current/NDFRT/index.html>- OXMIS: https://oxrisk.com/oxmis/- RXNORM: https://www.nlm.nih.gov/research/umls/rxnorm/index.html- RXNORM EXTENSION: https://www.nlm.nih.gov/research/umls/rxnorm/index.html- SPL: https://www.fda.gov/industry/fda-resources-data-standards/structured-product-labeling-resources- Other: Please indicate if there is another standard that you are using. This will trigger a support ticket where you can request the addition of the terminology to the HOP.- NHS Scotland National Codes: https://www.ndc.scot.nhs.uk/Data-Dictionary/- NHS Wales National Codes: http://www.datadictionary.wales.nhs.uk/',",
+ "guidance": "List any relevant terminologies / ontologies / controlled vocabularies, such as ICD 10 Codes, NHS Data Dictionary National Codes or SNOMED CT International, that are being used by the dataset.- If the controlled vocabularies are local standards, please make that explicit. If you are using a standard that has not been included in the list, please use \u201cother\u201d and contact support desk to ask for an addition.- Notes: More than one vocabulary may be provided.- Local: Local Coding Standard.- OPCS4: https://www.datadictionary.nhs.uk/web_site_content/supporting_information/clinical_coding/opcs_classification_of_interventions_and_procedures.asp.- READ: https://digital.nhs.uk/services/terminology-and-classifications/read-codes.- SNOMED CT: http://www.snomed.org/.- SNOMED RT: https://confluence.ihtsdotools.org/display/DOCGLOSS/SNOMED+RT.- DM+D: https://digital.nhs.uk/data-and-information/information-standards/information-standards-and-data-collections-including-extractions/publications-and-notifications/standards-and-collections/scci0052-dictionary-of-medicines-and-devices-dm-d.- NHS National Codes: https://www.datadictionary.nhs.uk/.- ODS: https://digital.nhs.uk/services/organisation-data-service.- LOINC: https://loinc.org/.- ICD10: https://www.who.int/classifications/icd/icdonlineversions/en/.- ICD10CM: https://www.cdc.gov/nchs/icd/icd10cm.htm.- ICD10PCS: https://ec.europa.eu/eip/ageing/standards/healthcare/e-health/icd-10-pcs_en.- ICD9CM: https://www.cdc.gov/nchs/icd/icd9cm.htm.- ICD9: https://www.cdc.gov/nchs/icd/icd9.htm.- ICDO3: https://www.who.int/classifications/icd/adaptations/oncology/en/.- AMT: https://www.digitalhealth.gov.au/about-the-agency/tenders-and-offers/community-pharmacy-software-industry-partnership-offer/Webinar%20-%20Australian%20Medicines%20Terminology%20(AMT)%20and%20Implementation%20Options%2001032017.pdf.- APC: https://www.acep.org/administration/reimbursement/reimbursement-faqs/apc-ambulatory-payment-classifications-faq/.- ATC: https://www.whocc.no/atc_ddd_index/.- CIEL: https://github.com/OpenConceptLab/ocl_web/wiki/CIEL.- HPO: https://hpo.jax.org/app/.- CPT4: https://www.cms.gov/Regulations-and-Guidance/Legislation/CLIA/Downloads/SubjecttoCLIA.pdf.- DPD: https://health-products.canada.ca/dpd-bdpp/index-eng.jsp.- DRG: http://www.euro.who.int/__data/assets/pdf_file/0004/162265/e96538.pdf.- HEMONC: https://hemonc.org/wiki/Main_Page.- JMDC: https://www.jmdc.co.jp/en/.- KCD7: https://forums.ohdsi.org/t/adding-kcd7-code-korean-icd-10-to-the-omop-vocabulary/7576.- MULTUM: https://www.cerner.com/solutions/drug-database.- NAACCR: https://www.naaccr.org/.- NDC: https://www.fda.gov/drugs/drug-approvals-and-databases/national-drug-code-directory.- NDFRT <:https://www.nlm.nih.gov/research/umls/sourcereleasedocs/current/NDFRT/index.html>.- OXMIS: https://oxrisk.com/oxmis/.- RXNORM: https://www.nlm.nih.gov/research/umls/rxnorm/index.html.- RXNORM EXTENSION: https://www.nlm.nih.gov/research/umls/rxnorm/index.html.- SPL: https://www.fda.gov/industry/fda-resources-data-standards/structured-product-labeling-resources.- Other: Please indicate if there is another standard that you are using. This will trigger a support ticket where you can request the addition of the terminology to the HOP.- NHS Scotland National Codes: https://www.ndc.scot.nhs.uk/Data-Dictionary/.- NHS Wales National Codes: http://www.datadictionary.wales.nhs.uk/",
"items": {
"$ref": "#/$defs/ControlledVocabulary"
},
@@ -1028,7 +1047,7 @@
"examples": [
"LOCAL,NHS DATA DICTIONARY"
],
- "guidance": "'- List standardised data models that the dataset has been stored in or transformed to, such as OMOP or FHIR.- If the data is only available in a local format, please make that explicit. If you are using a standard that has not been included in the list, please use \u201cother\u201d and contact support desk to ask for an addition.- HL7 FHIR: https://www.hl7.org/fhir/- HL7 V2: https://www.hl7.org/implement/standards/product_section.cfm?section=13- HL7 CDA: https://www.hl7.org/implement/standards/product_section.cfm?section=10- HL7 CCOW: https://www.hl7.org/implement/standards/product_section.cfm?section=16- DICOM: https://www.dicomstandard.org/- I2B2: https://www.i2b2.org/- IHE: https://www.ihe.net/resources/profiles/- OMOP: https://www.ohdsi.org/data-standardization/the-common-data-model/- openEHR: https://www.openehr.org/- Sentinel: https://www.sentinelinitiative.org/sentinel/data/distributed-database-common-data-model- PCORnet: https://pcornet.org/data-driven-common-model/- CDISC: https://www.cdisc.org/standards/data-exchange/odm- Local: In-house developed data model- Other: Other standardised data model- NHS Data Dictionary: https://www.datadictionary.nhs.uk/- NHS Scotland Data Dictionary: https://www.ndc.scot.nhs.uk/Data-Dictionary/- NHS Wales Data Dictionary: https://www.datadictionary.wales.nhs.uk/',",
+ "guidance": "List standardised data models that the dataset has been stored in or transformed to, such as OMOP or FHIR.- If the data is only available in a local format, please make that explicit. If you are using a standard that has not been included in the list, please use \u201cother\u201d and contact support desk to ask for an addition.- HL7 FHIR: https://www.hl7.org/fhir/.- HL7 V2: https://www.hl7.org/implement/standards/product_section.cfm?section=13.- HL7 CDA: https://www.hl7.org/implement/standards/product_section.cfm?section=10.- HL7 CCOW: https://www.hl7.org/implement/standards/product_section.cfm?section=16.- DICOM: https://www.dicomstandard.org/.- I2B2: https://www.i2b2.org/.- IHE: https://www.ihe.net/resources/profiles/.- OMOP: https://www.ohdsi.org/data-standardization/the-common-data-model/.- openEHR: https://www.openehr.org/.- Sentinel: https://www.sentinelinitiative.org/sentinel/data/distributed-database-common-data-model.- PCORnet: https://pcornet.org/data-driven-common-model/.- CDISC: https://www.cdisc.org/standards/data-exchange/odm.- Local: In-house developed data model.- Other: Other standardised data model.- NHS Data Dictionary: https://www.datadictionary.nhs.uk/.- NHS Scotland Data Dictionary: https://www.ndc.scot.nhs.uk/Data-Dictionary/.- NHS Wales Data Dictionary: https://www.datadictionary.wales.nhs.uk/.",
"items": {
"$ref": "#/$defs/StandardisedDataModels"
},
@@ -1050,8 +1069,8 @@
"type": "null"
}
],
- "description": "This should list all the languages in which the dataset metadata and underlying data is made available.",
- "guidance": "aa: Afar- ab: Abkhazian- af: Afrikaans- ak: Akan- sq: Albanian- am: Amharic- ar: Arabic- an: Aragonese- hy: Armenian- as: Assamese- av: Avaric- ae: Avestan- ay: Aymara- az: Azerbaijani- ba: Bashkir- bm: Bambara- eu: Basque- be: Belarusian- bn: Bengali- bh: Bihari languages- bi: Bislama- bo: Tibetan- bs: Bosnian- br: Breton- bg: Bulgarian- my: Burmese- ca: Catalan; Valencian- cs: Czech- ch: Chamorro- ce: Chechen- zh: Chinese- cu: Church Slavic; Old Slavonic; Church Slavonic; Old Bulgarian; Old Church Slavonic- cv: Chuvash- kw: Cornish- co: Corsican- cr: Cree- cy: Welsh- cs: Czech- da: Danish- de: German- dv: Divehi; Dhivehi; Maldivian- nl: Dutch; Flemish- dz: Dzongkha- el: Greek, Modern (1453-)- en: English- eo: Esperanto- et: Estonian- eu: Basque- ee: Ewe- fo: Faroese- fa: Persian- fj: Fijian- fi: Finnish- fr: French- fy: Western Frisian- ff: Fulah- ka: Georgian- de: German- gd: Gaelic; Scottish Gaelic- ga: Irish- gl: Galician- gv: Manx- el: Greek, Modern (1453-)- gn: Guarani- gu: Gujarati- ht: Haitian; Haitian Creole- ha: Hausa- ho: Hiri Motu- hr: Croatian- hu: Hungarian- hy: Armenian- ig: Igbo- is: Icelandic- io: Ido- ii: Sichuan Yi; Nuosu- iu: Inuktitut- ie: Interlingue; Occidental- ia: Interlingua (International Auxiliary Language Association)- id: Indonesian- ik: Inupiaq- is: Icelandic- it: Italian- jv: Javanese- ja: Japanese- kl: Kalaallisut; Greenlandic- kn: Kannada- ks: Kashmiri- ka: Georgian- kr: Kanuri- kk: Kazakh- km: Central Khmer- ki: Kikuyu; Gikuyu- rw: Kinyarwanda- ky: Kirghiz; Kyrgyz- kv: Komi- kg: Kongo- ko: Korean- kj: Kuanyama; Kwanyama- ku: Kurdish- lo: Lao- la: Latin- lv: Latvian- li: Limburgan; Limburger; limburgish- ln: Lingala- lt: Lithuanian- lb: Luxembourgish; Letzeburgesch- lu: Luba-Katanga- lg: Ganda- mk: Macedonian- mh: Marshallese- ml: Malayalam- mi: Maori- mr: Marathi- ms: Malay- mk: Macedonian- mg: Malagasy- mt: Maltese- mn: Mongolian- mi: Maori- ms: Malay- my: Burmese- na: Nauru- nv: Navajo; Navaho- nr: Ndebele, South; South Ndebele- nd: Ndebele, North; North Ndebele- ng: Ndonga- ne: Nepali- nl: Dutch; Flemish- nn: Norwegian Nynorsk; Nynorsk, Norwegian- nb: Bokm\u00e5l, Norwegian; Norwegian Bokm\u00e5l- no: Norwegian- ny: Chichewa; Chewa; Nyanja- oc: Occitan (post 1500)- oj: Ojibwa- or: Oriya- om: Oromo- os: Ossetian; Ossetic- pa: Panjabi; Punjabi- fa: Persian- pi: Pali- pl: Polish- pt: Portuguese- ps: Pushto; Pashto- qu: Quechua- rm: Romansh- ro: Romanian; Moldavian; Moldovan- rn: Rundi- ru: Russian- sg: Sango- sa: Sanskrit- si: Sinhala; Sinhalese- sk: Slovak- sl: Slovenian- se: Northern Sami- sm: Samoan- sn: Shona- sd: Sindhi- so: Somali- st: Sotho, Southern- es: Spanish; Castilian- sq: Albanian- sc: Sardinian- sr: Serbian- ss: Swati- su: Sundanese- sw: Swahili- sv: Swedish- ty: Tahitian- ta: Tamil- tt: Tatar- te: Telugu- tg: Tajik- tl: Tagalog- th: Thai- bo: Tibetan- ti: Tigrinya- to: Tonga (Tonga Islands)- tn: Tswana- ts: Tsonga- tk: Turkmen- tr: Turkish- tw: Twi- ug: Uighur; Uyghur- uk: Ukrainian- ur: Urdu- uz: Uzbek- ve: Venda- vi: Vietnamese- vo: Volap\u00fck- cy: Welsh- wa: Walloon- wo: Wolof- xh: Xhosa- yi: Yiddish- yo: Yoruba- za: Zhuang; Chuang- zh: Chinese- zu: Zulu',",
+ "description": "This should list all the languages in which the dataset metadata and underlying data is made available complaint with ISO 639.",
+ "guidance": "https://www.iso.org/iso-639-language-code- aa: Afar- ab: Abkhazian- af: Afrikaans- ak: Akan- sq: Albanian- am: Amharic- ar: Arabic- an: Aragonese- hy: Armenian- as: Assamese- av: Avaric- ae: Avestan- ay: Aymara- az: Azerbaijani- ba: Bashkir- bm: Bambara- eu: Basque- be: Belarusian- bn: Bengali- bh: Bihari languages- bi: Bislama- bo: Tibetan- bs: Bosnian- br: Breton- bg: Bulgarian- my: Burmese- ca: Catalan; Valencian- cs: Czech- ch: Chamorro- ce: Chechen- zh: Chinese- cu: Church Slavic; Old Slavonic; Church Slavonic; Old Bulgarian; Old Church Slavonic- cv: Chuvash- kw: Cornish- co: Corsican- cr: Cree- cy: Welsh- cs: Czech- da: Danish- de: German- dv: Divehi; Dhivehi; Maldivian- nl: Dutch; Flemish- dz: Dzongkha- el: Greek, Modern (1453-)- en: English- eo: Esperanto- et: Estonian- eu: Basque- ee: Ewe- fo: Faroese- fa: Persian- fj: Fijian- fi: Finnish- fr: French- fy: Western Frisian- ff: Fulah- ka: Georgian- de: German- gd: Gaelic; Scottish Gaelic- ga: Irish- gl: Galician- gv: Manx- el: Greek, Modern (1453-)- gn: Guarani- gu: Gujarati- ht: Haitian; Haitian Creole- ha: Hausa- ho: Hiri Motu- hr: Croatian- hu: Hungarian- hy: Armenian- ig: Igbo- is: Icelandic- io: Ido- ii: Sichuan Yi; Nuosu- iu: Inuktitut- ie: Interlingue; Occidental- ia: Interlingua (International Auxiliary Language Association)- id: Indonesian- ik: Inupiaq- is: Icelandic- it: Italian- jv: Javanese- ja: Japanese- kl: Kalaallisut; Greenlandic- kn: Kannada- ks: Kashmiri- ka: Georgian- kr: Kanuri- kk: Kazakh- km: Central Khmer- ki: Kikuyu; Gikuyu- rw: Kinyarwanda- ky: Kirghiz; Kyrgyz- kv: Komi- kg: Kongo- ko: Korean- kj: Kuanyama; Kwanyama- ku: Kurdish- lo: Lao- la: Latin- lv: Latvian- li: Limburgan; Limburger; limburgish- ln: Lingala- lt: Lithuanian- lb: Luxembourgish; Letzeburgesch- lu: Luba-Katanga- lg: Ganda- mk: Macedonian- mh: Marshallese- ml: Malayalam- mi: Maori- mr: Marathi- ms: Malay- mk: Macedonian- mg: Malagasy- mt: Maltese- mn: Mongolian- mi: Maori- ms: Malay- my: Burmese- na: Nauru- nv: Navajo; Navaho- nr: Ndebele, South; South Ndebele- nd: Ndebele, North; North Ndebele- ng: Ndonga- ne: Nepali- nl: Dutch; Flemish- nn: Norwegian Nynorsk; Nynorsk, Norwegian- nb: Bokm\u00e5l, Norwegian; Norwegian Bokm\u00e5l- no: Norwegian- ny: Chichewa; Chewa; Nyanja- oc: Occitan (post 1500)- oj: Ojibwa- or: Oriya- om: Oromo- os: Ossetian; Ossetic- pa: Panjabi; Punjabi- fa: Persian- pi: Pali- pl: Polish- pt: Portuguese- ps: Pushto; Pashto- qu: Quechua- rm: Romansh- ro: Romanian; Moldavian; Moldovan- rn: Rundi- ru: Russian- sg: Sango- sa: Sanskrit- si: Sinhala; Sinhalese- sk: Slovak- sl: Slovenian- se: Northern Sami- sm: Samoan- sn: Shona- sd: Sindhi- so: Somali- st: Sotho, Southern- es: Spanish; Castilian- sq: Albanian- sc: Sardinian- sr: Serbian- ss: Swati- su: Sundanese- sw: Swahili- sv: Swedish- ty: Tahitian- ta: Tamil- tt: Tatar- te: Telugu- tg: Tajik- tl: Tagalog- th: Thai- bo: Tibetan- ti: Tigrinya- to: Tonga (Tonga Islands)- tn: Tswana- ts: Tsonga- tk: Turkmen- tr: Turkish- tw: Twi- ug: Uighur; Uyghur- uk: Ukrainian- ur: Urdu- uz: Uzbek- ve: Venda- vi: Vietnamese- vo: Volap\u00fck- cy: Welsh- wa: Walloon- wo: Wolof- xh: Xhosa- yi: Yiddish- yo: Yoruba- za: Zhuang; Chuang- zh: Chinese- zu: Zulu",
"title": "Language"
},
"format": {
@@ -1070,7 +1089,13 @@
}
],
"description": "If multiple formats are available please specify. See application, audio, image, message, model, multipart, text, video, https://www.iana.org/assignments/media-types/media-types.xhtml Note: If your file format is not included in the current list of formats, please indicate other. If you are using the HOP you will be directed to a service desk page where you can request your additional format. If not please go to: https://metadata.atlassian.net/servicedesk/customer/portal/4 to request your format.",
- "guidance": "'- If multiple formats are available, please specify. See application, audio, image, message, model, multipart, text, video, https://www.iana.org/assignments/media-types/media-types.xhtml- Please enter one format type at a time and click Add New Field to add further keywords.- Note: If your file format is not included in the current list of formats, please indicate other.- If you are using the HOP, you will be directed to a service desk page where you can request your additional format.- If not, please go to: https://metadata.atlassian.net/servicedesk/customer/portal/4 to request your format.- Example: text/tab-separated-values, application/sql, text/csv, image/diacom-rle',",
+ "examples": [
+ "text/tab-separated-values",
+ "application/sql",
+ "text/csv",
+ "image/diacom-rle"
+ ],
+ "guidance": "If multiple formats are available, please specify. See application, audio, image, message, model, multipart, text, video, https://www.iana.org/assignments/media-types/media-types.xhtml.- Please enter one format type at a time and click Add New Field to add further keywords.- Note: If your file format is not included in the current list of formats, please indicate other.- Example: text/tab-separated-values, application/sql, text/csv, image/diacom-rle",
"title": "Format"
}
},
@@ -1367,16 +1392,16 @@
"$ref": "#/$defs/StatisticalPopulationConstrainedV2"
}
],
- "description": "Please select one of the following statistical populations for you observation.",
+ "description": "Please select one of the following broad notes for your measured observation. Indicating whether the measured property is a recording of unique persons, events, findings or scans per modality.",
"examples": [
- "PERSONS"
+ "Persons"
],
- "guidance": "Persons: Unique persons recorded in the dataset- Events: Unique events such as procedures and prescriptions within the dataset - Findings: Unique findings included in the dataset such as diagnoses, test '-Number of scans per modality: Unique scans for a specified modality (e.g. 12 x-rays)",
+ "guidance": "Persons: Unique persons recorded in the dataset- Events: Unique events such as procedures and prescriptions within the dataset-Findings: Unique findings included in the dataset such as diagnoses'-Number of scans per modality: Unique scans for a specified imaging method modality (e.g. 12 x-rays)",
"title": "Dataset volume measure"
},
"measuredValue": {
- "description": "Please provide the population size associated with the population type the dataset i.e. 1000 people in a study, or 87 images (MRI) of Knee Usage Note: Used with Statistical Population, which specifies the type of the population in the dataset.",
- "guidance": "Please provide the dataset size associated with the volume measure type.- You can add more than one volume measure by clicking the '+' symbol. Example: 1000 people in a study, or 87 images (MRI) of Knee.",
+ "description": "An integer value size of the measured property, such as \u20181000\u2019 for 1000 people in the study or \u201887\u2019 for 87 MRI scans in the dataset.",
+ "guidance": "An integer value size of the measured property, such as \u20181000\u2019 for 1000 people in the study or \u201887\u2019 for 87 MRI scans in the dataset.",
"title": "Measured value",
"type": "integer"
},
@@ -1390,8 +1415,8 @@
}
],
"default": null,
- "description": "If SNOMED CT term does not provide sufficient detail, please provide a description that disambiguates the population type.",
- "guidance": "If SNOMED CT term does not provide sufficient detail, please provide a description that disambiguates the dataset volume measure type.",
+ "description": "If required, please provide additional details that help distinguish between similar measured properties within your dataset, for example this is useful when SNOMED CT terms do not provide sufficient detail to distinguish between parts of the dataset population. Limited to 500 characters.",
+ "guidance": "If required please provide additional details that help distinguish between similar measured properties within your dataset, for example this is useful when SNOMED CT terms do not provide sufficient detail to distinguish between parts of the dataset population.",
"title": "Disambiguating description"
},
"observationDate": {
@@ -1405,8 +1430,8 @@
"type": "string"
}
],
- "description": "Please provide the date that the observation was made. Some datasets may be continuously updated and the number of records will change regularly, so the observation date provides users with the date that the analysis or query was run to generate the particular observation. Multiple observations can be made i.e. an observation of cumulative COVID positive cases by specimen on the 1/1/2021 could be 2M. On the 8/1/2021 a new observation could be 2.1M. Users can add multiple observations.",
- "guidance": "Please provide the date that the observation was made. Some datasets may be continuously updated and the number of records will change regularly, so the observation date provides users with the date that the analysis or query was run to generate the particular observation. Multiple observations can be made i.e. an observation of cumulative COVID positive cases by specimen on the 1/1/2021 could be 2M. On the 8/1/2021 a new observation could be 2.1M.",
+ "description": "Provide the date, or datetime that the observation was made. Multiple observations of the same property can be provided, for example an observation of cumulative COVID positive cases by specimen on the 1/1/2021 with a measuredValue of 2000000, and a second observation entry on 8/2/2021 recording a measuredValue of as 3100000.",
+ "guidance": "Provide the date, or datetime that the observation was made. Multiple observations of the same property can be provided, for example an observation of cumulative COVID positive cases by specimen on the 1/1/2021 with a measuredValue of 2000000, and a second observation entry on 8/2/2021 recording a measuredValue of as 3100000.",
"title": "Observation date"
},
"measuredProperty": {
@@ -1415,8 +1440,8 @@
"$ref": "#/$defs/MeasuredProperty"
}
],
- "description": "Descibe the property used to measure each observation.",
- "guidance": "The default value is 'COUNT' (e.g. the count of persons who are in the cohort)",
+ "description": "Descriptive term for the observation property measured. For example, people, procedures, x-rays, or diagnosis of type 1 diabetes. This could also be a specific SNOMED CT term.",
+ "guidance": "Descriptive term for the observation property measured.",
"title": "Measured property"
}
},
@@ -1449,7 +1474,7 @@
],
"default": null,
"description": "Please provide a Research Organization Registry (ROR) identifier (see https://ror.org/) for your organisation.",
- "guidance": "Example: https://ror.org/053fq8t95 If your organisation does not have a ROR identifier please use the \u201csuggest and institute\u201d function here: https://docs.google.com/forms/d/e/1FAIpQLSdJYaMTCwS7muuTa-B_CnAtCSkKzt19lkirAKG4u7umH9Nosg/viewform",
+ "guidance": "Example: https://ror.org/053fq8t95If your organisation does not have a ROR identifier please use the \u201csuggest and institute\u201d function here: https://docs.google.com/forms/d/e/1FAIpQLSdJYaMTCwS7muuTa-B_CnAtCSkKzt19lkirAKG4u7umH9Nosg/viewform",
"title": "identifier"
},
"name": {
@@ -1541,7 +1566,7 @@
],
"default": null,
"description": "Please indicate the purpose(s) that the dataset was collected.",
- "guidance": "-Research cohort: Data collected for a defined group of people.- Study: Data collected for a specific research study.- Disease registry: Data collected as part of a disease registry.- Trial: Data collected for as part of a clinical trial.- Care: Data collected as part of routine clinical care.- Audit: Data collected as part of an audit programme- Administrative: Data collected for administrative and management information purposes- Financial: Data collected either for payments or for billing- Other: Data collected for other purpose',",
+ "guidance": "Research cohort: Data collected for a defined group of people.- Study: Data collected for a specific research study.- Disease registry: Data collected as part of a disease registry.- Trial: Data collected for as part of a clinical trial.- Care: Data collected as part of routine clinical care.- Audit: Data collected as part of an audit programme.- Administrative: Data collected for administrative and management information purposes.- Financial: Data collected either for payments or for billing.- Statutory: ...........- Other: Data collected for other purpose.",
"title": "Purpose of dataset collection"
},
"datasetType": {
@@ -1551,7 +1576,7 @@
}
],
"description": "The topic areas to which the dataset content relates.",
- "guidance": "\"Types include those liste below. Datasets can have more than one type associated. \u2022 Health and disease - Includes any data related to mental health, cardiovascular, cancer, rare diseases, metabolic and endocrine, neurological, reproductive, maternity and neonatology, respiratory, immunity, musculoskeletal, vision, renal and urogenital, oral and gastrointestinal, cognitive function or hearing. \u2022 Treatments/Interventions - Includes any data related to treatment or interventions related to vaccines or which are preventative or therapeutic in nature. \u2022 Measurements/Tests - Includes any data related to laboratory or other diagnostics. \u2022 Imaging types - Includes any data related to CT, MRI, PET, x-ray, ultrasound or pathology imaging. \u2022 Imaging area of the body - Indicates whether the dataset relates to head, chest, arm abdomen or leg imaging. \u2022 Omics - Includes any data related to proteomics, transcriptomics, epigenomics, metabolomics, multiomics, metagenomics or genomics. \u2022 Socioeconomic - Includes any data related to education, crime and justice, ethnicity, housing, labour, ageing, economics, marital status, social support, deprivation, religion, occupation, finances or family circumstances. \u2022 Lifestyle - Includes any data related to smoking, physical activity, dietary habits or alcohol. \u2022 Registry - Includes any data related to disease registries for research, national disease registries, audits, or birth and deaths records. \u2022 Environment and energy - Includes any data related to the monitoring or study of environmental or energy factors or events. \u2022 Information and communication - Includes any data related to the study or application of information and communication. \u2022 Politics - Includes any data related to political views, activities, voting, etc.\"",
+ "guidance": "Types include those listed below. Datasets can have more than one type associated.- Health and disease: Includes any data related to mental health, cardiovascular, cancer, rare diseases, metabolic and endocrine, neurological, reproductive, maternity and neonatology, respiratory, immunity, musculoskeletal, vision, renal and urogenital, oral and gastrointestinal, cognitive function or hearing.- Treatments/Interventions: Includes any data related to treatment or interventions related to vaccines or which are preventative or therapeutic in nature.- Measurements/Tests: Includes any data related to laboratory or other diagnostics.- Imaging types: Includes any data related to CT, MRI, PET, x-ray, ultrasound or pathology imaging.- Imaging area of the body: Indicates whether the dataset relates to head, chest, arm abdomen or leg imaging.- Omics: Includes any data related to proteomics, transcriptomics, epigenomics, metabolomics, multiomics, metagenomics or genomics.- Socioeconomic: Includes any data related to education, crime and justice, ethnicity, housing, labour, ageing, economics, marital status, social support, deprivation, religion, occupation, finances or family circumstances.- Lifestyle: Includes any data related to smoking, physical activity, dietary habits or alcohol.- Registry: Includes any data related to disease registries for research, national disease registries, audits, or birth and deaths records.- Environment and energy: Includes any data related to the monitoring or study of environmental or energy factors or events.- Information and communication: Includes any data related to the study or application of information and communication.- Politics: Includes any data related to political views, activities, voting, etc.",
"title": "Dataset type"
},
"datasetSubType": {
@@ -1563,8 +1588,8 @@
"type": "null"
}
],
- "description": "The sub-type of the dataset content.",
- "guidance": "\"Sub-types include those liste below under each data type. Datasets can have more than one sub-type associated. \u2022 Health and disease - Includes any data related to mental health, cardiovascular, cancer, rare diseases, metabolic and endocrine, neurological, reproductive, maternity and neonatology, respiratory, immunity, musculoskeletal, vision, renal and urogenital, oral and gastrointestinal, cognitive function or hearing. \u2022 Treatments/Interventions - Includes any data related to treatment or interventions related to vaccines or which are preventative or therapeutic in nature. \u2022 Measurements/Tests - Includes any data related to laboratory or other diagnostics. \u2022 Imaging types - Includes any data related to CT, MRI, PET, x-ray, ultrasound or pathology imaging. \u2022 Imaging area of the body - Indicates whether the dataset relates to head, chest, arm abdomen or leg imaging. \u2022 Omics - Includes any data related to proteomics, transcriptomics, epigenomics, metabolomics, multiomics, metagenomics or genomics. \u2022 Socioeconomic - Includes any data related to education, crime and justice, ethnicity, housing, labour, ageing, economics, marital status, social support, deprivation, religion, occupation, finances or family circumstances. \u2022 Lifestyle - Includes any data related to smoking, physical activity, dietary habits or alcohol. \u2022 Registry - Includes any data related to disease registries for research, national disease registries, audits, or birth and deaths records. \u2022 Environment and energy - Includes any data related to the monitoring or study of environmental or energy factors or events. \u2022 Information and communication - Includes any data related to the study or application of information and communication. \u2022 Politics - Includes any data related to political views, activities, voting, etc.\"",
+ "description": "The sub-type of the dataset content. Multiomics is selected on behalf of the submitter if more that one omics datasetSubType ('proteomics', 'transcriptomics', 'epigenomics', 'metabolomics', 'metagenomics', 'genomics', 'lipidomics') is selected",
+ "guidance": "Sub-types include those listed below under each data type. Datasets can have more than one sub-type associated.- Health and disease: Includes any data related to mental health, cardiovascular, cancer, rare diseases, metabolic and endocrine, neurological, reproductive, maternity and neonatology, respiratory, immunity, musculoskeletal, vision, renal and urogenital, oral and gastrointestinal, cognitive function or hearing.- Treatments/Interventions: Includes any data related to treatment or interventions related to vaccines or which are preventative or therapeutic in nature.- Measurements/Tests- Includes any data related to laboratory or other diagnostics.- Imaging types: Includes any data related to CT, MRI, PET, x-ray, ultrasound or pathology imaging.- *Imaging area of the body: Indicates whether the dataset relates to head, chest, arm abdomen or leg imaging.- Omics: Includes any data related to proteomics, transcriptomics, epigenomics, metabolomics, multiomics, metagenomics or genomics. Multiomics is selected on behalf of the submitter if more that one omics datasetSubType is selected.- Socioeconomic: Includes any data related to education, crime and justice, ethnicity, housing, labour, ageing, economics, marital status, social support, deprivation, religion, occupation, finances or family circumstances.- *Lifestyle: Includes any data related to smoking, physical activity, dietary habits or alcohol.- Registry: Includes any data related to disease registries for research, national disease registries, audits, or birth and deaths records.- Environment and energy: Includes any data related to the monitoring or study of environmental or energy factors or events.- *Information and communication: Includes any data related to the study or application of information and communication.- Politics*: Includes any data related to political views, activities, voting, etc.",
"title": "Dataset sub-type"
},
"source": {
@@ -1581,7 +1606,7 @@
],
"default": null,
"description": "Please indicate the source of the data extraction.",
- "guidance": "EPR: Data Extracted from Electronic Patient Record- Electronic survey: Data has been extracted from electronic surveys- LIMS: Data has been extracted from a laboratory information management system- Paper-based: Data has been extracted from paper forms- Free text NLP: Data has been extracted from unstructured freetext using natural language processing- Machine generated: Data has been machine generated i.e. imaging- Other: Data has been extracted by other means',",
+ "guidance": "EPR: Data Extracted from Electronic Patient Record.- Electronic survey: Data has been extracted from electronic surveys.- LIMS: Data has been extracted from a laboratory information management system.- Paper-based: Data has been extracted from paper forms.- Free text NLP: Data has been extracted from unstructured freetext using natural language processing.- Machine generated: Data has been machine generated i.e. imaging.- Other: Data has been extracted by other means.",
"title": "Source of data extraction"
},
"collectionSource": {
@@ -1598,7 +1623,7 @@
],
"default": null,
"description": "Please indicate the setting(s) where data was collected. Multiple settings may be provided.",
- "guidance": "\"Cohort, study, trial: Cohort, study or trial data collection as part of protocol Clinic: Specific clinic such as antenatal clinic Primary care - Referrals: General medical practitioner referral to another service Primary care - Clinic: General medical practitioner practice Primary care - Out of hours: General medical practitioner care or advice outside of standard hours Secondary care - Accident and emergency: Accident emergency department Secondary care - Outpatients: Outpatient care Secondary care - In-patients: In-patient care Secondary care - Ambulance: Care provided in association with ambulance service Secondary care - ICU: Intensive care units, also referred to as critical care units (CCUs) or intensive therapy units (ITUs) Prescribing - Community pharmacy: Pharmacy based in the community Prescribing - Community pharmacy: Pharmacy based in a hospital setting Patient report outcome: Reported by patient Wearables: Data collection devices worn on the body Local authority: Local authority or entity associated with a local authority National government: National government or entity associated with the national government Community: Community settings Services: Services such as drug misuse or blood transfusion Home: Home setting Private: Private medical clinic Social care - Health care at home: service provided in the home or residence of a person Social care - Other social data: service provided in a setting outside of the person's home or residence Census: collected as part of census Other: Other setting\"",
+ "guidance": "Cohort, study, trial: Cohort, study or trial data collection as part of protocol.- Clinic: Specific clinic such as antenatal clinic.- Primary care - Referrals: General medical practitioner referral to another service.- Primary care - Clinic: General medical practitioner practice.- Primary care - Out of hours: General medical practitioner care or advice outside of standard hours.- Secondary care - Accident and emergency: Accident emergency department.- Secondary care - Outpatients: Outpatient care.- Secondary care - In-patients: In-patient care.- Secondary care - Ambulance: Care provided in association with ambulance service.- Secondary care - ICU: Intensive care units, also referred to as critical care units (CCUs) or intensive therapy units (ITUs).- Prescribing - Community pharmacy: Pharmacy based in the community.- Prescribing - Community pharmacy: Pharmacy based in a hospital setting.- Patient report outcome: Reported by patient.- Wearables: Data collection devices worn on the body.- Local authority: Local authority or entity associated with a local authority.- National government: National government or entity associated with the national government.- Community: Community settings.- Services: Services such as drug misuse or blood transfusion.- Home: Home setting.- Private: Private medical clinic.- Social care - Health care at home: service provided in the home or residence of a person.- Social care - Other social data: service provided in a setting outside of the person's home or residence.- Census: collected as part of census.- Other: Other setting.",
"title": "Collection source setting"
},
"imageContrast": {
@@ -1612,7 +1637,7 @@
],
"default": "Not stated",
"description": "Indicate whether usage of imaging contrast is captured within the dataset.",
- "guidance": "If any constrast media or constrast agents were used in creating the images within the dataset and the constrast is known, mark 'Yes'. If this information is not known or not captured, indicate 'Not stated'. If there was no contrast used in the images, mark 'No'.",
+ "guidance": "If any contrast media or contrast agents were used in creating the images within the dataset and the contrast is known, mark 'Yes'. If this information is not known or not captured, indicate 'Not stated'. If there was no contrast used in the images, mark 'No'.",
"title": "Image contrast"
}
},
@@ -1664,7 +1689,7 @@
}
],
"default": null,
- "description": "Coverate by origin (geographical and situations).",
+ "description": "Coverage by origin (geographical and situations).",
"title": "Origin Coverage"
},
"temporal": {
@@ -1890,11 +1915,12 @@
"$ref": "#/$defs/OneHundredFiftyCharacters"
}
],
- "description": "Title of the dataset limited to 150 characters. It should provide a short description of the dataset and be unique across the gateway. If your title is not unique, please add a prefix with your organisation name or identifier to differentiate it from other datasets within the Gateway. Please avoid acronyms wherever possible. Good titles should summarise the content of the dataset and if relevant, the region the dataset covers.",
+ "description": "Title of the dataset limited to 150 characters. It should provide a short description of the dataset and be unique across the gateway. If your title is not unique, please add a prefix with your organisation name or identifier to differentiate it from other datasets within the Gateway. Good titles should summarise the content of the dataset and if relevant, the region the dataset covers.",
"examples": [
- "North West London COVID-19 Patient Level Situation Report"
+ "North West London COVID-19 Patient Level Situation Report",
+ "Scottish Morbidity Record (SMR)"
],
- "guidance": "The title should provide a short description of the dataset and be unique across the gateway.- If your title is not unique, please add a prefix with your organisation name or identifier to differentiate it from other datasets within the Gateway.- If the dataset is a \u201clinked dataset\u201d, please indicate this using the prefix \u201cLinked\u201d.- Please avoid acronyms wherever possible.- Good titles should summarise the content of the dataset and if relevant, the region the dataset covers.- Example: North West London COVID-19 Patient Level Situation Report',",
+ "guidance": "The title should provide a short description of the dataset and be unique across the gateway.- If your title is not unique, please add a prefix with your organisation name or identifier to differentiate it from other datasets within the Gateway.- If an accronym is widely used the dataset name, please add it in brackets () at the end of the title.- Good titles should summarise the content of the dataset and if relevant, the region the dataset covers.- Example: North West London COVID-19 Patient Level Situation Report",
"title": "Title"
},
"abstract": {
@@ -1907,7 +1933,7 @@
"examples": [
"CPRD Aurum contains primary care data contributed by General Practitioner (GP) practices using EMIS Web\u00ae including patient registration information and all care events that GPs have chosen to record as part of their usual medical practice."
],
- "guidance": "The abstract should provide a clear and brief descriptive signpost for researchers who are searching for data that may be relevant to their research.- The abstract should allow the reader to determine the scope of the data collection and accurately summarise its content.- Effective abstracts should avoid long sentences and abbreviations where possible.- Note: Researchers will view Titles and Abstracts when searching for datasets and choosing whether to explore their content further. Abstracts should be different from the full description for a dataset.- Example: CPRD Aurum contains primary care data contributed by General Practitioner (GP) practices using EMIS Web\u00ae including patient registration information and all care events that GPs have chosen to record as part of their usual medical practice.',",
+ "guidance": "The abstract should provide a clear and brief descriptive signpost for researchers who are searching for data that may be relevant to their research.- The abstract should allow the reader to determine the scope of the data collection and accurately summarise its content.- Effective abstracts should avoid long sentences and abbreviations where possible.- Note: Researchers will view Titles and the first line of Abstracts (list view) when searching for datasets and choosing whether to explore their content further.- Abstracts should be different from the full description for a dataset.- Example: CPRD Aurum contains primary care data contributed by General Practitioner (GP) practices using EMIS Web\u00ae including patient registration information and all care events that GPs have chosen to record as part of their usual medical practice.",
"title": "Dataset abstract"
},
"dataProvider": {
@@ -1916,8 +1942,8 @@
"$ref": "#/$defs/Organisation"
}
],
- "description": "This is the organisation responsible for running or supporting the data access request process, as well as publishing and maintaining the metadata. In most this will be the same as the HDR UK Organisation (Hub or Alliance Member). However, in some cases this will be different i.e. Tissue Directory are an HDR UK Gateway organisation but coordinate activities across a number of data publishers i.e. Cambridge Blood and Stem Cell Biobank.",
- "title": "Dataset provider"
+ "description": "This is the organisation responsible for running or supporting the data access request process, as well as enquiries about a dataset. In most this will be the same as the HDR UK Organisation (Hub or Alliance Member). However, in some cases this will be different i.e. Tissue Directory are an HDR UK Gateway organisation but coordinate activities across a number of data publishers i.e. Cambridge Blood and Stem Cell Biobank.",
+ "title": "Dataset Custodian"
},
"populationSize": {
"description": "Input the number of people captured within the dataset.",
@@ -1940,11 +1966,11 @@
"type": "null"
}
],
- "description": "Please provide a list of relevant and specific keywords that can improve the SEO of your dataset as a comma separated list. Notes: Onboarding portal will suggest keywords based on title, abstract and description. We are compiling a standardised list of keywords and synonyms across datasets to make filtering easier for users.",
+ "description": "Please provide a list of relevant and specific keywords that can improve the search engine optimisation (SEO) of your dataset as a comma separated list. Notes: Onboarding portal will suggest keywords based on title, abstract and description. We are compiling a standardised list of keywords and synonyms across datasets to make filtering easier for users.",
"examples": [
- "Preprints,Papers,HDR UK"
+ "Health Data, Research, SAIL, Primary care, GP"
],
- "guidance": "Please provide relevant and specific keywords that can improve the search engine optimization of your dataset.- Please enter one keyword at a time and click Add New Field to add further keywords.- Text from the title is automatically included in the search, there is no need to include this in the keywords.- Include words that researcher may include in their searches.- Example: Health Data, Research, SAIL, Primary care, GP',",
+ "guidance": "Please provide relevant and specific keywords that can improve the search engine optimization of your dataset.- Please enter one keyword at a time and click Add New Field to add further keywords.- Text from the title is automatically included in the search, there is no need to include this in the keywords.- Include words that researcher may include in their searches.",
"title": "Keywords"
},
"doiName": {
@@ -1957,12 +1983,12 @@
}
],
"default": null,
- "description": "DOI associated to this dataset.",
+ "description": "DOI associated to this dataset. Find out more about DOIs here: https://www.doi.org/the-identifier/what-is-a-doi/",
"examples": [
"10.1093/ije/dyx196"
],
- "guidance": "Please note: This is not the DOI of the publication(s) associated with the dataset.- All HDR UK registered datasets should either have a Digital Object Identifier (DOI) or be working towards obtaining one.- If a DOI is available, please provide the DOI.- Example: 10.1093/ije/dyx196- What happens if I do not have a DOI?: Contact your academic organisation to find out if there is an existing relationship with a DOI provider. If that is not available, sites such as figshare offer free services to mint a DOI for your dataset. Subsequent versions of the Metadata Exchange will provide a DOI minting service.',",
- "title": "DOI for dataset"
+ "guidance": "Please note: This is not the DOI of the publication(s) associated with the dataset.- All HDR UK registered datasets should either have a (DOI) or be working towards obtaining one.- If a DOI is available, please provide the DOI.- What happens if I do not have a DOI?: Contact your academic organisation to find out if there is an existing relationship with a DOI provider. If that is not available, sites such as figshare offer free services to mint a DOI for your dataset. Subsequent versions of the Metadata Exchange will provide a DOI minting service.",
+ "title": "Digital Object Identifier (DOI) for dataset"
},
"contactPoint": {
"allOf": [
@@ -1974,7 +2000,7 @@
"examples": [
"SAILDatabank@swansea.ac.uk"
],
- "guidance": "Organisations are expected to provide a dedicated email address associated with the data access request process. If no contact point is provided in this field, this field will be defaulted to the teams support email provided in the teams setting. Note: An employee's email address can only be provided on a temporary basis and if one is provided, you must obtain explicit consent for this purpose. - Example: SAILDatabank@swansea.ac.uk'.",
+ "guidance": "Organisations are expected to provide a dedicated email address associated with the data access request process. If no contact point is provided in this field, this field will be defaulted to the teams support email provided in the teams setting.Note: An employee's email address can only be provided on a temporary basis and if one is provided, you must obtain explicit consent for this purpose.",
"title": "Contact point"
},
"alternateIdentifiers": {
@@ -2025,7 +2051,7 @@
}
],
"description": "Please indicate the frequency of distribution release. If a dataset is distributed regularly please choose a distribution release periodicity from the constrained list and indicate the next release date. When the release date becomes historical, a new release date will be calculated based on the publishing periodicity. If a dataset has been published and will remain static please indicate that it is static and indicated when it was released. If a dataset is released on an irregular basis or \u201con-demand\u201d please indicate that it is Irregular and leave release date as null. If a dataset can be published in real-time or near-real-time please indicate that it is continuous and leave release date as null. Notes: see https://www.dublincore.org/specifications/dublin-core/collection-description/frequency/",
- "guidance": "'- Please indicate the frequency of publishing.- If a dataset is published regularly please choose a publishing periodicity from the constrained list and indicate the next release date.- When the release date becomes historical, a new release date will be calculated based on the publishing periodicity.- If a dataset has been published and will remain static please indicate that it is static and indicate when it was released.- If a dataset is released on an irregular basis or \u201con-demand\u201d please indicate that it is Irregular and leave release date as null.- If a dataset can be published in real-time or near-real-time please indicate that it is continuous and leave release date as null.- Notes: see https://www.dublincore.org/specifications/dublin-core/collection-description/frequency/- Static: Dataset published once.- Irregular: Dataset published at uneven intervals.- Continuous: Dataset published without interruption.- Biennial: Dataset published every two years.- Annual: Dataset published occurs once a year.- Biannual: Dataset published twice a year.- Quarterly: Dataset published every three months.- Bimonthly: Dataset published every two months.- Monthly: Dataset published once a month.- Biweekly: Dataset published every two weeks.- Weekly: Dataset published once a week.- Twice weekly: Dataset published twice a week.- Daily: Dataset published once a day.- Other: Dataset published using other interval.',",
+ "guidance": "Please indicate the frequency of publishing.- If a dataset is published regularly please choose a publishing periodicity from the constrained list and indicate the next release date.- When the release date becomes historical, a new release date will be calculated based on the publishing periodicity.- If a dataset has been published and will remain static please indicate that it is static and indicate when it was released.- If a dataset is released on an irregular basis or \u201con-demand\u201d please indicate that it is Irregular and leave release date as null.- If a dataset can be published in real-time or near-real-time please indicate that it is continuous and leave release date as null.- Notes: see https://www.dublincore.org/specifications/dublin-core/collection-description/frequency/. Options:- Static: Dataset published once.- Irregular: Dataset published at uneven intervals.- Continuous: Dataset published without interruption.- Biennial: Dataset published every two years.- Annual: Dataset published occurs once a year.- Biannual: Dataset published twice a year.- Quarterly: Dataset published every three months.- Bimonthly: Dataset published every two months.- Monthly: Dataset published once a month.- Biweekly: Dataset published every two weeks.- Weekly: Dataset published once a week.- Twice weekly: Dataset published twice a week.- Daily: Dataset published once a day.- Other: Dataset published using other interval.",
"title": "Publishing frequency"
},
"distributionReleaseDate": {
@@ -2044,7 +2070,7 @@
],
"default": null,
"description": "Date of the latest release of the dataset. If this is a regular release i.e. quarterly, or this is a static dataset please complete this alongside Periodicity. If this is Irregular or Continuously released please leave this blank. Notes: Periodicity and release date will be used to determine when the next release is expected. E.g. if the release date is documented as 01/01/2020 and it is now 20/04/2020 and there is a quarterly release schedule, the latest release will be calculated as 01/04/2020.",
- "guidance": "'- Please indicate the frequency the dataset is published.- If a dataset is published regularly please choose a publishing periodicity from the constrained list and indicate the next release date.- When the release date becomes historical, a new release date will be calculated based on the publishing periodicity.- If a dataset has been published and will remain static please indicate that it is static and indicate when it was released.- If a dataset is released on an irregular basis or \u201con-demand\u201d please indicate that it is Irregular and leave release date as null.- If a dataset can be published in real-time or near-real-time please indicate that it is continuous and leave release date as null.- Notes: see https://www.dublincore.org/specifications/dublin-core/collection-description/frequency/',",
+ "guidance": "Please indicate the frequency the dataset is published.- If a dataset is published regularly please choose a publishing periodicity from the constrained list and indicate the next release date.- When the release date becomes historical, a new release date will be calculated based on the publishing periodicity.- If a dataset has been published and will remain static please indicate that it is static and indicate when it was released.- If a dataset is released on an irregular basis or \u201con-demand\u201d please indicate that it is Irregular and leave release date as null.- If a dataset can be published in real-time or near-real-time please indicate that it is continuous and leave release date as null.- Notes: see https://www.dublincore.org/specifications/dublin-core/collection-description/frequency/",
"title": "Distribution release date"
},
"startDate": {
@@ -2059,7 +2085,7 @@
}
],
"description": "The start of the time period that the dataset provides coverage for. If there are multiple cohorts in the dataset with varying start dates, please provide the earliest date and use the description or the media attribute to provide more information.",
- "guidance": "The start of the time period that the dataset provides coverage for.- If there are multiple cohorts in the dataset with varying start dates, please provide the earliest date and use the description or the media attribute to provide more information.',",
+ "guidance": "The start of the time period that the dataset provides coverage for.- If there are multiple cohorts in the dataset with varying start dates, please provide the earliest date and use the description or the media attribute to provide more information.",
"title": "Start date"
},
"endDate": {
@@ -2081,7 +2107,7 @@
],
"default": null,
"description": "The end of the time period that the dataset provides coverage for. If the dataset is \u201cContinuous\u201d and has no known end date, please state continuous. If there are multiple cohorts in the dataset with varying end dates, please provide the latest date and use the description or the media attribute to provide more information.",
- "guidance": "The end of the time period that the dataset provides coverage for.- If the dataset is \u201cContinuous\u201d and has no known end date, please leave blank.- If there are multiple cohorts in the dataset with varying end dates, please provide the latest date.',",
+ "guidance": "The end of the time period that the dataset provides coverage for.- If the dataset is \u201cContinuous\u201d and has no known end date, please leave blank.- If there are multiple cohorts in the dataset with varying end dates, please provide the latest date.",
"title": "End date"
},
"timeLag": {
@@ -2091,7 +2117,7 @@
}
],
"description": "Please indicate the typical time-lag between an event and the data for that event appearing in the dataset.",
- "guidance": "Please indicate the typical time-lag between an event and the data for that event appearing in the dataset.- Less than 1 week: Typical time lag of less than a week- 1-2 weeks: Typical time lag of one to two weeks- 2-4 weeks: Typical time lag of two to four weeks- 1-2 months: Typical time lag of one to two months- 2-6 months: Typical time lag of two to six months- 6 months plus: Typical time lag of more than six months- Variable: Variable time lag- Not applicable: Not Applicable i.e. static dataset- Other: Other time lag',",
+ "guidance": "Please indicate the typical time-lag between an event and the data for that event appearing in the dataset.- Less than 1 week: Typical time lag of less than a week.- 1-2 weeks: Typical time-lag of one to two weeks.- 2-4 weeks: Typical time-lag of two to four weeks.- 1-2 months: Typical time-lag of one to two months.- 2-6 months: Typical time-lag of two to six months.- 6 months plus: Typical time-lag of more than six months.- Variable: Variable time-lag.- Not applicable: Not Applicable i.e. static dataset.- Other: Other time-lag.",
"title": "Time lag"
}
},
@@ -2156,8 +2182,8 @@
}
],
"default": null,
- "description": "Please provide an indication of consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used. NOTE: we have extended the DUO to include a value for NO LINKAGE.",
- "guidance": "Please provide an indication of consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used.- General research use: This data use limitation indicates that use is allowed for general research use for any research purpose- Genetic studies only: This data use limitation indicates that use is limited to genetic studies only (i.e., no phenotype-only research)- No general methods research: This data use limitation indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations.- No restriction: This data use limitation indicates there is no restriction on use.- Research-specific restrictions: This data use limitation indicates that use is limited to studies of a certain research type.- Research use only: This data use limitation indicates that use is limited to research purposes (e.g., does not include its use in clinical care).- No linkage: This data use limitation indicates there is a restriction on linking to any other datasets',",
+ "description": "Please provide an indication of consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used. NOTE: we have extended the Data Use Ontology to include a value for NO LINKAGE.",
+ "guidance": "Please provide an indication of consent permissions for datasets and/or materials, and relates to the purposes for which datasets and/or material might be removed, stored or used.- General research use: This data use limitation indicates that use is allowed for general research use for any research purpose.- Genetic studies only: This data use limitation indicates that use is limited to genetic studies only (i.e., no phenotype-only research).- No general methods research: This data use limitation indicates that use includes methods development research(e.g., development of software or algorithms) only within the bounds of other use limitations.- No restriction: This data use limitation indicates there is no restriction on use.- Research-specific restrictions: This data use limitation indicates that use is limited to studies of a certain research type.- Research use only: This data use limitation indicates that use is limited to research purposes (e.g., does not include its use in clinical care).- No linkage: This data use limitation indicates there is a restriction on linking to any other datasets",
"title": "Data use limitation"
},
"dataUseRequirements": {
@@ -2174,7 +2200,7 @@
],
"default": null,
"description": "Please indicate fit here are any additional conditions set for use if any, multiple requirements may be provided. Please ensure that these restrictions are documented in access rights information.",
- "guidance": "Please indicate if there are any additional conditions set for use if any, multiple requirements may be provided.- Please ensure that these restrictions are documented in access rights information.- Collaboration required: This requirement indicates that the requestor must agree to collaboration with the primary study investigator(s).- Ethics approval required: This requirement indicates that the requestor must provide documentation of local IRB/ERB approval.- Geographical restrictions: This requirement indicates that use is limited to within a specific geographic region.- Institution-specific restrictions: This requirement indicates that use is limited to use within an approved institution.- Not for profit use: This requirement indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use.- Project-specific restrictions: This requirement indicates that use is limited to use within an approved project.- Publication moratorium: This requirement indicates that requestor agrees not to publish results of studies until a specific date.- Publication required: This requirement indicates that requestor agrees to make results of studies using the data available to the larger scientific community.- Return to database or resource: This requirement indicates that the requestor must return derived/enriched data to the database/resource.- Time limit on use: This requirement indicates that use is approved for a specific number of months.- User-specific restriction: This requirement indicates that use is limited to use by approved users.',",
+ "guidance": "Please indicate if there are any additional conditions set for use if any, multiple requirements may be provided.- Please ensure that these restrictions are documented in access rights information.- Collaboration required: This requirement indicates that the requestor must either agree to join a research consortium or collaborate with the primary study investigator(s).- Ethics approval required: This requirement indicates that the requestor must provide documentation of local institutional review board (IRB)/ ethics review board (ERB) approval.- Geographical restrictions: This requirement indicates that use is limited to within a specific geographic region.- Institution-specific restrictions: This requirement indicates that use is limited to use within an approved institution.- Not for profit use: This requirement indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use.- Project-specific restrictions: This requirement indicates that use is limited to use within an approved project.- Publication moratorium: This requirement indicates that requestor agrees not to publish results of studies until a specific date.- Publication required: This requirement indicates that requestor agrees to make results of studies using the data available to the larger scientific community.- Return to database or resource: This requirement indicates that the requestor must return derived/enriched data to the database/resource.- Time limit on use: This requirement indicates that use is approved for a specific number of months.- User-specific restriction: This requirement indicates that use is limited to use by approved users.",
"title": "Data use requirements"
},
"resourceCreator": {
@@ -2201,7 +2227,10 @@
],
"default": null,
"description": "Please provide the text that you would like included as part of any citation that credits this dataset. This is typically just the name of the publisher. No employee details should be provided.",
- "guidance": "Please provide the text that you would like included as part of any citation that credits this dataset.- This is typically just the name of the publisher. No employee details should be provided.- To add multiple entries, please click on '+' symbol to enter each separate website.- Example: National Services Scotland',",
+ "examples": [
+ "National Services Scotland"
+ ],
+ "guidance": "Please provide the text that you would like included as part of any citation that credits this dataset.- This is typically just the name of the publisher. No employee details should be provided.- To add multiple entries, please click on '+' symbol to enter each separate website.- Example: National Services Scotland",
"title": "Citation requirements"
}
},
@@ -2248,7 +2277,7 @@
"examples": [
"1.1.0"
],
- "guidance": "Dataset metadata version should follow standard SEMVER naming conventions(https://semver.org). For example: 1.1.0 major.minor.patch. Major: Significant/breaking changes. Minor: New features and bug fixes. Patch: Minor fixes without new features.",
+ "guidance": "Dataset metadata version should follow standard SEMVER naming conventions (https://semver.org). For example: 1.1.0 major.minor.patch.Major: Significant/breaking changes.Minor: New features and bug fixes.Patch: Minor fixes without new features.",
"title": "Dataset Version"
},
"revisions": {
@@ -2262,7 +2291,7 @@
"issued": {
"description": "Datetime stamp of when this metadata version was initially issued",
"format": "date-time",
- "title": "Metadata Issued Datetime',",
+ "title": "Metadata Issued Datetime",
"type": "string"
},
"modified": {
@@ -2340,7 +2369,7 @@
"title": "Enrichment and Linkage"
},
"observations": {
- "description": "Multiple observations about the dataset may be provided and users are expected to provide at least one observation (1..*). We will be supporting the schema.org observation model (https://schema.org/Observation) with default values. Users will be encouraged to provide their own statistical populations as the project progresses. Example: Statistical Population 1 type: StatisticalPopulation populationType: Persons numConstraints: 0 Statistical Population 2 type: StatisticalPopulation populationType: Events numConstraints: 0 Statistical Population 3 type: StatisticalPopulation populationType: Findings numConstraints: 0 typeOf: Observation observedNode: Statistical Population 1 measuredProperty: count measuredValue: 32937 observationDate: \u201c2017\u201d\"",
+ "description": "This section provides an overview of observations of your dataset linked to specific points in time. Multiple observations about the dataset are encouraged to be provided, including multiple observations of the same property at different timepoints. At least one observation is required.",
"items": {
"$ref": "#/$defs/Observation"
},