<visible style=""/> <extendedDescription/> <viewStyle cssClass="" renderstyle="textarea"/> <description/> </field> </fields> </fieldSet> </fieldsets> <title>Data Summary Data Summary
<extendedDescription/> <description/> </section> </sections> <fieldGroups> <fieldGroup defaultVisibility="true" id="FindDataMetadataGroup" ordinal="1" page="0"> <fieldsets> <fieldSet id="useMetadataQ211FS" ordinal="1"> <fields> <field defaultVisibility="true" id="useMetadataQ211" ordinal="1"> <title>Q2.1.1 Will you use metadata to describe the data? true true false true true User can select from a list of metadata standards. If they cannot find the standard in the list provided then they should choose "not listed". Selecting this will result in a field in which the user can insert the URL to the description of the metadata scheme used. A "comments" box should exist to allow users to add comments. They may select more than one metadata standard. They may specify more than one URL when selecting "not listed". They are also presented with a field in which to specify the location of the metadata service. Users can select the "no metadata" button to specify no metadata will be used to describe the data.
Metadata standards The data will be described by metadata that follows the metadata standards described in <url1>, <url2>
Not listed true
Url URL to the description of the metadata scheme used
The data will not be described by any metadata
Comments
Q2.1.1a Will your metadata use standardised vocabularies? User selects from a drop-down list of existing standardised vocabularies or ‘not listed’ or ‘none’. There should be a ‘comments’ fields for additional information. If ‘not listed’ is selected the user is presented with two additional fields in which the user can put the URL to the new vocabulary along with a short description. The user should be allowed to select more than one option.
Not listed true true
None The metadata will not make use of any vocabulary
Url Description
Q2.1.1b Will you make the metadata available free-of-charge? User is presented with a ‘yes’ or ‘no’ along with a ‘comments’ field for additional information.
Q2.1.1c Will your metadata be harvestable?
<description/> <extendedDescription/> </fieldGroup> <fieldGroup defaultVisibility="true" id="namingConventionGroup" ordinal="2" page="0"> <fieldsets> <fieldSet id="namingConventionQ212FS" ordinal="1"> <fields> <field defaultVisibility="true" id="namingConventionQ212" ordinal="1"> <title>Q2.1.2 Will you use a naming conventions for your data? true User selects either ‘yes’ or ‘no’. If they choose ‘yes’ they are presented with a field asking them to put in the URLs where the naming conventions are described. There should be a ‘comments’ section to allow users to add additional information.
Url
Comments
Naming convention
Q2.1.3 Will you provide clear version numbers for your data? User selects a yes or no response. There should be a ‘comments’ field for the user to add additional notes.
Comments
Version numbers
Q2.1.4 Will you provide persistent identifiers for your data? true Users can select from a list: DOI, Persistent Unique Identifier. They can select the ‘no identifiers’ to indicate no persistent identifiers will be provided to the data. There should be a ‘comments’ field to allow the user to add additional information.
The data will be issued with <identifier type> identifiers once the data has reached an approved level of maturity for consumption by interested parties.
Comments
Persistent identifiers
Q2.1.5 Will you provide searchable metadata for your data? true Users are given the choices: ‘yes’ and ‘no’. There should be a ‘comments’ field to allow users to provide additional information.
Q2.1.5a What services will you use to provide searchable metadata? User can select from a list of discovery services (eg openAIRE etc) that allow the user to publish metadata on their datasets. They can choose ‘not listed’ to supply the URL and name of the discovery service that is not specified in the list.
Not listed
Url Name
Searchable metadata
Q2.1.6 Will you use standardised formats for some or all of your data? true true true true true true true
Comments
Q2.1.6a Which standardised data formats do you plan on using? User can select multiple formats from a list. The list could be harvested from the PRONOM registry (https://www.nationalarchives.gov.uk/PRONOM/Default.aspx not all formats may be listed). There should be an ‘other’ to allow the user to specify the ‘standard’ formats they use. This should include a ‘name’ and ‘url’ to information on the format. There should be a ‘comments’ field allowing the user to add additional information.
Other true true
Commnets
Url Name
Q2.1.6b Please describe the formats you plan to store your data in, including any URLs to documentation. User is presented with a ‘name’, ‘url’ field. They should be allowed to add more ‘name’ and ‘url’ fields. There should be a checkbox to indicate it’s a commonly used format in their field. There should be a ‘comments’ field to allow the user to add additional information.
Name Url
it’s a commonly used format
Comments
Standardised formats
Q2.1.7 Are the file formats you will use open? true User presented with a choice of ‘all’, ‘some’, ‘none’. There should be a ‘comments’ field for additional information.
Comments
<visible style=""/> <extendedDescription/> <viewStyle cssClass="" renderstyle="textarea"/> <description>User is presented with a field in which they can describe the data that are not in an open format and the reason why.</description> </field> </fields> </fieldSet> </fieldsets> <title>Open File Formats
Q2.1.8 Do supported open-source tools exist for accessing the data? for_some_data User is presented with a choice of ‘for all data’, ‘for some data’, ‘for no data’. The user is provided with a ‘comments’ section for additional information.
Comments
Q2.1.8a Please describe which data are require proprietary tools to access the data?
Open source Tools
Q2.1.9 Will you provide metadata describing the quality of the data? User is presented with a ‘yes’, ‘no’ choice along with a ‘comments’ field for additional information.
Comments
Quality Of Tha Data
2.1 Making data findable, including provisions for metadata
Q2.2.1 Are there ethical or legal issues that can impact sharing the data? true User is presented with a ‘yes’, ‘no’. A ‘comments’ field should be provided for the user to provide any additional information.
Comments
Q2.2.1a Please provide a description of the ethical or legal restrictions on sharing the data User is presented with a field in which they can supply a description of the restrictions.
ethical or legal issues ethical or legal issues
Q2.2.2 Will all your data be openly accessible? true
openly accessible data
Data type Reason Url
Q2.2.2a Please indicate the types of data that are closed and the reason.
Q2.2.3 How will the data be made available? User can select from a list of repositories where the data would be stored. If the repository is not specified the user can select ‘not listed’
Comments
Not listed true
Url
Available data
Q2.2.4 Is the storage sufficiently secure for the data and does the storage provide backup and recovery procedures? insecure_backup_recovery insecure_nobackup_norecovery
Q2.2.4a Please describe the reason you chose an insecure repository
Q2.2.4a Please describe the reason you chose an insecure repository without backup or recovery
Storage sufficiently secure
Q2.2.5 Will you provide methods and tools to access the data? true true true true The user can select ‘yes’ or ‘no’ for the methods. There is a ‘comments’ field for the user to provide additional information.
Comments
Q2.2.5 Will you provide methods and tools to access the data?
<visible style=""/> <extendedDescription/> <viewStyle cssClass="" renderstyle="freetext"/> <description/> </field> <field defaultVisibility="false" id="urlA2225a" ordinal="2"> <title>Url
Comments
Q2.2.5a Please provide links describing the methods for accessing the data.
tool Url
Comments
Q2.2.5b Please provide links describing the tools for accessing the data.
Q2.2.6 Will you also make auxiliary data that may be of interest to researchers available? never User is presented with a list of options: ‘no auxiliary data’, ‘after publication’, ‘at end of project’, ‘never’. There is a ‘comments’ field for users to provide additional information.
Comments
Reason
<description/> <extendedDescription/> </fieldGroup> </fieldGroups> <title>2.2 Making data openly accessible
Q2.3.1 Will you use a standard vocabulary for your data types? User is presented with a selection of ‘all data types’, ‘some data types’, ‘none’. A ‘comments’ field is also provided for additional information.
Q2.3.1a Will you provide a mapping to more commonly used ontologies?
<description/> <extendedDescription/> </fieldGroup> </fieldGroups> <title>2.3 Making data interoperable
2 Fair Data