Answer to the text area question for plan 1
Line 2
Line 3
Questions to consider:
Guidance:
List any other relevant funder, institutional, departmental or group policies on data management, data sharing and data security. Some of the information you give in the remainder of the DMP will be determined by the content of other policies. If so, point/link to them here.
" - themes: related_policies - -existing_data: - text: "Questions to consider:
Guidance:
Check to see if there are any existing data that you can reuse, for examples by consulting relevant repositories.
When creating new data sources, explain why existing data sources cannot be re-used.
A list of repositories is provided by Databib or Re3data .
" - themes: existing_data - -licensing_of_existing_data: - text: "Questions to consider:
Guidance:
If purchasing or reusing existing data sources, explain how issues such as copyright and IPR have been addressed.
" - themes: licensing_of_existing_data - -relationship_to_existing_data: - text: "Questions to consider:
Guidance:
Consider the relationship between the data that you will capture and existing data available in public repositories or elsewhere.
" - themes: relationship_to_existing_data - -description_of_data_content: - text: "Questions to consider:
Guidance:
Give a brief description of the data that will be created, noting its content and coverage
" - themes: description_of_data_content - -data_format: - text: "Questions to consider:
Guidance:
Outline and justify your choice of format e.g. SPSS, Open Document Format, tab-delimited format, MS Excel.
Decisions may be based on staff expertise, a preference for Open formats, the standards accepted by data centres or widespread usage with a given community. Using standardised and interchangeable or open lossless data formats ensures the long-term usability of data.
See UKDA Guidance on recommended data formats.
" - themes: data_format - -data_volumes: - text: "Questions to consider:
Guidance:
Consider the implications of data volumes in terms of storage, backup and access.
Estimate the volume of data in KB/MB/GB and how this will grow to make sure any additional storage and technical support required can be provided.
" - themes: data_volumes - -data_type: - text: "Questions to consider:
Guidance:
Outline the types of data that are expected to be produced from the project e.g. quantitative, qualitative, survey data, experimental measurements, models, images, audiovisual data, samples…
Include the raw data arising directly from the research, the reduced data derived from it, and published data.
" - themes: data_type - -data_capture_methods: - text: "Questions to consider:
Guidance:
Outline how the data will be collected/generated and which community data standards (if any) will be used at this stage.
" - themes: data_capture_methods - -data_organisation: - text: "Questions to consider:
Guidance:
Indicate how the data will be organised during the project, mentioning for example naming conventions, version control and folder structures. Consistent, well-ordered research data will be easier for the research team to find, understand and reuse.
" - themes: data_organisation - -data_quality: - text: "Questions to consider:
Guidance:
Explain how the consistency and quality of data collection will be controlled and documented.
This may include processes such as calibration, repeat samples or measurements, standardised data capture or recording, data entry validation, peer review of data or representation with controlled vocabularies.
" - themes: data_quality - -documentation: - text: "Questions to consider:
Guidance:
Describe the types of documentation that will accompany the data to provide a secondary users with any necessary details to prevent misuse, misinterpretation or confusion. This may include information on the methodology used to collect the data, analytical and procedural information, definitions of variables, units of measurement, any assumptions made, the format and file type of the data.
" - themes: documentation - -metadata_capture: - text: "Questions to consider:
Guidance:
Metadata should be created to describe the data and aid discovery. Consider how you will capture this information and where it will be recorded e.g. in a database with links to each item, in a ‘readme’ text file, in file headers.
" - themes: metadata_capture - -metadata_standards: - text: "Questions to consider:
Guidance:
Researchers are strongly encouraged to utilise community standards to describe and structure data, where these are in place. The DCC offers a catalogue of disciplinary metadata standards.
" - themes: metadata_standards - -discovery_by_users: - text: "Questions to consider:
Guidance:
Indicate how potential new users can find out about your data and identify whether they could be suitable for their research purposes. For example, you may provide basic discovery metadata online, such as title, author, subjects, keywords and publisher.
" - themes: discovery_by_users - -ethical_issues: - text: "Questions to consider:
Guidance:
Investigators carrying out research involving human participants must ensure that consent is obtained to share data. Managing ethical concerns may include: anonymisation of data; referral to departmental or institutional ethics committees; and formal consent agreements. Ethical issues may affect how you store data, who can see/use it and how long it is kept. You should show that you’re aware of this and have planned accordingly.
See UKDA Guidance on Consent, Confidentiality and Ethics.
" - themes: ethical_issues - -ipr_ownership_and_licencing: - text: "Questions to consider:
Guidance:
State who will own the copyright and IPR of any new data that you will generate. For multi-partner projects, IPR ownership may be worth covering in a consortium agreement. Outline any restrictions needed on data sharing e.g. to protect proprietary or patentable data.
See DCC How to license research data.
" - themes: ipr_ownership_and_licencing - -active_data_storage: - text: "Questions to consider:
Guidance:
Storing data on laptops, computer hard drives or external storage devices alone is very risky. The use of robust, managed storage provided by university IT teams is preferable.
See UKDA Guidance on Data Storage.
" - themes: active_data_storage - -backup_procedures: - text: "Questions to consider:
Guidance:
Describe the data back-up procedures that you will adopt to ensure the data and metadata are securely stored during the lifetime of the project. You may need to discuss your institution’s policy on back-ups. It is better to use automatic backup services provided by university IT than rely on manual processes.
See UKDA Guidance on Data Backup.
" - themes: backup_procedures - -data_security: - text: "Questions to consider:
Guidance:
If your data is sensitive (e.g. detailed personal data, politically sensitive information or trade secrets) you should discuss any appropriate security measures that you will be taking. Note the main risks and how these will be managed. Identify any formal standards that you will comply with e.g. ISO 27001.
See DCC Briefing Paper on Information Security Management - ISO 27000.
See UKDA Guidance on Data Security.
" - themes: data_security - -data_selection: - text: "Questions to consider:
Guidance:
Indicate which data you intend to preserve beyond the period of funding. This should be based on what has long-term value and is economically viable to keep. Consider how long you wish to keep the data and what will happen to it e.g. deposit in a data repository to enable reuse.
See DCC How to appraise and select research data.
" - themes: data_selection - -preservation_plan: - text: "Questions to consider:
Guidance:
Researchers should consider how datasets that have long-term value will be preserved and curated beyond the lifetime of the grant. Also outline the plans for preparing and documenting data for sharing and archiving.
If you do not propose to use an established repository, the data management plan should demonstrate that resources and systems will be in place to enable the data to be curated effectively beyond the lifetime of the grant.
" - themes: preservation_plan - -period_of_preservation: - text: "Questions to consider:
Guidance:
This may depend on the type of data. Most research funders expect data to be retained for a minimum of 10 years from the end of the project. For data that by their nature cannot be re-measured, efforts should be made to retain them indefinitely.
" - themes: period_of_preservation - -data_repository: - text: "Questions to consider:
Guidance:
Most research funders recommend the use of established data repositories, community databases and related initiatives to aid data preservation, sharing and reuse.
An international list of data repositories is available via Databib or Re3data.
" - themes: data_repository - -audience: - text: "Questions to consider:
Guidance:
Where possible outline the types of users you expect and estimate numbers.
" - themes: audiencethe - -expected_reuse: - text: "Questions to consider:
Guidance:
You should think about the possibilities for re-use of your data in other contexts and by other users, and connect this as appropriate with your plans for dissemination and Pathways to Impact. Where there is potential for reuse, you should use standards and formats that facilitate this.
" - themes: expected_reuse - -method_for_data_sharing: - text: "Questions to consider:
Guidance:
Consider where, how, and to whom the data should be made available. Will you share data via a data repository, handle data requests directly or use another mechanism?
The methods used to share data will be dependent on a number of factors such as the type, size, complexity and sensitivity of data. Mention earlier examples to show a track record of effective data sharing.
" - themes: method_for_data_sharing - -timeframe_for_data_sharing: - text: "Questions to consider:
Guidance:
Data (with accompanying metadata) should be shared in a timely fashion. It is generally expected that timely release would generally be no later than the release through publication of the main findings and should be in-line with established best practice in the field.
" - themes: timeframe_for_data_sharing - -embargo_period: - text: "Questions to consider:
Guidance:
The value of data often depends on timeliness. Researchers have a legitimate interest in benefiting from their investment of time and effort in producing data, but not in prolonged exclusive use. Research funders typically allow embargoes in line with practice in the field, but expect these to be outlined and justified.
" - themes: embargo_period - -restrictions_on_sharing: - text: "Questions to consider:
Guidance:
Outline any expected difficulties in data sharing, along with causes and possible measures to overcome these. Restrictions to data sharing may be due to participant confidentiality, consent agreements or IPR. Strategies to limit restrictions may include: anonymising or aggregating data; gaining participant consent for data sharing; gaining copyright permissions; and agreeing a limited embargo period.
" - themes: restrictions_on_sharing - -managed_access_procedures: - text: "Questions to consider:
Guidance:
Indicate whether external users are (will be) bound by data sharing agreements, licenses or end-user agreements. If so, set out the terms and key responsibilities to be followed.
Note how access will be controlled, for example by the use of specialist services. A data enclave provides a controlled secure environments in which eligible researchers can perform analyses using restricted data resources.
Where a managed access process is required, the procedure should be clearly described and transparent.
" - themes: managed_access_procedures - -responsibilities: - text: "Questions to consider:
Guidance:
Outline the roles and responsibilities for all activities e.g. data capture, metadata production, data quality, storage and backup, data archiving & data sharing. Individuals should be named where possible. For collaborative projects you should explain the co-ordination of data management responsibilities across partners.
See UKDA Guidance on data management roles and responsibilities.
" - themes: responsibilities - -resourcing_skills_and_training: - text: "Questions to consider:
Guidance:
Carefully consider any resources needed to deliver the plan. Where dedicated resources are needed, these should be outlined and justified.
Outline any relevant technical expertise, support and training that is likely to be required and how it will be acquired.
" - themes: resourcing_skills_and_training - -resourcing_hardware_and_software: - text: "Questions to consider:
Guidance:
Carefully consider any resources needed to deliver the plan. Where dedicated resources are needed, these should be outlined and justified.
Provide details and justification for any hardware or software which will be used to support the project’s research methodology, which is additional or exceptional to conventional desk-based research and institutional provision. This includes additional storage and backup costs that may be charged by IT services.
" - themes: resourcing_hardware_and_software - -resourcing_preservation_and_data_sharing: - text: "Questions to consider:
Guidance:
Carefully consider any resources needed to deliver the plan. Where dedicated resources are needed, these should be outlined and justified.
Funding should be included to cover any charges applied by data repositories, for example to handle data of exceptional size or complexity. Also remember to cost in time and effort to prepare data for deposit and ensure it is adequately documented to enable reuse.
If you are not depositing in a data repository, ensure you have appropriate resources and systems in place to share and preserve the data.
See UKDA How to cost data management.
" - themes: resourcing_preservation_and_data_sharing - -ahrc_funder_guidance: - text: "sample funder guidance ahrc" - themes: embargo_period - -bbsrc_funder_guidance: - text: "sample funder guidance bbsrc" - themes: embargo_period - -aru_institution_guidance: - text: "sample institution guidance aru" - themes: embargo_period - -au_institution_guidance_1: - text: "sample institution guidance au 1" - themes: embargo_period - -au_institution_guidance_2: - text: "sample instiution guidance au 2" - themes: embargo_period - -bu_institution_guidance_1: - text: "sample institution guidance bu 1" - themes: embargo_period - -bu_institution_guidance_2: - text: "sample institution guidance bu 2" - themes: embargo_period - -one: - text: "one" - themes: embargo_period - - - diff --git a/test/fixtures/identifier_schemes.yml b/test/fixtures/identifier_schemes.yml deleted file mode 100644 index c70bb17..0000000 --- a/test/fixtures/identifier_schemes.yml +++ /dev/null @@ -1,7 +0,0 @@ -<% # Load the org types from thosedefined in the MagicStrings section of the locale %> -<% I18n.t("identifier_schemes.schemes").each do |k,v| %> -<%= k.downcase %>: - name: <%= "#{k}" %> - description: <%= "#{k.downcase}.org - testing" %> - active: true -<% end %> \ No newline at end of file diff --git a/test/fixtures/languages.yml b/test/fixtures/languages.yml deleted file mode 100644 index 55ea794..0000000 --- a/test/fixtures/languages.yml +++ /dev/null @@ -1,17 +0,0 @@ -en-UK: - abbreviation: 'en-UK' - description: 'UK English' - name: 'English (UK)' - default_language: true - -en-US: - abbreviation: 'en-US' - description: 'US English' - name: 'English (US)' - default_language: false - -fr: - abbreviation: 'fr' - description: 'French' - name: 'French' - default_language: false \ No newline at end of file diff --git a/test/fixtures/option_warnings.yml b/test/fixtures/option_warnings.yml deleted file mode 100644 index 46bac23..0000000 --- a/test/fixtures/option_warnings.yml +++ /dev/null @@ -1,40 +0,0 @@ -single_select_1_warning: - option: single_select_1 - organisation: uog - text: This warning should display when option 1 of the single item select box example is selected for a project at the University of Glasgow - -single_select_2_warning: - option: single_select_2 - organisation: hatii - text: This warning should display when option 2 of the single item select box example is selected for a project at HATII - - -multiple_select_3_warning: - option: multiple_select_3 - organisation: uoe - text: This warning should display when option 3 of the multiple item select box example is selected for a project at the University of Edinburgh - -multiple_select_4_warning: - option: multiple_select_4 - organisation: uoe_si - text: This warning should display when option 4 of the multiple item select box example is selected for a project at the School of Informatics - -radio_button_1_warning: - option: radio_button_1 - organisation: uog - text: This warning should display when option 1 of the radio button example is selected for a project at the University of Glasgow - -radio_button_2_warning: - option: radio_button_2 - organisation: hatii - text: This warning should display when option 2 of the radio button example is selected for a project at HATII - -checkbox_3_warning: - option: checkbox_3 - organisation: uoe - text: This warning should display when option 3 of the checkbox example is selected for a project at the University of Edinburgh - -checkbox_4_warning: - option: checkbox_4 - organisation: uoe_si - text: This warning should display when option 4 of the checkbox example is selected for a project at the School of Informatics \ No newline at end of file diff --git a/test/fixtures/options.yml b/test/fixtures/options.yml deleted file mode 100644 index 6824d1d..0000000 --- a/test/fixtures/options.yml +++ /dev/null @@ -1,40 +0,0 @@ -# Produces: -# ----------------------------- -# Generates a set of Options for each question using an appropriate format -# (see sections.yml, questions.yml and question_formats.yml) -# -# [template]_phase_[1..2]_version_[1..2]_section_[1..2]_question_[check_box, etc]_option_[1..2] -# - -# Import sections.yml so that we can dynamically generate sections -<% sections = YAML::load(ERB.new(File.read('./test/fixtures/sections.yml')).result) %> - -<% sections.each do |lbl, hash| %> - <% 2.times.each do |n| %> - -<%= lbl %>_question_radio_button_option_<%= n %>: - question: test_project_1_plan_1_answer_for_radio_button_question - text: <%= (n == 1 ? 'A' : 'B') %> - number: <%= n %> - is_default: <%= (n == 1 ? true : false) %> - -<%= lbl %>_question_check_box_option_<%= n %>: - question: test_project_1_plan_1_answer_for_check_box_question - text: <%= (n == 1 ? 'A' : 'B') %> - number: <%= n %> - is_default: <%= (n == 1 ? true : false) %> - -<%= lbl %>_question_dropdown_option_<%= n %>: - question: test_project_1_plan_1_answer_for_dropdown_question - text: <%= (n == 1 ? 'A' : 'B') %> - number: <%= n %> - is_default: <%= (n == 1 ? true : false) %> - -<%= lbl %>_question_multi_select_box_option_<%= n %>: - question: test_project_1_plan_1_answer_for_multi_select_box_question - text: <%= (n == 1 ? 'A' : 'B') %> - number: <%= n %> - is_default: <%= (n == 1 ? true : false) %> - - <% end %> -<% end %> diff --git a/test/fixtures/organisation_types.yml b/test/fixtures/organisation_types.yml deleted file mode 100644 index c969384..0000000 --- a/test/fixtures/organisation_types.yml +++ /dev/null @@ -1,5 +0,0 @@ -<% # Load the org types from thosedefined in the MagicStrings section of the locale %> -<% I18n.t("magic_strings.organisation_types").each do |k,v| %> -<%= k %>: - name: <%= "#{v}" %> -<% end %> \ No newline at end of file diff --git a/test/fixtures/organisations.yml b/test/fixtures/organisations.yml deleted file mode 100644 index d98f1e2..0000000 --- a/test/fixtures/organisations.yml +++ /dev/null @@ -1,56 +0,0 @@ -# Produces: -# ----------------------------- -# curation_center -# funder -# complete <-- child of curation_center -# -# institution_[1..2] -# school_[1..2] -# project_[1..2] - -# Import organisation_types.yml so that we can dynamically generate organisations -<% organisation_types = YAML::load(ERB.new(File.read('./test/fixtures/organisation_types.yml')).result) %> - -curation_center: - name: 'Curation Centre' - abbreviation: 'cc' - organisation_type: organisation - contact_email: 'admin@example.org' - -funder: - name: 'Grant Funder' - abbreviation: 'funder' - organisation_type: funder - contact_email: 'admin@example-funder.org' - -# We unfortunatley cannot tab this out nicely because YAML is expecting the values in -# the first column -<% organisation_types.each do |lbl, obj| %> - <% unless ['funder', 'organisation'].include?(lbl) %> - <% 2.times do |n| %> - -<%= lbl %>_<%= n + 1 %>: - name: <%= "#{obj['name']} #{n}" %> - domain: <%= "www.#{lbl}-#{n + 1}.org" %> - organisation_type: <%= "#{lbl}" %> - - <% end %> - <% end %> -<% end %> - -complete: - name: 'Organisation with all attributes' - abbreviation: 'complete' - target_url: 'http:\/\/www.complete-org.org' - organisation_type: organisation - domain: 'www.complete-org.org' - wayfless_entity: '' - stylesheet_file_id: 'complete-org.css' - is_other: false - sort_name: 'complete' - banner_text: 'Complete organisation banner text' - region_id: eu - language_id: en-UK - logo_uid: '2016/08/30/1234abcd-complete-org.gif' - logo_name: 'complete-org.gif' - contact_email: 'admin@example.org' \ No newline at end of file diff --git a/test/fixtures/phases.yml b/test/fixtures/phases.yml deleted file mode 100644 index 1a24240..0000000 --- a/test/fixtures/phases.yml +++ /dev/null @@ -1,28 +0,0 @@ -# Produces: -# ----------------------------- -# Generates 1 Phase for each published template and 2 Phases for each one that -# is unpublished (see dmptemplates.yml for template list) -# -# [template]_phase_1 -# [template]_unpublished_phase_[1..2] -# -# - -# Import dmptemplates.yml so that we can dynamically generate phases -<% templates = YAML::load(ERB.new(File.read('./test/fixtures/dmptemplates.yml')).result) %> - -<% templates.each do |lbl, hash| %> - -<%= lbl %>_phase_1: - title: <%= "hash['title'] - Phase 1" %> - number: 1 - dmptemplate: <%= lbl %> - - <% if lbl.include?('_unpublished') %> -<%= lbl %>_phase_2: - title: <%= "hash['title'] - Phase 2" %> - number: 2 - dmptemplate: <%= lbl %> - <% end %> - -<% end %> diff --git a/test/fixtures/plan_sections.yml b/test/fixtures/plan_sections.yml deleted file mode 100644 index b5a70f5..0000000 --- a/test/fixtures/plan_sections.yml +++ /dev/null @@ -1,15 +0,0 @@ -# Read about fixtures at http://api.rubyonrails.org/classes/ActiveRecord/Fixtures.html - -#one: -# edit: false -# at: 2013-06-11 15:17:04 -# user_editing_id: 1 -# section_id: 1 -# plan_id: 1 -# -#two: -# edit: false -# at: 2013-06-11 15:17:04 -# user_editing_id: 1 -# section_id: 1 -# plan_id: 1 diff --git a/test/fixtures/plans.yml b/test/fixtures/plans.yml deleted file mode 100644 index ee53434..0000000 --- a/test/fixtures/plans.yml +++ /dev/null @@ -1,9 +0,0 @@ -<% projects = YAML::load(ERB.new(File.read('./test/fixtures/projects.yml')).result) %> -<% versions = YAML::load(ERB.new(File.read('./test/fixtures/versions.yml')).result) %> - -<% projects.each do |lbl, hash| %> -<%= lbl %>_plan: - project: <%= lbl %> - version: version.first - locked: false -<% end %> \ No newline at end of file diff --git a/test/fixtures/project_groups.yml b/test/fixtures/project_groups.yml deleted file mode 100644 index d0dd7b2..0000000 --- a/test/fixtures/project_groups.yml +++ /dev/null @@ -1,21 +0,0 @@ -# Read about fixtures at http://api.rubyonrails.org/classes/ActiveRecord/Fixtures.html - -#one: -# project_creator: false -# project_editor: false -# user_id: 1 -# project_id: 1 -# -#two: -# project_creator: false -# project_editor: false -# user_id: 1 -# project_id: 1 - -<% 4.times do |n| %> - many_projects_group_<%= n + 1 %>: - project_creator: true - project_editor: true - user: with_many_projects - project: test_plan<%= "_#{n + 1}" if n > 0 %> -<% end %> diff --git a/test/fixtures/projects.yml b/test/fixtures/projects.yml deleted file mode 100644 index 2f21031..0000000 --- a/test/fixtures/projects.yml +++ /dev/null @@ -1,9 +0,0 @@ -<% templates = YAML::load(ERB.new(File.read('./test/fixtures/dmptemplates.yml')).result) %> - -<% templates.each do |lbl, hash| %> -<%= lbl %>_project: - title: <%= "#{lbl} Project" %> - dmptemplate: <%= lbl %> - organisation: complete - visibility: 1 -<% end %> \ No newline at end of file diff --git a/test/fixtures/question_formats.yml b/test/fixtures/question_formats.yml deleted file mode 100644 index ebeacc0..0000000 --- a/test/fixtures/question_formats.yml +++ /dev/null @@ -1,23 +0,0 @@ -question_format_text_area: - title: 'Text Area' - description: 'Text area' - -question_format_text_field: - title: 'Text Field' - description: 'Text field' - -question_format_radio_button: - title: 'Radio Button' - description: 'Radio buttons' - -question_format_check_box: - title: 'Check Box' - description: 'Check boxes' - -question_format_dropdown: - title: 'Dropdown' - description: 'Select box' - -question_format_multi_select: - title: 'Multi Select Box' - description: 'Multi Select box' \ No newline at end of file diff --git a/test/fixtures/questions.yml b/test/fixtures/questions.yml deleted file mode 100644 index 21a3d06..0000000 --- a/test/fixtures/questions.yml +++ /dev/null @@ -1,67 +0,0 @@ -# Produces: -# ----------------------------- -# Generates a Question for each question format for each Section -# (see dmptemplates.yml, phases.yml, versions.yml, sections.yml and question_formats.yml) -# -# [template]_phase_[1..2]_version_[1..2]_section_[1..2]_question_[text_area, text_field, etc] -# [template]_unpublished_phase_[1..2]_version_[1..2]_section_[1..4]_question_[text_area, etc] -# - -# Import sections.yml so that we can dynamically generate sections -<% sections = YAML::load(ERB.new(File.read('./test/fixtures/sections.yml')).result) %> - -<% sections.each do |lbl, hash| %> -<%= lbl %>_question_text_area: - text: 'Question with Text Area' - default_value: 'Default value for text area' - guidance: 'Guidance for text area' - number: 1 - section: <%= lbl %> - question_format: question_format_text_area - option_comment_display: true - -<%= lbl %>_question_text_field: - text: 'Question with Text Field' - default_value: 'Default value for text field' - guidance: 'Guidance for text field' - number: 2 - section: <%= lbl %> - question_format: question_format_text_field - option_comment_display: true - -<%= lbl %>_question_radio_button: - text: 'Question with Radio Buttons' - default_value: 'Default value for radio buttons' - guidance: 'Guidance for radio buttons' - number: 3 - section: <%= lbl %> - question_format: question_format_radio_button - option_comment_display: true - -<%= lbl %>_question_check_box: - text: 'Question with Check Boxes' - default_value: 'Default value for check boxes' - guidance: 'Guidance for check boxes' - number: 4 - section: <%= lbl %> - question_format: question_format_check_box - option_comment_display: true - -<%= lbl %>_question_dropdown: - text: 'Question with Select Box' - default_value: 'Default value for select box' - guidance: 'Guidance for Select Box' - number: 5 - section: <%= lbl %> - question_format: question_format_dropdown - option_comment_display: true - -<%= lbl %>_question_multi_select_box: - text: 'Question with Multi-Select Box' - default_value: 'Default value for multi select' - guidance: 'Guidance for multi select' - number: 6 - section: <%= lbl %> - question_format: question_format_multi_select - option_comment_display: true -<% end %> diff --git a/test/fixtures/roles.yml b/test/fixtures/roles.yml deleted file mode 100644 index ff4b787..0000000 --- a/test/fixtures/roles.yml +++ /dev/null @@ -1,5 +0,0 @@ -<% # Load the roles from those defined within the MagicStrings section of the locale %> -<% I18n.t("magic_strings.roles").each do |k,v| %> -<%= v %>: - name: <%= "#{v}" %> -<% end %> diff --git a/test/fixtures/sections.yml b/test/fixtures/sections.yml deleted file mode 100644 index ae406fd..0000000 --- a/test/fixtures/sections.yml +++ /dev/null @@ -1,48 +0,0 @@ -# Produces: -# ----------------------------- -# Generates 2 Sections for each Version of a published template and 4 Sections for -# each Version of an unpublished template -# (see dmptemplates.yml, phases.yml and versions.yml) -# -# [template]_phase_1_version_1_section_[1..2] -# [template]_unpublished_phase_[1..2]_version_[1..2]_section_[1..4] -# -# The complete organisation has 2 sections attached to its template and 2 -# customisations -# -# complete_customised_template_phase_1_version_1_section_[1..2] -# - -# Import versions.yml so that we can dynamically generate sections -<% versions = YAML::load(ERB.new(File.read('./test/fixtures/versions.yml')).result) %> - -<% versions.each do |lbl, hash| %> - <% if lbl.include?('customised_') %> - - <% 2.times do |n| %> -<%= lbl %>_customisation_<%= n + 1 %>: - title: <%= "#{(n == 0) ? 'Licensing (Customisation)' : 'Access (Customisation)'}" %> - number: <%= 3 + n %> - version: <%= lbl %> - organisation: complete - <% end %> - - <% else %> - - <% 2.times do |x| %> -<%= lbl %>_section_<%= x + 1 %>: - title: <%= "#{(x == 0) ? 'Data Collection' : 'Storage and Backup'}" %> - number: <%= x + 1 %> - version: <%= lbl %> - <% end %> - - <% if lbl.include?('_unpublished') %> - <% 2.times do |y| %> -<%= lbl %>_section_<%= y + 3 %>: - title: <%= "#{(y == 0) ? 'Documentation' : 'Compliance'}" %> - number: <%= 3 + y %> - version: <%= lbl %> - <% end %> - <% end %> - <% end %> -<% end %> diff --git a/test/fixtures/templates.yml b/test/fixtures/templates.yml deleted file mode 100644 index 937a0c0..0000000 --- a/test/fixtures/templates.yml +++ /dev/null @@ -1,11 +0,0 @@ -# Read about fixtures at http://api.rubyonrails.org/classes/ActiveRecord/FixtureSet.html - -# This model initially had no columns defined. If you add columns to the -# model remove the '{}' from the fixture names and add the columns immediately -# below each fixture, per the syntax in the comments below -# -one: {} -# column: value -# -two: {} -# column: value diff --git a/test/fixtures/themes.yml b/test/fixtures/themes.yml deleted file mode 100644 index d02ca85..0000000 --- a/test/fixtures/themes.yml +++ /dev/null @@ -1,176 +0,0 @@ -# Read about fixtures at http://api.rubyonrails.org/classes/ActiveRecord/Fixtures.html - -related_policies: - title: Related Policies - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -existing_data: - title: Existing Data - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -licensing_of_existing_data: - title: Licensing of Existing Data - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -relationship_to_existing_data: - title: Relationship to Existing Data - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -description_of_data_content: - title: Description of Data Content - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -data_format: - title: Data Format - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -data_volumes: - title: Data Volumes - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -data_type: - title: Data Type - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -data_capture_methods: - title: Data Capture Methods - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -data_organisation: - title: Data Organisation - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -data_quality: - title: Data Quality - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -documentation: - title: Documentation - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -metadata_capture: - title: Metadata Capture - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -metadata_standards: - title: Metadata Standards - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -discovery_by_users: - title: Discovery by Users - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -ethical_issues: - title: Ethical Issues - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -ipr_ownership_and_licencing: - title: IPR Ownership and Licencing - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -active_data_storage: - title: Active Data Storage - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -backup_procedures: - title: Backup Procedures - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -data_security: - title: Data Security - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -data_selection: - title: Data Selection - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -preservation_plan: - title: Preservation Plan - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -period_of_preservation: - title: Period of Preservation - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -data_repository: - title: Data Repository - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -audience: - title: Audience - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -expected_reuse: - title: Expected Reuse - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -method_for_data_sharing: - title: Method For Data Sharing - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -timeframe_for_data_sharing: - title: Timeframe For Data Sharing - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -embargo_period: - title: Embargo Period - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -restrictions_on_sharing: - title: Restrictions on Sharing - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -managed_access_procedures: - title: Managed Access Procedures - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -responsibilities: - title: Responsibilities - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -resourcing_skills_and_training: - title: "Resourcing: Skills and Training" - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -resourcing_hardware_and_software: - title: "Resourcing: Hardware and Software" - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en - -resourcing_preservation_and_data_sharing: - title: "Resourcing: Preservation and Data Sharing" - description: "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum." - locale: en diff --git a/test/fixtures/token_permission_types.yml b/test/fixtures/token_permission_types.yml deleted file mode 100644 index 3c39e5b..0000000 --- a/test/fixtures/token_permission_types.yml +++ /dev/null @@ -1,7 +0,0 @@ -plans_token_type: - token_type: 'plans' - text_description: 'allows a user access to the plans api endpoint' - -guidances_token_type: - token_type: 'guidances' - text_description: 'allows a user access to the guidances api endpoint' \ No newline at end of file diff --git a/test/fixtures/users.yml b/test/fixtures/users.yml deleted file mode 100644 index 1ed82ff..0000000 --- a/test/fixtures/users.yml +++ /dev/null @@ -1,121 +0,0 @@ -# Produces: -# ----------------------------- -# cc_super -# cc_admin -# -# funder_admin -# -# complete_admin -# complete_user -# -# institution_[1..2]_admin -# institution_[1..2]_user -# -# school_[1..2]_admin -# school_[1..2]_user -# -# project_[1..2]_admin -# project_[1..2]_user -# - -# Import organisation_types.yml and roles.yml -<% organisation_types = YAML::load(ERB.new(File.read('./test/fixtures/organisation_types.yml')).result) %> -cc_super: - firstname: 'Curation Centre' - surname: 'Super Admin' - email: 'super-admin@example-cc.org' - encrypted_password: <%= User.new.send(:password_digest, 'password123') %> - accept_terms: true - organisation: curation_center - roles: [add_organisations, change_org_affiliation, grant_api_to_orgs, grant_permissions, modify_templates, modify_guidance, change_org_details, use_api] - api_token: "ABCD1234ZYX987supercc" - language: en-UK - confirmed_at: '2016-09-09 10:10:10' - -cc_admin: - firstname: 'Curation Centre' - surname: 'Administrator' - email: 'admin@example-cc.org' - encrypted_password: <%= User.new.send(:password_digest, 'password123') %> - accept_terms: true - organisation: curation_center - roles: [grant_permissions, modify_templates, modify_guidance, change_org_details, use_api] - api_token: "ABCD1234ZYX987admincc" - language: en-UK - confirmed_at: '2016-09-09 10:10:10' - -funder_admin: - firstname: 'Funder' - surname: 'Administrator' - email: 'admin@example-funder.org' - encrypted_password: <%= User.new.send(:password_digest, 'password123') %> - accept_terms: true - organisation: funder - roles: [grant_permissions, modify_templates, modify_guidance, change_org_details, use_api] - api_token: "ABCD1234ZYX987adminfunder" - language: en-UK - confirmed_at: '2016-09-09 10:10:10' - -# We unfortunatley cannot tab this out nicely because YAML is expecting the values in -# the first column -<% organisation_types.each do |lbl, obj| %> - <% unless ['funder', 'organisation'].include?(lbl) %> - <% 2.times do |x| %> - -<%= lbl %>_<%= x + 1 %>_admin: - firstname: <%= "#{obj['name']} #{x + 1}" %> - surname: "Admin" - email: <%= "admin@example-#{lbl}-#{x + 1}.org" %> - encrypted_password: <%= User.new.send(:password_digest, 'password123') %> - orcid_id: <%= "orcid-#{lbl}-#{x + 1}-admin12345" %> - shibboleth_id: <%= "shib-#{lbl}-#{x + 1}-admin12345" %> - accept_terms: true - organisation: <%= lbl %>_<%= x + 1 %> - roles: [grant_permissions, modify_templates, modify_guidance, change_org_details, use_api] - api_token: "ABCD1234ZYX987admin#{lbl}#{x + 1}" - language: en-UK - confirmed_at: '2016-09-09 10:10:10' - -<%= lbl %>_<%= x + 1 %>_user: - firstname: <%= "#{obj['name']} #{x + 1}" %> - surname: "User" - email: <%= "user@example-#{lbl}-#{x + 1}.org" %> - encrypted_password: <%= User.new.send(:password_digest, 'password123') %> - orcid_id: <%= "orcid-#{lbl}-#{x + 1}-user12345" %> - shibboleth_id: <%= "shib-#{lbl}-#{x + 1}-user12345" %> - accept_terms: true - organisation: <%= lbl %>_<%= x + 1 %> - api_token: "ABCD1234ZYX987user#{lbl}#{x + 1}" - language: en-UK - confirmed_at: '2016-09-09 10:10:10' - - <% end %> - <% end %> -<% end %> - -complete_admin: - firstname: "Complete" - surname: "Admin" - email: <%= "admin@example-complete.org" %> - encrypted_password: <%= User.new.send(:password_digest, 'password123') %> - orcid_id: <%= "orcid-complete-admin12345" %> - shibboleth_id: <%= "shib-complete-admin12345" %> - accept_terms: true - organisation: complete - roles: [grant_permissions, modify_templates, modify_guidance, change_org_details, use_api] - api_token: "ABCD1234ZYX987admincomplete" - language: en-UK - confirmed_at: '2016-09-09 10:10:10' - -complete_user: - firstname: "Complete" - surname: "User" - email: <%= "user@example-complete.org" %> - encrypted_password: <%= User.new.send(:password_digest, 'password123') %> - orcid_id: <%= "orcid-complete-user12345" %> - shibboleth_id: <%= "shib-complete-user12345" %> - accept_terms: true - organisation: complete - api_token: "ABCD1234ZYX987usercomplete" - language: en-UK - confirmed_at: '2016-09-09 10:10:10' \ No newline at end of file diff --git a/test/fixtures/versions.yml b/test/fixtures/versions.yml deleted file mode 100644 index d4e9758..0000000 --- a/test/fixtures/versions.yml +++ /dev/null @@ -1,40 +0,0 @@ -# Produces: -# ----------------------------- -# Generates 1 Version for each Phase of a published template and 2 Versions for -# each Phase of an unpublished template -# (see dmptemplates.yml for template list and phases.yml for phase list) -# -# [template]_phase_1_version_1 -# [template]_unpublished_phase_[1..2]_version_[1..2] -# -# A copy of Funder Template 1 Phase 1 that contains customisations -# -# complete_template_customised_phase -# - -# Import phases.yml so that we can dynamically generate versions -<% phases = YAML::load(ERB.new(File.read('./test/fixtures/phases.yml')).result) %> - -<% phases.each do |lbl, hash| %> - -<%= lbl %>_version_1: - title: <%= "hash['title'] - Version 1" %> - number: 1 - published: true - phase: <%= lbl %> - - <% if lbl.include?('_unpublished') %> -<%= lbl %>_version_2: - title: <%= "hash['title'] - Version 2" %> - number: 2 - published: false - phase: <%= lbl %> - <% end %> - -<% end %> - -complete_customised_template_phase_1_version_1: - title: "Customisation of Funder Template 1, Phase 1, Version 1" - number: 1 - published: false - phase: funder_template_1_phase_1 \ No newline at end of file diff --git a/test/test_helper.rb b/test/test_helper.rb index 11bf531..0aa1e8c 100644 --- a/test/test_helper.rb +++ b/test/test_helper.rb @@ -19,7 +19,10 @@ # # Note: You'll currently still have to declare fixtures explicitly in integration tests # -- they do not yet inherit this setting - fixtures :all + #fixtures :all + + # Use the db/seed.rb file to populate the test DB + require_relative '../db/seeds.rb' # Add more helper methods to be used by all tests here...