required metadata needed for the GWDM
+Need a field in Mauro that captures the datasetID to link to gateway database - or can we just use the one created in Mauro?
+| title | +examples | +required | +type | +
|---|---|---|---|
| Gatewayid | ++ | True | +str | +
Need a field in Mauro that captures the dataset pid to link to gateway database
+| title | +examples | +required | +type | +
|---|---|---|---|
| Gatewaypid | ++ | True | +str | +
Aren't issued and modified always the same because of versioning? Is that fine to duplicate because datasets in dcat might look different?
+| title | +examples | +required | +type | +
|---|---|---|---|
| Issued | ++ | True | +datetime | +
Aren't issued and modified always the same because of versioning? Is that fine to duplicate because datasets in dcat might look different?
+| title | +examples | +required | +type | +
|---|---|---|---|
| Modified | ++ | True | +datetime | +
None
+Version number used for previous version of this dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| revision version | ++ | True | +str | +
Some url with a reference to the record of a previous version of this dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| revision url | ++ | True | +Url | +
Summary of metadata describing key pieces of information.
+The main title of the dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Title | ++ | True | +TwoHundredFiftyFiveCharacters | +
A shorter descriptive title of the dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Shorttitle | ++ | True | +ShortTitle | +
DOI associated to this dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Doiname | ++ | True | +Doi | +
Longer abstract detailing the dataset.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Abstract | ++ | True | +LongAbstractText | +
Comma separated key words associated to this dataset.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Keywords | ++ | True | +CommaSeparatedValues | +
Keywords that have been filtered and limited
+| title | +examples | +required | +type | +
|---|---|---|---|
| Controlled Keywords | ++ | True | +CommaSeparatedValues | +
email of a person who can be the main contact point of this dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Contact Point | ++ | True | +EmailStr | +
What type of dataset is this?
+| title | +examples | +required | +type | +
|---|---|---|---|
| Dataset type | ++ | True | +DatasetType | +
Longer description of the dataset in detail
+| title | +examples | +required | +type | +
|---|---|---|---|
| Description | ++ | True | +LongDescription | +
Link to details about the publisher of this dataset
+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)/
+| title | +examples | +required | +type | +
|---|---|---|---|
| Publisher name | ++ | True | +Name | +
The link to an ID somewhere in the gateway where more information on the publisher can be retrieved.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Publisher gateway id | ++ | False | +str | +
Spatial and Temporal coverage
+List of countries where the data was taken from
+| title | +examples | +required | +type | +
|---|---|---|---|
| Spatial | ++ | False | +CommaSeparatedValues | +
A list of what the dataset actually contains in terms of sample measurements
+| title | +examples | +required | +type | +
|---|---|---|---|
| Physical Sample Availability | ++ | False | +CommaSeparatedValues | +
Long description of the clinical/diagnostic/treatment pathway if applicable. This could include if the dataset is from a single speciality or area, a single tier of care, linked across two tier (e.g. primary and secondary care), or an integrated care record covering the whole patient pathway.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Pathway | ++ | False | +LongDescription | +
What is the typical time span that a patient appears in the dataset (follow up period)
+| title | +examples | +required | +type | +
|---|---|---|---|
| Followup | ++ | False | +Followup | +
Age range in whole years of participants in the dataset. Please provide range in the following format '[min age] – [max age]' where both the minimum and maximum are whole numbers (integers).
+| title | +examples | +required | +type | +
|---|---|---|---|
| Typical Age Range | ++ | False | +AgeRange | +
Provenance information
+None
+Indicates the purpose(s) that the dataset was collected.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Purpose | ++ | False | +CommaSeparatedValues | +
Indicates the source of the data extraction
+| title | +examples | +required | +type | +
|---|---|---|---|
| Source | ++ | False | +CommaSeparatedValues | +
Indicate the setting(s) where data was collected. Multiple settings may be provided
+| title | +examples | +required | +type | +
|---|---|---|---|
| Setting | ++ | False | +CommaSeparatedValues | +
None
+The start of the time period that the dataset provides coverage for
+| title | +examples | +required | +type | +
|---|---|---|---|
| Start Date | ++ | True | +date | +
The end of the time period that the dataset provides coverage for
+| title | +examples | +required | +type | +
|---|---|---|---|
| End Date | ++ | False | +date | +
Rypical time-lag between an event and the data for that event appearing in the dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Time Lag | ++ | True | +TimeLag | +
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.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Periodicity | ++ | True | +Periodicity | +
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.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Release Date | ++ | False | +date | +
Accessibility information.
+This section includes information about how the data can be used and how it is currently being used
+Any restrictions to its usage
+| title | +examples | +required | +type | +
|---|---|---|---|
| Data Use Limitation | ++ | True | +CommaSeparatedValues | +
Any requirements needed for data usage
+| title | +examples | +required | +type | +
|---|---|---|---|
| Data Use Requirements | ++ | True | +CommaSeparatedValues | +
Who has created this resource
+| title | +examples | +required | +type | +
|---|---|---|---|
| Resource Creator | ++ | False | +ShortDescription | +
This section includes information about data access
+Optional link(s) or a description of where the license associated to accessing this dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Access Rights | ++ | True | +CommaSeparatedValues | +
| title | +examples | +required | +type | +
|---|---|---|---|
| Access Service | ++ | False | +LongDescription | +
| title | +examples | +required | +type | +
|---|---|---|---|
| Organisation Access Request Cost | ++ | False | +LongDescription | +
An arbitrary guess at the time to gain access to the dataset...
+| title | +examples | +required | +type | +
|---|---|---|---|
| Access Request Duration | ++ | False | +DeliveryLeadTime | +
Comma separated country codes of where the data jurisdiction is.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Jurisdiction | ++ | True | +CommaSeparatedValues | +
Name of the data controller
+| title | +examples | +required | +type | +
|---|---|---|---|
| Data Controller | ++ | True | +LongDescription | +
Name of the data processors
+| title | +examples | +required | +type | +
|---|---|---|---|
| Data Processor | ++ | False | +LongDescription | +
Section includes technical attributes for language vocabularies, sizes etc. and gives researchers facts about and processing the underlying data in the dataset.
+Code value of the ontology vocabulary encoding
+| title | +examples | +required | +type | +
|---|---|---|---|
| Controlled Vocabulary | ++ | True | +CommaSeparatedValues | +
What the vocabulary conforms to.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Conforms To | ++ | True | +CommaSeparatedValues | +
Language code(s) of the language of the dataset metadata and underlying data is made available.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Language Code(s) | ++ | True | +CommaSeparatedValues | +
Format(s) the dataset can be made available in
+| title | +examples | +required | +type | +
|---|---|---|---|
| Dataset Format | ++ | True | +CommaSeparatedValues | +
Linkage and enrichment.
+??
+| title | +examples | +required | +type | +
|---|---|---|---|
| Is Generated Using | ++ | False | +CommaSeparatedValues | +
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
+| title | +examples | +required | +type | +
|---|---|---|---|
| Associated Media | ++ | False | +CommaSeparatedValues | +
??
+| title | +examples | +required | +type | +
|---|---|---|---|
| Data Uses | ++ | False | +CommaSeparatedValues | +
Rhe keystone paper associated with the dataset. Also include a list of known citations, if available and should be links to existing resources where the dataset has been used or referenced.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Is Reference in | ++ | False | +CommaSeparatedValues | +
URL of any analysis tools or models that have been created for this dataset and are available for further use
+| title | +examples | +required | +type | +
|---|---|---|---|
| Tools | ++ | False | +CommaSeparatedValues | +
Dataset Linkage copied over from
+Indicate if derived datasets or predefined extracts are available and the type of derivation available. Notes. Single or multiple dimensions can be provided as a derived extract alongside the dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Derivations | ++ | False | +CommaSeparatedValues | +
If the dataset is part of a group or family
+| title | +examples | +required | +type | +
|---|---|---|---|
| Is PartOf | ++ | False | +CommaSeparatedValues | +
Dataset is a member of XXX(?)
+| title | +examples | +required | +type | +
|---|---|---|---|
| Is MemberOf | ++ | False | +CommaSeparatedValues | +
Links to other datasets.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Linked Datasets | ++ | False | +CommaSeparatedValues | +
Please provide the keystone paper associated with the dataset.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Investigations | ++ | False | +CommaSeparatedValues | +
Obsservations
+| title | +examples | +required | +type | +
|---|---|---|---|
| Observations | ++ | False | +Observation | +
Descriptions of all tables and data elements that can be included in the dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Structural Metadata | ++ | False | +DataTable | +
required metadata needed for the GWDM
+Need a field in Mauro that captures the datasetID to link to gateway database - or can we just use the one created in Mauro?
+| title | +examples | +required | +type | +
|---|---|---|---|
| Gatewayid | ++ | True | +str | +
Need a field in Mauro that captures the dataset pid to link to gateway database
+| title | +examples | +required | +type | +
|---|---|---|---|
| Gatewaypid | ++ | True | +str | +
Aren't issued and modified always the same because of versioning? Is that fine to duplicate because datasets in dcat might look different?
+| title | +examples | +required | +type | +
|---|---|---|---|
| Issued | ++ | True | +datetime | +
Aren't issued and modified always the same because of versioning? Is that fine to duplicate because datasets in dcat might look different?
+| title | +examples | +required | +type | +
|---|---|---|---|
| Modified | ++ | True | +datetime | +
None
+Version number used for previous version of this dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| revision version | ++ | True | +str | +
Some url with a reference to the record of a previous version of this dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| revision url | ++ | True | +Url | +
Dataset metadata version
+| title | +examples | +required | +type | +
|---|---|---|---|
| Dataset Version | +['1.1.0'] | +True | +str | +
Summary of metadata describing key pieces of information.
+The main title of the dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Title | ++ | True | +TwoHundredFiftyFiveCharacters | +
A shorter descriptive title of the dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Shorttitle | ++ | True | +ShortTitle | +
DOI associated to this dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Doiname | ++ | True | +Doi | +
Longer abstract detailing the dataset.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Abstract | ++ | True | +LongAbstractText | +
Comma separated key words associated to this dataset.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Keywords | ++ | True | +CommaSeparatedValues | +
Keywords that have been filtered and limited
+| title | +examples | +required | +type | +
|---|---|---|---|
| Controlled Keywords | ++ | True | +CommaSeparatedValues | +
email of a person who can be the main contact point of this dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Contact Point | ++ | True | +EmailStr | +
What type of dataset is this?
+| title | +examples | +required | +type | +
|---|---|---|---|
| Dataset type | ++ | True | +DatasetType | +
Longer description of the dataset in detail
+| title | +examples | +required | +type | +
|---|---|---|---|
| Description | ++ | True | +LongDescription | +
Link to details about the publisher of this dataset
+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)/
+| title | +examples | +required | +type | +
|---|---|---|---|
| Name | ++ | True | +Name | +
The link to an ID somewhere in the gateway where more information on the publisher can be retrieved.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Publisher gateway id | ++ | False | +str | +
The Research Organization Registry (ROR) for the organisation, if applicable
+| title | +examples | +required | +type | +
|---|---|---|---|
| Research Organization Registry Identifier | ++ | False | +str | +
Observational, Spatial and Temporal coverage
+List of countries where the data was taken from
+| title | +examples | +required | +type | +
|---|---|---|---|
| Spatial | ++ | False | +CommaSeparatedValues | +
Long description of the clinical/diagnostic/treatment pathway if applicable. This could include if the dataset is from a single speciality or area, a single tier of care, linked across two tier (e.g. primary and secondary care), or an integrated care record covering the whole patient pathway.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Pathway | ++ | False | +LongDescription | +
What is the typical time span that a patient appears in the dataset (follow up period)
+| title | +examples | +required | +type | +
|---|---|---|---|
| Followup | ++ | False | +Followup | +
Age range in whole years of participants in the dataset. Please provide range in the following format '[min age] – [max age]' where both the minimum and maximum are whole numbers (integers).
+| title | +examples | +required | +type | +
|---|---|---|---|
| Typical Age Range | ++ | False | +AgeRange | +
Male, Female, Other
+| title | +examples | +required | +type | +
|---|---|---|---|
| Gender | ++ | False | +Gender | +
Blood, Saliva, Urine, Other
+| title | +examples | +required | +type | +
|---|---|---|---|
| Biological Samples | ++ | False | +BiologicalSamples | +
Mental health, Cognitive function
+| title | +examples | +required | +type | +
|---|---|---|---|
| Psychological | ++ | False | +Psychological | +
Cardiovascular, Respiratory, Musculoskeletal, Hearing and Vision, Reproductive
+| title | +examples | +required | +type | +
|---|---|---|---|
| Physical | ++ | False | +Physical | +
Height, Weight, Waist circumference, Hip circumference, Blood pressure
+| title | +examples | +required | +type | +
|---|---|---|---|
| Anthropometric | ++ | False | +Anthropometric | +
Cohort lifestyle habits: Smoking, Physical activity, Dietary habits, Alcohol
+| title | +examples | +required | +type | +
|---|---|---|---|
| Lifestyle | ++ | False | +Lifestyles | +
Occupation, Family circumstances, Housing, Education, Ethnic group, Martial status, Social support
+| title | +examples | +required | +type | +
|---|---|---|---|
| Socio-economic | ++ | False | +SocioEconomic | +
Provenance information
+None
+Indicates the purpose(s) that the dataset was collected.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Purpose | ++ | False | +CommaSeparatedValues | +
Indicates the source of the data extraction
+| title | +examples | +required | +type | +
|---|---|---|---|
| Source | ++ | False | +CommaSeparatedValues | +
Indicate the setting(s) where data was collected. Multiple settings may be provided
+| title | +examples | +required | +type | +
|---|---|---|---|
| Setting | ++ | False | +CommaSeparatedValues | +
None
+The start of the time period that the dataset provides coverage for
+| title | +examples | +required | +type | +
|---|---|---|---|
| Start Date | ++ | True | +date | +
The end of the time period that the dataset provides coverage for
+| title | +examples | +required | +type | +
|---|---|---|---|
| End Date | ++ | False | +date | +
Rypical time-lag between an event and the data for that event appearing in the dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Time Lag | ++ | True | +TimeLag | +
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.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Periodicity | ++ | True | +Periodicity | +
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.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Release Date | ++ | False | +date | +
Accessibility information.
+This section includes information about how the data can be used and how it is currently being used
+Any restrictions to its usage
+| title | +examples | +required | +type | +
|---|---|---|---|
| Data Use Limitation | ++ | True | +CommaSeparatedValues | +
Any requirements needed for data usage
+| title | +examples | +required | +type | +
|---|---|---|---|
| Data Use Requirements | ++ | True | +CommaSeparatedValues | +
Who has created this resource
+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)/
+| title | +examples | +required | +type | +
|---|---|---|---|
| Name | ++ | True | +Name | +
The link to an ID somewhere in the gateway where more information on the publisher can be retrieved.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Publisher gateway id | ++ | False | +str | +
The Research Organization Registry (ROR) for the organisation, if applicable
+| title | +examples | +required | +type | +
|---|---|---|---|
| Research Organization Registry Identifier | ++ | False | +str | +
This section includes information about data access
+Optional link(s) or a description of where the license associated to accessing this dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Access Rights | ++ | True | +CommaSeparatedValues | +
| title | +examples | +required | +type | +
|---|---|---|---|
| Access Service | ++ | False | +LongDescription | +
| title | +examples | +required | +type | +
|---|---|---|---|
| Organisation Access Request Cost | ++ | False | +LongDescription | +
An arbitrary guess at the time to gain access to the dataset...
+| title | +examples | +required | +type | +
|---|---|---|---|
| Access Request Duration | ++ | False | +DeliveryLeadTime | +
Comma separated country codes of where the data jurisdiction is.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Jurisdiction | ++ | True | +CommaSeparatedValues | +
Name of the data controller
+| title | +examples | +required | +type | +
|---|---|---|---|
| Data Controller | ++ | True | +LongDescription | +
Name of the data processors
+| title | +examples | +required | +type | +
|---|---|---|---|
| Data Processor | ++ | False | +LongDescription | +
Section includes technical attributes for language vocabularies, sizes etc. and gives researchers facts about and processing the underlying data in the dataset.
+Code value of the ontology vocabulary encoding
+| title | +examples | +required | +type | +
|---|---|---|---|
| Controlled Vocabulary | ++ | True | +CommaSeparatedValues | +
What the vocabulary conforms to.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Conforms To | ++ | True | +CommaSeparatedValues | +
Language code(s) of the language of the dataset metadata and underlying data is made available.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Language Code(s) | ++ | True | +CommaSeparatedValues | +
Format(s) the dataset can be made available in
+| title | +examples | +required | +type | +
|---|---|---|---|
| Dataset Format | ++ | True | +CommaSeparatedValues | +
Linkage and enrichment.
+??
+| title | +examples | +required | +type | +
|---|---|---|---|
| Is Generated Using | ++ | False | +CommaSeparatedValues | +
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
+| title | +examples | +required | +type | +
|---|---|---|---|
| Associated Media | ++ | False | +CommaSeparatedValues | +
??
+| title | +examples | +required | +type | +
|---|---|---|---|
| Data Uses | ++ | False | +CommaSeparatedValues | +
Rhe keystone paper associated with the dataset. Also include a list of known citations, if available and should be links to existing resources where the dataset has been used or referenced.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Is Reference in | ++ | False | +CommaSeparatedValues | +
URL of any analysis tools or models that have been created for this dataset and are available for further use
+| title | +examples | +required | +type | +
|---|---|---|---|
| Tools | ++ | False | +CommaSeparatedValues | +
Dataset Linkage copied over from
+Indicate if derived datasets or predefined extracts are available and the type of derivation available. Notes. Single or multiple dimensions can be provided as a derived extract alongside the dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Derivations | ++ | False | +CommaSeparatedValues | +
If the dataset is part of a group or family
+| title | +examples | +required | +type | +
|---|---|---|---|
| Is PartOf | ++ | False | +CommaSeparatedValues | +
Dataset is a member of XXX(?)
+| title | +examples | +required | +type | +
|---|---|---|---|
| Is MemberOf | ++ | False | +CommaSeparatedValues | +
Links to other datasets.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Linked Datasets | ++ | False | +CommaSeparatedValues | +
Please provide the keystone paper associated with the dataset.
+| title | +examples | +required | +type | +
|---|---|---|---|
| Investigations | ++ | False | +CommaSeparatedValues | +
Obsservations
+| title | +examples | +required | +type | +
|---|---|---|---|
| Observations | ++ | False | +Observation | +
Descriptions of all tables and data elements that can be included in the dataset
+| title | +examples | +required | +type | +
|---|---|---|---|
| Structural Metadata | ++ | False | +DataTable | +
Collection of OMOP IDs that are contained within the dataset.
+OMOP Concept IDs for measured quantities. E.g. 44810410 - https://athena.ohdsi.org/search-terms/terms/44810410
+| title | +examples | +required | +type | +
|---|---|---|---|
| OMOP Measurements | ++ | False | +CommaSeparatedIntegers | +
OMOP Concept IDs for drug exposures. E.g. 602396 - https://athena.ohdsi.org/search-terms/terms/602396
+| title | +examples | +required | +type | +
|---|---|---|---|
| OMOP Drugs | ++ | False | +CommaSeparatedIntegers | +
OMOP Concept IDs for observations.
+| title | +examples | +required | +type | +
|---|---|---|---|
| OMOP Observations | ++ | False | +CommaSeparatedIntegers | +
OMOP Concept IDs for specimens.
+| title | +examples | +required | +type | +
|---|---|---|---|
| OMOP Specimens | ++ | False | +CommaSeparatedIntegers | +
OMOP Concept IDs for condition occurrences.
+| title | +examples | +required | +type | +
|---|---|---|---|
| OMOP Condition Occurrences | ++ | False | +CommaSeparatedIntegers | +
OMOP Concept IDs for procedure occurrences.
+| title | +examples | +required | +type | +
|---|---|---|---|
| OMOP Procedure Occurrences | ++ | False | +CommaSeparatedIntegers | +
OMOP Concept IDs for device exposures.
+| title | +examples | +required | +type | +
|---|---|---|---|
| OMOP | ++ | False | +CommaSeparatedIntegers | +
System dataset identifier
+| title | +required | +type | +
|---|---|---|
| Dataset identifier | +True | +Uuidv4 | +
Examples: + * ['226fb3f1-4471-400a-8c39-2b66d46a39b6', 'https://web.www.healthdatagateway.org/dataset/226fb3f1-4471-400a-8c39-2b66d46a39b6']
+Dataset metadata version
+| title | +required | +type | +
|---|---|---|
| Dataset Version | +True | +Semver | +
Examples: + * 1.1.0
+Revisions of Dataset metadata
+Semantic Version
+| title | +required | +type | +
|---|---|---|
| + | True | +Semver | +
URL endpoint to obtain the version
+| title | +required | +type | +
|---|---|---|
| + | True | +Url | +
Dataset Metadata Creation Date
+| title | +required | +type | +
|---|---|---|
| Creation Date | +True | +datetime | +
Dataset Metadata Creation Date
+| title | +required | +type | +
|---|---|---|
| Modification Date | +True | +datetime | +
Summary metadata must be completed by Data Custodians onboarding metadata into the Innovation Gateway MVP.
+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.
+| title | +required | +type | +
|---|---|---|
| Title | +True | +OneHundredFiftyCharacters | +
Examples: + * ['North West London COVID-19 Patient Level Situation Report']
+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. The optimal length is one paragraph (limited to 255 characters) and effective abstracts should avoid long sentences and abbreviations where possible
+| title | +required | +type | +
|---|---|---|
| Dataset Abstract | +True | +AbstractText | +
Examples: + * CPRD Aurum contains primary care data contributed by General Practitioner (GP) practices using EMIS Web® including patient registration information and all care events that GPs have chosen to record as part of their usual medical practice.
+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.
+Please provide a Grid.ac identifier (see https://www.grid.ac/institutes) for your organisation. If your organisation does not have a Grid.ac identifier please use the “suggest and institute” function here: https://www.grid.ac/institutes#
+| title | +required | +type | +
|---|---|---|
| Organisation Identifier | +False | +Url | +
Name of the organisation
+| title | +required | +type | +
|---|---|---|
| Organisation Name | +True | +OneHundredFiftyCharacters | +
Please provide a logo associated with the Gateway Organisation using a valid URL. The following formats will be accepted .jpg, .png or .svg.
+| title | +required | +type | +
|---|---|---|
| Organisation Logo | +False | +Url | +
Please provide a URL that describes the organisation.
+| title | +required | +type | +
|---|---|---|
| Organisation Description | +False | +Description | +
Organisation contact point(s)
+| title | +required | +type | +
|---|---|---|
| Organisation Contact Point | +True | +EmailAddress | +
Please indicate if the organisation is an Alliance Member or a Hub.
+| title | +required | +type | +
|---|---|---|
| Organisation Membership | +False | +MemberOf | +
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.
+| title | +required | +type | +
|---|---|---|
| Organisation Default Access Rights | +False | +Url | +
Please provide an indication of the typical processing times based on the types of requests typically received. Note: This value will be used as default access request duration for all datasets submitted by the organisation. However, there will be the opportunity to overwrite this value for each dataset.
+| title | +required | +type | +
|---|---|---|
| Access Request Duration | +False | +DeliveryLeadTime | +
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 | +required | +type | +
|---|---|---|
| Organisation Access Service | +False | +LongDescription | +
Examples: + * https://cnfl.extge.co.uk/display/GERE/Research+Environment+User+Guide
+Please provide link(s) to a webpage or a short description detailing the commercial model for processing data access requests for the organisation (if available) Definition: Indication of commercial model or cost (in GBP) for processing each data access request by the data custodian.
+| title | +required | +type | +
|---|---|---|
| Organisation Access Request Cost | +False | +ShortDescription | +
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. Notes: where there are existing data-sharing arrangements such as the HDR UK HUB data sharing agreement or the NIHR HIC data sharing agreement this should be indicated within access rights. This value will be used as terms for all datasets submitted by the organisation. However, there will be the opportunity to overwrite this value for each dataset.
+| title | +required | +type | +
|---|---|---|
| Data Use Limitation | +False | +CommaSeparatedValues | +
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.
+| title | +required | +type | +
|---|---|---|
| Data Use Requirements | +False | +CommaSeparatedValues | +
Please provide a valid email address that can be used to coordinate data access requests with the publisher. Organisations are expected to provide a dedicated email address associated with the data access request process. Notes- An employee's email address can only be provided on a temporary basis and if one is provided an explicit consent must be obtained for this purpose.
+| title | +required | +type | +
|---|---|---|
| Contact Point | +True | +EmailAddress | +
Examples: + * SAILDatabank@swansea.ac.uk
+Please provide 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.
+| title | +required | +type | +
|---|---|---|
| Keywords | +True | +CommaSeparatedValues | +
Alternate dataset identifiers or local identifiers
+| title | +required | +type | +
|---|---|---|
| Alternate dataset identifiers | +False | +CommaSeparatedValues | +
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.
+| title | +required | +type | +
|---|---|---|
| Digital Object Identifier | +False | +Doi | +
Examples: + * 10.3399/bjgp17X692645
+Documentation can include a rich text description of the dataset or links to media such as documents, images, presentations, videos or links to data dictionaries, profiles or dashboards. Organisations are required to confirm that they have permission to distribute any additional media.
+A free-text description of the record.
+| title | +required | +type | +
|---|---|---|
| Description | +False | +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.
+| title | +required | +type | +
|---|---|---|
| Associated Media | +False | +CommaSeparatedValues | +
Examples: + * PDF Document that describes study protocol
+Please complete only if the dataset is part of a group or family
+| title | +required | +type | +
|---|---|---|
| Group | +False | +CommaSeparatedValues | +
Examples: + * Hospital Episodes Statistics datasets (A&E, APC, OP, AC MSDS).
+This information includes attributes for geographical and temporal coverage, cohort details etc. to enable a deeper understanding of the dataset content so that researchers can make decisions about the relevance of the underlying data.
+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.
+| title | +required | +type | +
|---|---|---|
| Geographic Coverage | +False | +CommaSeparatedValues | +
Examples: + * https://www.geonames.org/2635167/united-kingdom-of-great-britain-and-northern-ireland.html
+Please indicate the age range in whole years of participants in the dataset. Please provide range in the following format '[min age] – [max age]' where both the minimum and maximum are whole numbers (integers).
+| title | +required | +type | +
|---|---|---|
| Age Range | +False | +AgeRange | +
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 sample are not yet available, please provide “AVAILABILITY TO BE CONFIRMED”. If samples are not available, then please provide “NOT AVAILABLE”.
+| title | +required | +type | +
|---|---|---|
| Physical Sample Availability | +False | +CommaSeparatedValues | +
Examples: + * BONE MARROW
+If known, what is the typical time span that a patient appears in the dataset (follow up period)
+| title | +required | +type | +
|---|---|---|
| Followup | +False | +Followup | +
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 | +required | +type | +
|---|---|---|
| Pathway | +False | +Description | +
Provenance information allows researchers to understand data within the context of its origins and can be an indicator of quality, authenticity and timeliness.
+None
+Pleases indicate the purpose(s) that the dataset was collected.
+| title | +required | +type | +
|---|---|---|
| Purpose | +False | +CommaSeparatedValues | +
Pleases indicate the source of the data extraction
+| title | +required | +type | +
|---|---|---|
| Source | +False | +CommaSeparatedValues | +
Pleases indicate the setting(s) where data was collected. Multiple settings may be provided
+| title | +required | +type | +
|---|---|---|
| Setting | +False | +CommaSeparatedValues | +
None
+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 “on-demand” 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 | +required | +type | +
|---|---|---|
| Periodicity | +True | +Periodicity | +
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.
+| title | +required | +type | +
|---|---|---|
| Release Date | +False | +date | +
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 | +required | +type | +
|---|---|---|
| Start Date | +True | +date | +
The end of the time period that the dataset provides coverage for. If the dataset is “Continuous” 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.
+| title | +required | +type | +
|---|---|---|
| End Date | +False | +date | +
Please indicate the typical time-lag between an event and the data for that event appearing in the dataset
+| title | +required | +type | +
|---|---|---|
| Time Lag | +True | +TimeLag | +
Accessibility information allows researchers to understand access, usage, limitations, formats, standards and linkage or interoperability with toolsets.
+This section includes information about how the data can be used and how it is currently being used
+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
+| title | +required | +type | +
|---|---|---|
| Data Use Limitation | +False | +CommaSeparatedValues | +
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.
+| title | +required | +type | +
|---|---|---|
| Data Use Requirements | +False | +CommaSeparatedValues | +
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.
+| title | +required | +type | +
|---|---|---|
| Citation Requirements | +False | +ShortDescription | +
None
+| title | +required | +type | +
|---|---|---|
| Investigations | +False | +CommaSeparatedValues | +
Please provide the keystone paper associated with the dataset. Also include a list of known citations, if available and should be links to existing resources where the dataset has been used or referenced. Please provide multiple entries, or if you are using a csv upload please provide them as a tab separated list.
+| title | +required | +type | +
|---|---|---|
| Citations | +False | +Doi | +
This section includes information about data access
+None
+| title | +required | +type | +
|---|---|---|
| Access Rights | +True | +LongDescription | +
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 | +required | +type | +
|---|---|---|
| Access Service | +False | +LongDescription | +
Examples: + * https://cnfl.extge.co.uk/display/GERE/Research+Environment+User+Guide
+Please provide link(s) to a webpage detailing the commercial model for processing data access requests for the organisation (if available) Definition: Indication of commercial model or cost (in GBP) for processing each data access request by the data custodian.
+| title | +required | +type | +
|---|---|---|
| Organisation Access Request Cost | +False | +LongDescription | +
Please provide an indication of the typical processing times based on the types of requests typically received.
+| title | +required | +type | +
|---|---|---|
| Access Request Duration | +False | +DeliveryLeadTime | +
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.
+| title | +required | +type | +
|---|---|---|
| Jurisdiction | +True | +CommaSeparatedValues | +
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.
+| title | +required | +type | +
|---|---|---|
| Data Controller | +True | +LongDescription | +
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.
+| title | +required | +type | +
|---|---|---|
| Data Processor | +False | +LongDescription | +
Section includes technical attributes for language vocabularies, sizes etc. and gives researchers facts about and processing the underlying data in the dataset.
+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 “other” and contact support desk to ask for an addition. Notes: More than one vocabulary may be provided.
+| title | +required | +type | +
|---|---|---|
| Controlled Vocabulary | +True | +CommaSeparatedValues | +
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 “other” and contact support desk to ask for an addition.
+| title | +required | +type | +
|---|---|---|
| Conforms To | +True | +CommaSeparatedValues | +
This should list all the languages in which the dataset metadata and underlying data is made available.
+| title | +required | +type | +
|---|---|---|
| Language | +True | +CommaSeparatedValues | +
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.
+| title | +required | +type | +
|---|---|---|
| Format | +True | +CommaSeparatedValues | +
This section includes information about related datasets that may have previously been linked, as well as indicating if there is the opportunity to link to other datasets in the future. If a dataset has been enriched and/or derivations, scores and existing tools are available this section allows providers to indicate this to researchers.
+If applicable, please provide the DOI of other datasets that have previously been linked to this dataset and their availability. If no DOI is available, please provide the title of the datasets that can be linked, where possible using the same title of a dataset previously onboarded to the HOP. Note: If all the datasets from Gateway organisation can be linked please indicate “ALL” and the onboarding portal will automate linkage across the datasets submitted.
+| title | +required | +type | +
|---|---|---|
| Linked Datasets | +False | +CommaSeparatedValues | +
Indicate if derived datasets or predefined extracts are available and the type of derivation available. Notes. Single or multiple dimensions can be provided as a derived extract alongside the dataset.
+| title | +required | +type | +
|---|---|---|
| Derivations | +False | +CommaSeparatedValues | +
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 | +required | +type | +
|---|---|---|
| Tools | +False | +CommaSeparatedValues | +
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: <b> Statistical Population 1 </b> type: StatisticalPopulation populationType: Persons numConstraints: 0 <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: “2017”
+Please select one of the following statistical populations for you observation
+| title | +required | +type | +
|---|---|---|
| Statistical Population | +True | +StatisticalPopulationConstrained | +
Examples: + * PERSONS
+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.
+| title | +required | +type | +
|---|---|---|
| Measured Value | +True | +int | +
If SNOMED CT term does not provide sufficient detail, please provide a description that disambiguates the population type.
+| title | +required | +type | +
|---|---|---|
| Disambiguating Description | +False | +AbstractText | +
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.
+| title | +required | +type | +
|---|---|---|
| Observation Date | +True | +date | +
Initially this will be defaulted to "COUNT"
+| title | +required | +type | +
|---|---|---|
| Measured Property | +True | +MeasuredProperty | +
Descriptions of all tables and data elements that can be included in the dataset
+| title | +required | +type | +
|---|---|---|
| Structural Metadata | +False | +DataClass | +