argos/dmp-frontend/databaseviewstyle.xml

1165 lines
49 KiB
XML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?xml version="1.0" standalone="no"?>
<root>
<sections>
<section defaultVisibility="true" id="datasummary" ordinal="1" page="0">
<sections/>
<fieldGroups>
<fieldGroup defaultVisibility="true" id="dataSummaryGroup" ordinal="1" page="0">
<fieldsets>
<fieldSet id="dataSummaryFS" ordinal="1">
<fields>
<field defaultVisibility="true" id="dataSummary" ordinal="1">
<title/>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Data Summary</title>
<description/>
<extendedDescription/>
</fieldGroup>
</fieldGroups>
<title>Data Summary</title>
<extendedDescription/>
<description/>
</section>
<section defaultVisibility="true" id="fairData" ordinal="2" page="0">
<sections>
<section defaultVisibility="true" id="dataMetadata" ordinal="1" page="0">
<sections>
<section defaultVisibility="true" id="" ordinal="0" page="0">
<sections/>
<fieldGroups/>
<title/>
<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?</title>
<visible style="">
<rule ruleStyle="" target="metadataStandarsA211FS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="notlistedA211FS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="noMetadataFS" type="field value">
<value type="boolean">false</value>
</rule>
<rule ruleStyle="" target="freeOfChargeGroupQ211bFS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="metadataHarvestableQ211cFS" type="field value">
<value type="boolean">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description>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.</description>
</field>
</fields>
</fieldSet>
<fieldSet id="metadataStandarsA211FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="metadataStandarsA211" ordinal="1">
<title>Metadata standards</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description>The data will be described by metadata that follows the metadata standards described in &lt;url1&gt;, &lt;url2&gt;</description>
<data type="autocomplete" url="http://rd-alliance.github.io/metadata-directory">
<options/>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="notlistedA211FS" ordinal="3">
<fields>
<field defaultVisibility="true" id="notlistedA211" ordinal="1">
<title>Not listed</title>
<visible style="">
<rule ruleStyle="" target="notlistedUrlA211FS" type="field value">
<value type="">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="checkBox"/>
<description/>
<data label=""/>
</field>
</fields>
</fieldSet>
<fieldSet id="notlistedUrlA211FS" ordinal="4">
<fields>
<field defaultVisibility="true" id="notlistedUrlA211" ordinal="1">
<title>Url</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description>URL to the description of the metadata scheme used</description>
</field>
</fields>
</fieldSet>
<fieldSet id="noMetadataFS" ordinal="1">
<fields>
<field defaultVisibility="true" id="noMetadata" ordinal="1">
<title>The data will not be described by any metadata</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="checkBox"/>
<description/>
<data label=""/>
</field>
</fields>
</fieldSet>
<fieldSet id="CommentA211FS" ordinal="6">
<fields>
<field defaultVisibility="true" id="CommentA211" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="useVocabulariesQ211aFS" ordinal="7">
<fields>
<field defaultVisibility="true" id="useVocabulariesQ211a" ordinal="1">
<title>Q2.1.1a Will your metadata use standardised vocabularies?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description>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.</description>
<data type="wordlist" url="">
<options>
<option label="standardised vocabularies" value="standardised vocabularies"/>
</options>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="notlistedVocabularyA211aFS" ordinal="8">
<fields>
<field defaultVisibility="true" id="notlistedVocabularyA211a" ordinal="1">
<title>Not listed</title>
<visible style="">
<rule ruleStyle="" target="urlA211aFS" type="field value">
<value type="">true</value>
</rule>
<rule ruleStyle="" target="descA211aFS" type="field value">
<value type="">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="checkBox"/>
<description/>
<data label=""/>
</field>
</fields>
</fieldSet>
<fieldSet id="noMetadataVocabularyA211aFS" ordinal="9">
<fields>
<field defaultVisibility="true" id="noMetadataVocabularyA211a" ordinal="1">
<title>None</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="checkBox"/>
<description>The metadata will not make use of any vocabulary</description>
<data label=""/>
</field>
</fields>
</fieldSet>
<fieldSet id="urlDescA211aFS" ordinal="10">
<fields>
<field defaultVisibility="true" id="urlA211a" ordinal="1">
<title>Url</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
<field defaultVisibility="true" id="descA211a" ordinal="2">
<title>Description</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="freeOfChargeQ211b" ordinal="11">
<fields>
<field defaultVisibility="true" id="freeOfChargeGroupQ211b" ordinal="1">
<title>Q2.1.1b Will you make the metadata available free-of-charge?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description>User is presented with a yes or no along with a comments field for additional information.</description>
</field>
</fields>
</fieldSet>
<fieldSet id="metadataHarvestableQ211cFS" ordinal="12">
<fields>
<field defaultVisibility="true" id="metadataHarvestableQ211c" ordinal="0">
<title>Q2.1.1c Will your metadata be harvestable?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title/>
<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?</title>
<visible style="">
<rule ruleStyle="" target="namingConventionUrlA212FS" type="field value">
<value type="boolean">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description>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.</description>
</field>
</fields>
</fieldSet>
<fieldSet id="namingConventionUrlA212FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="namingConventionUrlA212" ordinal="1">
<title>Url</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="namingConventionCommentsA212FS" ordinal="3">
<fields>
<field defaultVisibility="true" id="namingConventionCommentsA212" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Naming convention</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="versionGroup" ordinal="3" page="0">
<fieldsets>
<fieldSet id="versionNumberQ213FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="versionNumberQ213" ordinal="1">
<title>Q2.1.3 Will you provide clear version numbers for your data?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description>User selects a yes or no response. There should be a comments field for the user to add additional notes.</description>
</field>
</fields>
</fieldSet>
<fieldSet id="commentsA213FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="commentsA213" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Version numbers</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="persistentIdentifiersGroup" ordinal="4" page="0">
<fieldsets>
<fieldSet id="persistentIdentifiersQ214FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="persistentIdentifiersQ214" ordinal="1">
<title>Q2.1.4 Will you provide persistent identifiers for your data?</title>
<visible style="">
<rule ruleStyle="" target="persistentIdentifiersListA214FS" type="field value">
<value type="boolean">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description>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.</description>
</field>
</fields>
</fieldSet>
<fieldSet id="persistentIdentifiersListA214FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="persistentIdentifiersListA214" ordinal="1">
<title>The data will be issued with &lt;identifier type&gt; identifiers once the data has reached an approved level of maturity for consumption by interested parties.</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description/>
<data type="wordlist" url="">
<options>
<option label="DOI" value="doi"/>
<option label="Persistent Unique Identifier" value="Persistent_Unique_Identifier"/>
</options>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="persistentIdentifiersCommentsA214FS" ordinal="3">
<fields>
<field defaultVisibility="true" id="persistentIdentifiersCommentsA214" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Persistent identifiers</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="searchableMetadataGroup" ordinal="5" page="0">
<fieldsets>
<fieldSet id="searchableMetadataQ215FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="searchableMetadataQ215" ordinal="1">
<title>Q2.1.5 Will you provide searchable metadata for your data?</title>
<visible style="">
<rule ruleStyle="" target="servicesToSearchableQ215aFS" type="field value">
<value type="boolean">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description>Users are given the choices: yes and no. There should be a comments field to allow users to provide additional information.</description>
</field>
</fields>
</fieldSet>
<fieldSet id="servicesToSearchableQ215aFS" ordinal="2">
<fields>
<field defaultVisibility="true" id="servicesToSearchableQ215a" ordinal="1">
<title>Q2.1.5a What services will you use to provide searchable metadata?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description>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. </description>
<data type="autocomplete" url="">
<options/>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="notlistedA215FS" ordinal="3">
<fields>
<field defaultVisibility="true" id="notlistedA215" ordinal="1">
<title>Not listed</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="checkBox"/>
<description/>
<data label=""/>
</field>
</fields>
</fieldSet>
<fieldSet id="urlNameA215aFS" ordinal="4">
<fields>
<field defaultVisibility="true" id="urlA215a" ordinal="1">
<title>Url</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
<field defaultVisibility="true" id="nameA215a" ordinal="2">
<title>Name</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Searchable metadata</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="standardisedFormatsGroup" ordinal="6" page="0">
<fieldsets>
<fieldSet id="standardisedFormatsQ216FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="standardisedFormatsQ216" ordinal="1">
<title>Q2.1.6 Will you use standardised formats for some or all of your data?</title>
<visible style="">
<rule ruleStyle="" target="standardisedFormatsQ216aFS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="otherA216aFS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="commentsA216aFS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="formatsStoreDataQ216bFS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="nameUrlA216bFS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="usedFormatFS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="commentsA216bFS" type="field value">
<value type="boolean">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="commnetsA216FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="commnetsA216" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="standardisedFormatsQ216aFS" ordinal="3">
<fields>
<field defaultVisibility="true" id="standardisedFormatsQ216a" ordinal="1">
<title>Q2.1.6a Which standardised data formats do you plan on using?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description>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.</description>
<data type="autocomplete" url="">
<options/>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="otherA216aFS" ordinal="4">
<fields>
<field defaultVisibility="true" id="otherA216a" ordinal="1">
<title>Other</title>
<visible style="">
<rule ruleStyle="" target="urlA216aFS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="nameA216aFS" type="field value">
<value type="boolean">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="checkBox"/>
<description/>
<data label=""/>
</field>
</fields>
</fieldSet>
<fieldSet id="commentsA216aFS" ordinal="5">
<fields>
<field defaultVisibility="true" id="commentsA216a" ordinal="1">
<title>Commnets</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="urlNameA216a" ordinal="6">
<fields>
<field defaultVisibility="true" id="urlA216a" ordinal="1">
<title>Url</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
<field defaultVisibility="true" id="nameA216a" ordinal="2">
<title>Name</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="formatsStoreDataQ216bFS" ordinal="7">
<fields>
<field defaultVisibility="false" id="formatsStoreDataQ216b" ordinal="1">
<title>Q2.1.6b Please describe the formats you plan to store your data in, including any URLs to documentation.</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description>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 its a commonly used format in their field. There should be a comments field to allow the user to add additional information.</description>
</field>
</fields>
</fieldSet>
<fieldSet id="nameUrlA216bFS" ordinal="8">
<fields>
<field defaultVisibility="false" id="nameA216b" ordinal="1">
<title>Name</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
<field defaultVisibility="false" id="urlA216b" ordinal="2">
<title>Url</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="usedFormatFS" ordinal="9">
<fields>
<field defaultVisibility="false" id="usedFormat" ordinal="1">
<title> its a commonly used format</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="checkBox"/>
<description/>
<data label=""/>
</field>
</fields>
</fieldSet>
<fieldSet id="commentsA216bFS" ordinal="10">
<fields>
<field defaultVisibility="false" id="commentsA216b" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Standardised formats</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="fileFormatsOpenGroup" ordinal="7" page="0">
<fieldsets>
<fieldSet id="fileFormatsOpenQ217FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="fileFormatsOpenQ217" ordinal="1">
<title>Q2.1.7 Are the file formats you will use open?</title>
<visible style="">
<rule ruleStyle="" target="notOpenFormatQ217aFS" type="field value">
<value type="boolean">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description>User presented with a choice of all, some, none. There should be a comments field for additional information.</description>
<data type="wordlist" url="">
<options>
<option label="all" value="all"/>
<option label="some" value="some"/>
<option label="none" value="none"/>
</options>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="commentsA217FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="commentsA217" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="notOpenFormatQ217aFS" ordinal="3">
<fields>
<field defaultVisibility="false" id="notOpenFormatQ217a" ordinal="1">
<title/>
<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</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="openSourceToolsGroup" ordinal="0" page="0">
<fieldsets>
<fieldSet id="openSourceToolsQ218FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="openSourceToolsQ218" ordinal="1">
<title>Q2.1.8 Do supported open-source tools exist for accessing the data?</title>
<visible style="">
<rule ruleStyle="" target="proprietaryToolsQ218aFS" type="field value">
<value type="string">for_some_data</value>
</rule>
<rule ruleStyle="" target="proprietaryToolsQ218aFS" type="field value">
<value type="string"/>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description>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.</description>
<data type="wordlist" url="">
<options>
<option label="for all data" value="for_all_data"/>
<option label="for some data" value="for_some_data"/>
<option label="for no data" value="for_no_data"/>
</options>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="commentsA218FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="commentsA218" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="proprietaryToolsQ218aFS" ordinal="3">
<fields>
<field defaultVisibility="false" id="proprietaryToolsQ218a" ordinal="1">
<title>Q2.1.8a Please describe which data are require proprietary tools to access the data?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Open source Tools</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="QualityOfTheDataGroup" ordinal="9" page="0">
<fieldsets>
<fieldSet id="metadataQualtiyQ219FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="metadataQualtiyQ219" ordinal="1">
<title>Q2.1.9 Will you provide metadata describing the quality of the data?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description>User is presented with a yes, no choice along with a comments field for additional information.</description>
</field>
</fields>
</fieldSet>
<fieldSet id="commentsA219FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="commentsA219" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Quality Of Tha Data</title>
<description/>
<extendedDescription/>
</fieldGroup>
</fieldGroups>
<title>2.1 Making data findable, including provisions for metadata</title>
<extendedDescription/>
<description/>
</section>
<section defaultVisibility="true" id="dataOpenlyAccessible" ordinal="4" page="0">
<sections/>
<fieldGroups>
<fieldGroup defaultVisibility="true" id="ethicalorLegalIssuesGroup" ordinal="1" page="0">
<fieldsets>
<fieldSet id="ethicalLegalIssuesQ221FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="ethicalLegalIssuesQ221" ordinal="1">
<title>Q2.2.1 Are there ethical or legal issues that can impact sharing the data?</title>
<visible style="">
<rule ruleStyle="" target="ethicalLegalRestrictions" type="field value">
<value type="boolean">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description>User is presented with a yes, no. A comments field should be provided for the user to provide any additional information.</description>
</field>
</fields>
</fieldSet>
<fieldSet id="ethicalLegalIssuesA221FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="ethicalLegalIssuesA221" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="ethicalLegalRestrictionsFS" ordinal="3">
<fields>
<field defaultVisibility="false" id="ethicalLegalRestrictions" ordinal="1">
<title>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.</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>ethical or legal issues</title>
<description>ethical or legal issues</description>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="openlyAccessibleGroup" ordinal="2" page="0">
<fieldsets>
<fieldSet id="openlyAccessibleQ222FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="openlyAccessibleQ222" ordinal="1">
<title>Q2.2.2 Will all your data be openly accessible?</title>
<visible style="">
<rule ruleStyle="" target="closedReasonQ222aGroup" type="field value">
<value type="boolean">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description/>
<data type="wordlist" url="">
<options>
<option label="all" value="all"/>
<option label="some" value="some"/>
<option label="none" value="none"/>
</options>
</data>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>openly accessible data</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="false" id="closedReasonQ222aGroup" ordinal="3" page="0">
<fieldsets>
<fieldSet id="closedReasonQ222aFS" ordinal="1">
<fields>
<field defaultVisibility="false" id="dataTypeA222a" ordinal="1">
<title>Data type</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
<field defaultVisibility="false" id="reasonA222a" ordinal="2">
<title>Reason</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
<field defaultVisibility="false" id="urlΑ222a" ordinal="3">
<title>Url</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Q2.2.2a Please indicate the types of data that are closed and the reason.</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="HowDataBeavailableGroup" ordinal="4" page="0">
<fieldsets>
<fieldSet id="howdataAvailableQ223FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="howdataAvailableQ223" ordinal="1">
<title>Q2.2.3 How will the data be made available?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description>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</description>
<data type="autocomplete" url="http://eestore.paas2.uninett.no/api/datarepo/">
<options/>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="commentsA223FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="commentsA223" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="notlistedRepositoryA223FS" ordinal="3">
<fields>
<field defaultVisibility="true" id="notlistedRepositoryA223" ordinal="1">
<title>Not listed</title>
<visible style="">
<rule ruleStyle="" target="urlRepositoryA223FS" type="field value">
<value type="">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="checkBox"/>
<description/>
<data label=""/>
</field>
</fields>
</fieldSet>
<fieldSet id="urlRepositoryA223FS" ordinal="4">
<fields>
<field defaultVisibility="false" id="urlRepositoryA223" ordinal="1">
<title>Url</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Available data</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="storageSufficientlySecureGroup" ordinal="5" page="0">
<fieldsets>
<fieldSet id="storageSufficientlySecureQ224FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="storageSufficientlySecureQ224" ordinal="1">
<title>Q2.2.4 Is the storage sufficiently secure for the data and does the storage provide backup and recovery procedures?</title>
<visible style="">
<rule ruleStyle="" target="insecureBackUpRecoveryA224FS" type="field value">
<value type="">insecure_backup_recovery</value>
</rule>
<rule ruleStyle="" target="insecureNoBackUpOrRecoveryA224FS" type="field value">
<value type="">insecure_nobackup_norecovery</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description/>
<data type="wordlist" url="">
<options>
<option label="secure with backup and recovery" value="secure_backup_security"/>
<option label="secure with no backup and recovery" value="secure_noBackup"/>
<option label="insecure with backup and recovery" value="insecure_backup_recovery"/>
<option label="insecure with no backup or recovery" value="insecure_nobackup_norecovery"/>
</options>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="insecureBackUpRecoveryA224FS" ordinal="2">
<fields>
<field defaultVisibility="false" id="insecureBackUpRecoveryA224" ordinal="1">
<title>Q2.2.4a Please describe the reason you chose an insecure repository</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="insecureNoBackUpOrRecoveryA224FS" ordinal="3">
<fields>
<field defaultVisibility="false" id="insecureNoBackUpOrRecoveryA224" ordinal="1">
<title>Q2.2.4a Please describe the reason you chose an insecure repository without backup or recovery</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title> Storage sufficiently secure</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="MethodsToolsToAccessDataGroup" ordinal="6" page="0">
<fieldsets>
<fieldSet id="methodsToolsToAccessDataQ225FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="methodsToolsToAccessDataQ225" ordinal="1">
<title>Q2.2.5 Will you provide methods and tools to access the data?</title>
<visible style="">
<rule ruleStyle="" target="linksForMethodsQ225aGroup" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="commentsA225bFS" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="toolsUrlsQ225bGroup" type="field value">
<value type="boolean">true</value>
</rule>
<rule ruleStyle="" target="commentsA225aFS" type="field value">
<value type="boolean">true</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description>The user can select yes or no for the methods. There is a comments field for the user to provide additional information.</description>
</field>
</fields>
</fieldSet>
<fieldSet id="commentsA225FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="commentsA225FS" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Q2.2.5 Will you provide methods and tools to access the data?</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="false" id="linksForMethodsQ225aGroup" ordinal="7" page="0">
<fieldsets>
<fieldSet id="methodUrlA225aFS" ordinal="1">
<fields>
<field defaultVisibility="false" id="methodA225a" ordinal="1">
<title/>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
<field defaultVisibility="false" id="urlA2225a" ordinal="2">
<title>Url</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="commentsA225aFS" ordinal="3">
<fields>
<field defaultVisibility="false" id="commentsA225a" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Q2.2.5a Please provide links describing the methods for accessing the data.</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="false" id="toolsUrlsQ225bGroup" ordinal="8" page="0">
<fieldsets>
<fieldSet id="toolsUrlsQ225bFS" ordinal="1">
<fields>
<field defaultVisibility="false" id="toolA225b" ordinal="1">
<title>tool</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
<field defaultVisibility="false" id="urlA225b" ordinal="2">
<title>Url</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="commentsA225bFS" ordinal="2">
<fields>
<field defaultVisibility="false" id="commentsA225b" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="freetext"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title>Q2.2.5b Please provide links describing the tools for accessing the data.</title>
<description/>
<extendedDescription/>
</fieldGroup>
<fieldGroup defaultVisibility="true" id="auxiliaryDataGroup" ordinal="9" page="0">
<fieldsets>
<fieldSet id="auxiliaryDataQ226FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="auxiliaryDataQ226" ordinal="1">
<title>Q2.2.6 Will you also make auxiliary data that may be of interest to researchers available?</title>
<visible style="">
<rule ruleStyle="" target="reasonA226FS" type="field value">
<value type="string">never</value>
</rule>
</visible>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description>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.</description>
<data type="wordlist" url="">
<options>
<option label="no auxiliary data" value="no_auxiliary_data"/>
<option label="after publication" value="after_publication"/>
<option label="at end of project" value="at_end_of_project"/>
<option label="never" value="never"/>
</options>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="commnetsA226FS" ordinal="2">
<fields>
<field defaultVisibility="true" id="commnetsA226" ordinal="1">
<title>Comments</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
<fieldSet id="reasonA226FS" ordinal="3">
<fields>
<field defaultVisibility="false" id="reasonA226" ordinal="1">
<title>Reason</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="textarea"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title/>
<description/>
<extendedDescription/>
</fieldGroup>
</fieldGroups>
<title>2.2 Making data openly accessible</title>
<extendedDescription/>
<description/>
</section>
<section defaultVisibility="true" id="data_interoperable" ordinal="5" page="0">
<sections/>
<fieldGroups>
<fieldGroup defaultVisibility="true" id="vocabularyDataTypesGroup" ordinal="1" page="0">
<fieldsets>
<fieldSet id="vocabularyDataTypesQ231FS" ordinal="1">
<fields>
<field defaultVisibility="true" id="vocabularyDataTypesQ231" ordinal="1">
<title>Q2.3.1 Will you use a standard vocabulary for your data types?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="combobox"/>
<description>User is presented with a selection of all data types, some data types, none. A comments field is also provided for additional information.</description>
<data type="wordlist" url="">
<options>
<option label="all data types" value="all_data_types"/>
<option label="some data types" value="some_data_types"/>
<option label="none" value="none"/>
</options>
</data>
</field>
</fields>
</fieldSet>
<fieldSet id="mappingOntologiesQ231aFS" ordinal="2">
<fields>
<field defaultVisibility="false" id="mappingOntologiesQ231a" ordinal="2">
<title>Q2.3.1a Will you provide a mapping to more commonly used ontologies?</title>
<visible style=""/>
<extendedDescription/>
<viewStyle cssClass="" renderstyle="booleanDecision"/>
<description/>
</field>
</fields>
</fieldSet>
</fieldsets>
<title/>
<description/>
<extendedDescription/>
</fieldGroup>
</fieldGroups>
<title>2.3 Making data interoperable</title>
<extendedDescription/>
<description/>
</section>
</sections>
<fieldGroups/>
<title>2 Fair Data</title>
<extendedDescription/>
<description/>
</section>
</sections>
</root>