diff --git a/app/controllers/application_controller.rb b/app/controllers/application_controller.rb index f1eced4..cbc894d 100644 --- a/app/controllers/application_controller.rb +++ b/app/controllers/application_controller.rb @@ -1,50 +1,73 @@ class ApplicationController < ActionController::Base - protect_from_forgery with: :exception - - # Override build_footer method in ActiveAdmin::Views::Pages + protect_from_forgery with: :exception + + # Override build_footer method in ActiveAdmin::Views::Pages require 'active_admin_views_pages_base.rb' - - rescue_from CanCan::AccessDenied do |exception| - redirect_to root_url, :alert => exception.message - end - - after_filter :store_location - def store_location - # store last url - this is needed for post-login redirect to whatever the user last visited. - if (request.fullpath != "/users/sign_in" && \ - request.fullpath != "/users/sign_up" && \ - request.fullpath != "/users/password" && \ + rescue_from CanCan::AccessDenied do |exception| + redirect_to root_url, :alert => exception.message + end + + before_filter :set_locale + + after_filter :store_location + + def set_locale + # parameter from url takes precedence + if params[:locale] + # if locales data is present in the parameter from url use it + # TODO we need to error to the user that locale is missing, it can be THE CASE because there can be a missmatch between locales files and db + I18n.locale = params[:locale] + elsif false # TODO + # if user has set preferred language use it + elsif false # TODO + # use user's organization language, keep in mine the "OTHER ORG" edge case which should use english + else + # just use the default language, line can be commented out, included just for clarity + # I18n.locale = config.i18n.default_locale + end + end + + # Added setting for passing local params across pages + def default_url_options(options = {}) + { locale: I18n.locale }.merge options + end + + def store_location + # store last url - this is needed for post-login redirect to whatever the user last visited. + if (request.fullpath != "/users/sign_in" && \ + request.fullpath != "/users/sign_up" && \ + request.fullpath != "/users/password" && \ request.fullpath != "/users/sign_up?nosplash=true" && \ - !request.xhr?) # don't store ajax calls - session[:previous_url] = request.fullpath - end - end + !request.xhr?) # don't store ajax calls + session[:previous_url] = request.fullpath + end + end - def after_sign_in_path_for(resource) - session[:previous_url] || root_path - end + def after_sign_in_path_for(resource) + session[:previous_url] || root_path + end - def after_sign_up_path_for(resource) - session[:previous_url] || root_path - end - - def after_sign_in_error_path_for(resource) - session[:previous_url] || root_path - end - - def after_sign_up_error_path_for(resource) - session[:previous_url] || root_path - end - - def authenticate_admin! - redirect_to root_path unless user_signed_in? && current_user.is_admin? - end + def after_sign_up_path_for(resource) + session[:previous_url] || root_path + end - def get_plan_list_columns - if user_signed_in? - @selected_columns = current_user.settings(:plan_list).columns - @all_columns = Settings::PlanList::ALL_COLUMNS - end - end + def after_sign_in_error_path_for(resource) + session[:previous_url] || root_path + end + + def after_sign_up_error_path_for(resource) + session[:previous_url] || root_path + end + + def authenticate_admin! + redirect_to root_path unless user_signed_in? && current_user.is_admin? + end + + def get_plan_list_columns + if user_signed_in? + @selected_columns = current_user.settings(:plan_list).columns + @all_columns = Settings::PlanList::ALL_COLUMNS + end + end end diff --git a/app/controllers/guidances_controller.rb b/app/controllers/guidances_controller.rb index a05db00..8718bb2 100644 --- a/app/controllers/guidances_controller.rb +++ b/app/controllers/guidances_controller.rb @@ -77,10 +77,10 @@ # updates phases, versions, sections and questions based on template selected dmptemplate = Dmptemplate.find(params[:dmptemplate_id]) # map to title and id for use in our options_for_select - @phases = dmptemplate.phases.map{|a| [a.title, a.id]}.insert(0, "Select a phase") - @versions = dmptemplate.versions.map{|s| [s.title, s.id]}.insert(0, "Select a version") - @sections = dmptemplate.sections.map{|s| [s.title, s.id]}.insert(0, "Select a section") - @questions = dmptemplate.questions.map{|s| [s.text, s.id]}.insert(0, "Select a question") + @phases = dmptemplate.phases.map{|a| [a.title, a.id]}.insert(0, I18n.t('helpers.select_phase')) + @versions = dmptemplate.versions.map{|s| [s.title, s.id]}.insert(0, I18n.t('helpers.select_version')) + @sections = dmptemplate.sections.map{|s| [s.title, s.id]}.insert(0, I18n.t('helpers.select_section')) + @questions = dmptemplate.questions.map{|s| [s.text, s.id]}.insert(0, I18n.t('helpers.select_question')) end @@ -88,23 +88,23 @@ # updates versions, sections and questions based on phase selected phase = Phase.find(params[:phase_id]) # map to name and id for use in our options_for_select - @versions = phase.versions.map{|s| [s.title, s.id]}.insert(0, "Select a version") - @sections = phase.sections.map{|s| [s.title, s.id]}.insert(0, "Select a section") - @questions = phase.questions.map{|s| [s.text, s.id]}.insert(0, "Select a question") + @versions = phase.versions.map{|s| [s.title, s.id]}.insert(0, I18n.t('helpers.select_version')) + @sections = phase.sections.map{|s| [s.title, s.id]}.insert(0, I18n.t('helpers.select_section')) + @questions = phase.questions.map{|s| [s.text, s.id]}.insert(0, I18n.t('helpers.select_question')) end def update_sections # updates sections and questions based on version selected version = Version.find(params[:version_id]) # map to name and id for use in our options_for_select - @sections = version.sections.map{|s| [s.title, s.id]}.insert(0, "Select a section") - @questions = version.questions.map{|s| [s.text, s.id]}.insert(0, "Select a question") + @sections = version.sections.map{|s| [s.title, s.id]}.insert(0, I18n.t('helpers.select_section')) + @questions = version.questions.map{|s| [s.text, s.id]}.insert(0, I18n.t('helpers.select_question')) end def update_questions # updates songs based on artist selected section = Section.find(params[:section_id]) - @questions = section.questions.map{|s| [s.text, s.id]}.insert(0, "Select a question") + @questions = section.questions.map{|s| [s.text, s.id]}.insert(0, I18n.t('helpers.select_question')) end diff --git a/app/controllers/projects_controller.rb b/app/controllers/projects_controller.rb index a2ab8cc..a860980 100644 --- a/app/controllers/projects_controller.rb +++ b/app/controllers/projects_controller.rb @@ -6,7 +6,7 @@ def index if user_signed_in? then if (current_user.shibboleth_id.nil? || current_user.shibboleth_id.length == 0) && !cookies[:show_shib_link].nil? && cookies[:show_shib_link] == "show_shib_link" then - flash.notice = "Would you like to #{view_context.link_to 'link your DMPonline account to your institutional credentials?', user_omniauth_shibboleth_path}".html_safe + flash.notice = "Would you like to #{view_context.link_to I18n.t('helpers.shibboleth_to_link_text'), user_omniauth_shibboleth_path}".html_safe end @projects = current_user.projects.filter(params[:filter]) diff --git a/app/mailers/user_mailer.rb b/app/mailers/user_mailer.rb index c413d99..6025e3b 100644 --- a/app/mailers/user_mailer.rb +++ b/app/mailers/user_mailer.rb @@ -1,20 +1,20 @@ class UserMailer < ActionMailer::Base - default from: 'info@dcc.ac.uk' + default from: I18n.t('helpers.main_email.from') def sharing_notification(project_group) @project_group = project_group - mail(to: @project_group.user.email, subject: "You have been given access to a Data Management Plan") + mail(to: @project_group.user.email, subject: I18n.t('helpers.main_email.access_given')) end def permissions_change_notification(project_group) @project_group = project_group - mail(to: @project_group.user.email, subject: "DMP permissions changed") + mail(to: @project_group.user.email, subject: I18n.t('helpers.main_email.permission_changed')) end def project_access_removed_notification(user, project) @user = user @project = project - mail(to: @user.email, subject: "DMP access removed") + mail(to: @user.email, subject: I18n.t('helpers.main_email.access_removed')) end def api_token_granted_notification(user) diff --git a/app/models/language.rb b/app/models/language.rb new file mode 100644 index 0000000..a402b79 --- /dev/null +++ b/app/models/language.rb @@ -0,0 +1,3 @@ +class Language < ActiveRecord::Base + +end \ No newline at end of file diff --git a/app/models/plan.rb b/app/models/plan.rb index e2989a3..70510fa 100644 --- a/app/models/plan.rb +++ b/app/models/plan.rb @@ -43,7 +43,7 @@ if !self.version.nil? && !self.version.phase.nil? && !self.version.phase.title? then return self.version.phase.title else - return "DMP title" + return I18n.t('tool_title2') end else return self.settings(:export).title diff --git a/app/models/question.rb b/app/models/question.rb index be97f38..f181719 100644 --- a/app/models/question.rb +++ b/app/models/question.rb @@ -72,7 +72,7 @@ GuidanceGroup.where("organisation_id = ?", org_admin.id).each do |group| group.guidances.each do |g| g.themes.where("id IN (?)", theme_ids).each do |gg| - guidances["#{group.name} guidance on #{gg.title}"] = g + guidances["#{group.name} " + I18n.t('admin.guidance_lowercase_on') + " #{gg.title}"] = g end end end @@ -81,7 +81,7 @@ question.guidances.each do |g_by_q| g_by_q.guidance_groups.each do |group| if group.organisation == org_admin - guidances["#{group.name} guidance"] = g_by_q + guidances["#{group.name} " + I18n.t('admin.guidance_lowercase')] = g_by_q end end end diff --git a/app/views/contact_us/contacts/new.html.erb b/app/views/contact_us/contacts/new.html.erb index fccdff6..7829d7a 100644 --- a/app/views/contact_us/contacts/new.html.erb +++ b/app/views/contact_us/contacts/new.html.erb @@ -20,7 +20,7 @@ <% if ContactUs.require_name %>
| <%= t('org_admin.guidance_group.name_label') %> | -
- <%= f.text_field :name,
- :as => :string,
- :class => 'text_field'%>
+
+
+ <%= form_for(@guidance_group, :url => admin_update_guidance_group_path(@guidance_group), :html => {:method => :put}) do |f| %>
-
-
- <%= link_to( image_tag('help_button.png'), '#', :class => 'guidance_group_title_popover', :rel => "popover", 'data-html' => "true", 'data-content' => t('org_admin.guidance_group.title_help_text_html'))%>
-
- |
-
| <%= t('org_admin.guidance.template') %> | -
- <% if @guidance_group.dmptemplate_ids == [] then %>
- <% default_select = "" %>
- <%else%>
- <% default_select = @guidance_group.dmptemplate_ids %>
- <%end%>
- <%= f.select :dmptemplate_ids, options_for_select(
- [['All templates', ""]].concat( Dmptemplate.funders_and_own_templates(current_user.organisation_id).collect{ |g| [g.title, g.id] }), :selected => default_select ),{} ,
- {:prompt => false , :multiple => true}%>
-
-
- <%= link_to( image_tag('help_button.png'), '#', :class => 'guidance_group_template_popover', :rel => "popover", 'data-html' => "true", 'data-content' => t('org_admin.guidance_group.template_help_text_html'))%>
-
-
- |
-
| <%= t('org_admin.guidance_group.published') %> | -
- <%= f.check_box :published %>
-
-
-
-
- |
-
| <%= t('org_admin.guidance_group.subset') %> | -
- <%= f.check_box :optional_subset %> <%= t('org_admin.guidance_group.subset_eg') %>
-
-
- <%= link_to( image_tag('help_button.png'), '#', :class => 'guidance_group_subset_popover', :rel => "popover", 'data-html' => "true", 'data-content' => t('org_admin.guidance_group.subset_option_help_text'))%>
-
- |
-
| <%= t('org_admin.guidance_group.name_label') %> | +
+
+ <%= f.text_field :name,
+ :as => :string,
+ :class => 'text_field' %>
+
+
+
+ <%= link_to(image_tag('help_button.png'), '#', :class => 'guidance_group_title_popover', :rel => "popover", 'data-html' => "true", 'data-content' => t('org_admin.guidance_group.title_help_text_html')) %>
+
+ |
+
| <%= t('org_admin.guidance.template') %> | +
+
+ <% if @guidance_group.dmptemplate_ids == [] then %>
+ <% default_select = "" %>
+ <% else %>
+ <% default_select = @guidance_group.dmptemplate_ids %>
+ <% end %>
+ <%= f.select :dmptemplate_ids, options_for_select(
+ [['All templates', ""]].concat(Dmptemplate.funders_and_own_templates(current_user.organisation_id).collect { |g| [g.title, g.id] }), :selected => default_select), {},
+ {:prompt => false, :multiple => true} %>
+
+
+ <%= link_to(image_tag('help_button.png'), '#', :class => 'guidance_group_template_popover', :rel => "popover", 'data-html' => "true", 'data-content' => t('org_admin.guidance_group.template_help_text_html')) %>
+
+
+ |
+
| <%= t('org_admin.templates.published_label') %> | +
+
+ <%= f.check_box :published %>
+
+
+
+
+ |
+
| <%= t('org_admin.guidance_group.subset') %> | +
+
+ <%= f.check_box :optional_subset %> <%= t('org_admin.guidance_group.subset_eg') %>
+
+
+ <%= link_to(image_tag('help_button.png'), '#', :class => 'guidance_group_subset_popover', :rel => "popover", 'data-html' => "true", 'data-content' => t('org_admin.guidance_group.subset_option_help_text')) %>
+
+ |
+
| <%= t("org_admin.guidance.name_label") %> | +<%= t('org_admin.guidance_group.name_label') %> |
<%= f.text_field :name,
:as => :string,
@@ -62,7 +62,7 @@
<%= f.submit t("helpers.submit.save"), :name => "draft", :class => "btn btn-primary" %>
- <%= f.submit t("helpers.submit.save_publish"), :name => "save_publish", :class => "btn btn-primary" %>
+ <%= f.submit t('helpers.submit.publish'), :name => "save_publish", :class => "btn btn-primary" %>
<%= link_to t("helpers.submit.cancel"), :back, :class => "btn cancel" %>
diff --git a/app/views/guidance_groups/admin_show.html.erb b/app/views/guidance_groups/admin_show.html.erb
index 670fb34..fe641ab 100644
--- a/app/views/guidance_groups/admin_show.html.erb
+++ b/app/views/guidance_groups/admin_show.html.erb
@@ -1,89 +1,92 @@
<%= stylesheet_link_tag "admin" %>
- <%= t("org_admin.guidance.guidance_group_label") %>
+ <%= t("org_admin.guidance.guidance_group_label") %>
-
-
|
| <%= t("org_admin.guidance_group.name_label") %> | -<%= raw @guidance_group.name %> | -
| - <% if @guidance_group.dmptemplates.count == 1 then %> - <%= t("org_admin.guidance.template") %> - <%else%> - <%= t("org_admin.guidance.templates") %> - <%end%> - | -<% i = 1 %> - <% if @guidance_group.dmptemplates.count == 0 then %> - <% list = Dmptemplate.funders_and_own_templates(current_user.organisation_id)%> - <% list.each do |tem|%> - <%= tem.title %> - <% if list.count > i then%> - , - <% i +=1 %> - <% end %> - <%end%> - <%else%> - <% @guidance_group.dmptemplates.each do |tem|%> - <%= tem.title %> - <% if @guidance_group.dmptemplates.count > i then%> - , - <% i +=1 %> - <% end %> - <%end%> - <%end%> - | -
| <%= t("org_admin.guidance_group.published") %> | -<%if @guidance_group.published.nil? || @guidance_group.published == false then%> - <%= t("helpers.no_label")%> - <%else%> - <%= t("helpers.yes_label")%> - <%end%> - | -
| <%= t("org_admin.guidance_group.subset") %> | -<%if @guidance_group.optional_subset.nil? || @guidance_group.optional_subset == false then%> - <%= t('helpers.no_label')%> - <%else%> - <%= t('helpers.yes_label')%> - <%end%> - | -
| <%= t("org_admin.guidance.created") %> | -<%= l @guidance_group.created_at.to_date, :formats => :short %> | -
| <%= t("org_admin.guidance.last_updated") %> | -<%= l @guidance_group.updated_at.to_date, :formats => :short %> | -
| <%= t("org_admin.guidance_group.name_label") %> | +<%= raw @guidance_group.name %> | +
| + <% if @guidance_group.dmptemplates.count == 1 then %> + <%= t("org_admin.guidance.template") %> + <% else %> + <%= t("org_admin.guidance.templates") %> + <% end %> + | ++ <% i = 1 %> + <% if @guidance_group.dmptemplates.count == 0 then %> + <% list = Dmptemplate.funders_and_own_templates(current_user.organisation_id) %> + <% list.each do |tem| %> + <%= tem.title %> + <% if list.count > i then %> + , + <% i +=1 %> + <% end %> + <% end %> + <% else %> + <% @guidance_group.dmptemplates.each do |tem| %> + <%= tem.title %> + <% if @guidance_group.dmptemplates.count > i then %> + , + <% i +=1 %> + <% end %> + <% end %> + <% end %> + | +
| <%= t('org_admin.templates.published_label') %> | ++ <% if @guidance_group.published.nil? || @guidance_group.published == false then %> + <%= t("helpers.no_label") %> + <% else %> + <%= t("helpers.yes_label") %> + <% end %> + | +
| <%= t("org_admin.guidance_group.subset") %> | ++ <% if @guidance_group.optional_subset.nil? || @guidance_group.optional_subset == false then %> + <%= t('helpers.no_label') %> + <% else %> + <%= t('helpers.yes_label') %> + <% end %> + | +
| <%= t("org_admin.guidance.created") %> | +<%= l @guidance_group.created_at.to_date, :formats => :short %> | +
| <%= t("org_admin.guidance.last_updated") %> | +<%= l @guidance_group.updated_at.to_date, :formats => :short %> | +
<%= t("helpers.settings.plans.desc") -%>
+ + +<%= t('helpers.settings.plans.description') -%>
<%= render "export_formatting_form" %> diff --git a/config/initializers/locale.rb b/config/initializers/locale.rb index 4aaaa49..0cf1456 100644 --- a/config/initializers/locale.rb +++ b/config/initializers/locale.rb @@ -7,12 +7,12 @@ config.i18n.load_path += Dir[Rails.root.join('my', 'locales', '*.{rb,yml}').to_s] # set default locale # in config/initializers/locale.rb - - # set default locale to something other than :en - config.i18n.default_locale = :en - - # set fallback locale - config.i18n.fallbacks = true - + + # set default locale to something other than :en + config.i18n.default_locale = :'en-UK' + + # set fallback locale + config.i18n.fallbacks = true + end end diff --git a/config/initializers/swagger.rb b/config/initializers/swagger.rb index 685cc01..a9dfeaf 100644 --- a/config/initializers/swagger.rb +++ b/config/initializers/swagger.rb @@ -6,7 +6,7 @@ end Swagger::Docs::Config.register_apis({ - '0.0': { + '0.0' => { controller_base_path: '', api_file_path: 'public/apidocs', base_path: 'http://localhost:3000', diff --git a/config/locales/de.bootstrap.yml b/config/locales/de.bootstrap.yml new file mode 100644 index 0000000..c176c40 --- /dev/null +++ b/config/locales/de.bootstrap.yml @@ -0,0 +1,18 @@ +# Sample localization file for English. Add more files in this directory for other locales. +# See https://github.com/svenfuchs/rails-i18n/tree/master/rails%2Flocale for starting points. + +de: + helpers: + actions: "Aktionen" + links: + back: "Zurück" + cancel: "Abbrechen" + confirm: "Sind Sie sicher?" + destroy: "Löschen" + new: "Neu" + edit: "Bearbeiten" + titles: + edit: "Bearbeiten" + save: "Speichern" + new: "Neu" + delete: "Löschen" diff --git a/config/locales/de.yml b/config/locales/de.yml new file mode 100644 index 0000000..a58f1fe --- /dev/null +++ b/config/locales/de.yml @@ -0,0 +1,801 @@ +de: + date: + formats: + # Use the strftime parameters for formats. + # When no format has been given, it uses default. + # You can provide other formats here if you like! + default: "%d-%m-%Y" + short: "%d/%m/%Y" + custom: "%d/%m/%Y %H:%M" + long: "%d %B, %Y" + + day_names: [Sonntag, Montag, Dienstag, Mittwoch, Donnerstag, Freitag, Samstag] + abbr_day_names: [So, Mo, Di, Mi, Do, Fr, Sa] + + # Don't forget the nil at the beginning; there's no such thing as a 0th month + month_names: [~, Januar, Februar, März, April, Mai, Juni, Juli, August, September, Oktober, November, Dezember] + abbr_month_names: [~, Jan, Feb, Mär, Apr, Mai, Jun, Jul, Aug, Sep, Okt, Nov, Dez] + # Used in date_select and datetime_select. + order: + - day + - month + - year + + time: + formats: + default: "%a, %d %b %Y %H:%M:%S %z" + short: "%d %b %H:%M" + long: "%B %d, %Y %H:%M" + custom: "%d/%m/%Y %H:%M" + am: "am" + pm: "pm" + + tool_title: "DMPonline" + dmponline3_text: "DMPonline vorherige Version" + dcc_name: "Digital Curation Centre" + welcome_title: "Willkommen." + welcome_text: "DMPonline wurde vom Digital Curation Centre entwickelt, um Sie bei der Erstellung von Data-Managment-Plänen zu unterstützen.
" + welcome_links: "" + ccid_message: "" + + + admin: + org_title: "Name der Organisation" + org: "Organisation" + orgs: "Organisationen" + org_type: "Art der Organisation" + org_parent: "Übergeordnete Organisation" + org_created_message: "Organisation wurde erfolgreich angelegt." + org_updated_message: "Organisation wurde erfolgreich aktualisiert." + plans: "Pläne" + title: "Titel" + desc: "Beschreibung" + guidance_group: "Hilfestellungsgruppe" + no_guidance_group: "Keine Hilfestellungsgruppe" + guidance: "Hilfestellung" + name: "Name" + abbrev: "Abkürzung" + question: "Frage" + question_format: "Fragenformat" + questions: "Fragen" + template_title: "Vorlagentitel" + section_title: "Abschnittstitel" + phase_title: "Phasentitel" + version_title: "Versionstitel" + user_name: "Nutzername" + firstname: "Vorname" + surname: "Nachname" + user: "Nutzer" + user_org_role: "Rolle des Nutzers in der Organisation" + user_role_type: "Art der Rolle" + user_role: "Nutzerrolle" + role: "Rolle" + user_status: "Nutzerstatus" + user_type: "Nutzerart" + last_logged_in: "Zuletzt angemeldet" + version_numb: "Versionsnummer" + details: "Details" + phases: "Phasen" + phase: "Phase" + version: "Version" + versions: "Versionen" + sections: "Abschnitte" + section: "Abschnitt" + multi_options: "Mehrfachfragen-Optionen" + templates: "Vorlagen" + template: "Vorlage" + themes: "Themen" + theme: "Thema" + sug_answer: "Antwortvorschlag" + sug_answers: "Antwortvorschläge" + old_temp_field: "altes Vorlagenfeld" + old_theme_field: "altes Themenfeld" + + + org_admin: + admin_area: "Administativer Bereich" + template_label: "Vorlagen" + user_list_label: "Nutzer" + org_details_label: "Organisations-Details" + org_text: "Grundlegende Informationen über ihre Organisation." + org_abbr_help_text_html: "Dies wird als Bezeichnung an Ihrer Anleitung angezeigt, z.B. 'Kieler Hilfestellung für Metadaten'. Am besten eine Abkürzung oder ein Namenskürzel." + users_list: "Liste der Nutzer" + user_full_name: "Name" + user_name: "E-Mail-Adresse" + last_logged_in: "Zuletzt angemeldet" + how_many_plans: "Wie viele Pläne?" + user_text_html: "Folgend findet sich die Liste von Benutzern registriert bzgl. Ihrer Organisation. Sie können diese Liste bzgl. aller Felder sortieren." + org_name: "Name" + org_abbr: "Abkürzung" + org_desc: "Beschreibung" + org_target_url: "Web-Seite" + org_type: "Organisationsart" + parent_org: "Übergeordnete Organisation" + last_updated: "Zuletzt aktualisiert" + desc_help_text_html: "Sie können eine Hilfestellungtexte erstellen, die im Zusammenhang mit bestimmten Themen angezeigt werden, oder die sich auf eine spezifische Frage beziehen. Generische Hilfestellungen für Themen helfen Zeit und Arbeit zu sparen, da Ihre Hilfestellungen automatisch für alle Vorlagen angezeigt werden; sie müssen andernfalls für jede Vorlage neu erstellt werden.
+Im Normalfall werden Sie wollen, dass Ihre Orinetierungshilfen in allen Vorlagen angezeigt wird. Ausnahmen sind z.B. Hilfestellungen die spezielle Hinweise für einen Förderer geben.
" + delete_message: "Sie sind dabei '%{guidance_summary}' zu löschen. Sind Sie sicher?" + guidance_group: + add_guidance_group: "Gruppe für Hilfestellungen hinzufügen" + guidance_group_list: "Liste der Gruppen für Hilfestellungen" + name_label: "Name" + subset: "Optionale Untergruppe" + subset_eg: "z.B. Fakultät / Einrichtung" + all_temp: "Alle Vorlagen" + help_text_add: "Bitte geben Sie einen Titel für die Gruppe an." + subset_option_help_text: "Falls die Hilfestellung nur für eine bestimmte Nutzergruppe, wie z.B. eine bestimmte Fakultät oder ein Institut, bestimmt ist, wählen Sie diese Option aus. Die Nutzer können die Anzeige von Hilfestellungen dieser Untergruppe im 'Plan erstellen'-Assistenten auswählen." + template_help_text_html: "Wählen Sie aus, in Vorlagen der Hilfetext angezeigt werden soll. Normalerweise werden dies alle Vorlagen sein." + title_help_text_html: "Geben Sie einen geeigneten Namen für Ihre Hilfestellungsgruppe ein, wie z.B. 'CAU Hilfestellungen'. Dieser Name soll den Nutzern vermitteln, woher die Hilfestellung kommt, z.B. 'CAU Hilfestellung zu Metadaten'" + guidance_group_text_html: "Erstelle zuerst eine Hilfestellungsgruppe. Diese könnte institutionsweit oder eine Untermenge von z.B. einer bestimmten Universität / Schule, eines Instituts oder einer Abteilung sein. Wenn Sie Hilfestellung erstellen, werden sie aufgefordert sie einer Hilfestellungsgruppe zuzuordnen.
" + delete_message: "Sie sind dabei '%{guidance_group_name}' zu löschen. Das wird Auswirkungen auf die Hilfestellungen haben. Sind Sie sicher?" + created_message: "Hilfestellungsgruppe erfolgreich erzeugt." + updated_message: "Hilfestellungsgruppe erfolgreich aktualisiert." + destroyed_message: "Hilfestellungsgruppe erfolgreich gelöscht." + templates: + create_template: "Vorlage erstellen" + new_label: "Neue Vorlage" + template_details: "Details der Vorlage" + edit_details: "Details der Vorlage bearbeiten" + view_all_templates: "Alle Vorlagen ansehen" + funders_temp: "Vorlagen der Geldgeber" + title_help_text: "Bitte geben sie einen Titel für Ihre Vorlage an." + section_title_help_text: "Bitte geben sie eine Überschrift für den Abschnitt an." + help_text_html: "Falls Sie eine Vorlage für eine Institution anlegen möchten, können Sie den Knopf 'Vorlage erstellen' nutzen. + Sie können verschiedene Vorlagen erstellen um auf Spezialisierungen einzugehen, z.B. für Forscher und für Doktoranden.
" + create_new_template_text_html: "Um eine Vorlage anzulegen beginnen sie mit einem Titel und einer Beschreibung. Nach dem Speichern haben Sie die Option zum Anlegen von ein oder mehreren Phasen.
" + desc_help_text_html: "Geben Sie eine Beschreibung, die hilft, zwischen den verschiedenen Vorlagen zu unterscheiden, z.B. für verschiedene Zielgruppen" + own_temp: "Eigene Vorlagen" + add_phase_label: "Neue Phase hinzufügen" + view_phase_label: "Phase ansehen" + edit_phase_label: "Phase bearbeiten" + back_to_edit_phase_label: "Zurück, um die Ansicht zu bearbeiten" + edit_phase_details_label: "Details der Phase bearbeiten" + phase_details_label: "Details der Phase" + phase_order_label: "Reihenfolge" + phase_details_text_html: "Dieser Titel wird den Nutzern angezeigt. Falls Sie mehrere Phasen für einen DMP haben wollen, sollte dies aus dem Titel und der Beschreibung hervorgehen.
" + phase_title_help_text: "Geben Sie einen Titel für die Phase an, z.B. Initialer DMP oder Kompletter DMP. Die Titel werden den Benutzern in den Reitern angezeigt, während sie einen Plan erstellen. Falls Sie nur eine Phase bereitstellen, geben Sie ihm einen allgemeinen Titel wie z.B. 'CAU DMP'" + phase_number_help_text: "Hier können sie die Abfolge der Phasen in Ihrer Vorlage bestimmen." + phase_desc_help_text_html: "Geben Sie eine kurze Beschreibung an. Diese wird den Nutzern oberhalb der Zusammenfassung der Abschnitte und der Fragen, die sie beantowrten müssen, angezeigt." + phase_delete_message: "Sie sind dabei '%{phase_title}' zu löschen. Das wird Auswirkungen auf die Versionen, Abschnitte und Fragen haben, die mit dieser Phase verknüpft sind. Sind Sie sicher?" + phase_new_text_html: "Wenn Sie eine neue Phase in einer Vorlage anlegen, wird automatische eine Version erzeugt. Nachdem Sie das folgende Formular ausgefüllt haben, werden Ihnen Optionen zum erstellen von Abschnitten und Fragen angezeigt." + versions_label: "Versionen" + version_details_label: "Details der Version" + add_section: "Abschnitt hinzufügen" + new_section: "Neuer Abschnitt" + section_title_placeholder: "Neue Abschnittsüberschrift" + section_desc_help_text_html: "Wählen Sie die für diese Frage relevanten Themen aus.
+Dies erlaubt es, sowohl generischen Hilfestellungen auf Institutions-Ebene, als auch aus anderen Quellen, wie z.B. der DINI, oder jedweder Institute oder Einrichtungen, für die Sie Unterstützung anbieten, einzubeziehen.
+Sie können mehrere Themen durch klicken und gleichzeitiges Drücken der Steuerungs- bzw. Kommando-Taste auswählen.
" + default_answer_label: "Vorauswahl" + guidance_label: "Hilfestellung" + question_guidance_help_text_html: "Geben Sie spezifische Hilfestellung an, die diese Frage begleiten soll. Falls Sie auch Hilfestellungen nach Themen angeben, werden diese mit angezeigt; Sie sollten deshalb möglichst wenig Text kopieren." + delete_message: "Sie sind dabei '%{question_text}' zu löschen. Sind Sie sicher?" + question_options_help_text_html: "Geben Sie alle Optionen an, die angezeigt werden sollen. Sie können eine der Option als Vorauswahl mit Hilfe der entsprechenden Checkbox markieren." + + + + + helpers: + home: "Start" + return_home: "Zurück zur Startseite." + admin_area: "Superadmin" + edit_profile: "Profil bearbeiten" + view_plans_label: "Pläne anzeigen" + create_plan_label: "Plan erstellen" + about_us_label: "Über uns" + news_label: "Aktuelles" + help_label: "Hilfe" + contact_label: "Kontakt" + jisc: "Das DCC wird untertützt von" + + greeting: "Hallo" + sign_in: "Anmelden" + sign_in_text: "Falls Sie ein Benutzerkonto besitzen" + sign_out: "Abmelden" + sign_up: "Registrieren" + sign_up_text: "Neu auf DMPonline? Heute noch registrieren." + signed_in: "Angemeldet als " + institution_sign_in_link: "Oder melden Sie sich mit den Zugangsdaten Ihres Instituts an" + institution_sign_in: "" + + + user_name: "E-Mail-Adresse" + email: "E-Mail" + org_not_listed: "Meine Organisation ist nicht in der Auflistung." + email_tip: "This must be a valid email address - a message will be sent to it for confirmation." + organisation_name_tip: "Bitte geben Sie den Namen Ihrer Organisation an." + password_tip: "Dieses muss mindestends 8 Zeichen lang sein." + password_reentry_tip: "Dieses muss mit der Eingabe des vorigen Feldes übereinstimmen." + valid_email: "Bitte geben Sie eine gültige E-Mail-Adresse an." + user_details_text_html: "Bitte beachten Sie, dass Ihre Email-Adresse als Nutzername verwendet wird. Vergessen Sie nicht, Ihre neue E-Mail-Adresse beim der nächsten Anmeldung zu verwenden, falls Sie diese geändert haben.
" + user_details_paragraph_html: "Alle folgenden Angaben können bearbeitet werden." + remember_me: "angemeldet bleiben" + + + password: "Passwort" + current_password: "Aktuelles Passwort" + new_password: "Neues Passwort" + password_conf: "Passwort bestätigen" + change_password: "Passwort ändern" + forgot_password: "Passwort vergessen?" + password_too_small: "Ihr Passwort muss mindestens acht Zeichen enthalten." + password_no_match: "Die Eingabe in diesem Feld muss mit der im vorherigen Feld übereinstimmen." + no_pass_instructions: "Bestätigungsanleitungen nicht erhalten?" + no_unlock_instructions: "Entsperrungsanleitungen nicht erhalten?" + send_password_info: "Anleitung zum Zurücksetzen des Passworts" + edit_password_info: "Zum Ändern Ihres Passworts folgende Felder ausfüllen." + accept_terms_html: "Ich akzeptiere die Nutzungsbedingungen *" + + text_area: "Text area" + text_field: "Textfeld" + radio_buttons: "Optionsfelder" + checkbox: "Checkbox" + dropdown: "Klappliste" + multi_select_box: "Mehrfachauswahlliste" + + error: "Fehler!" + comment: "Kommentar" + send: "Senden" + yes: "Ja" + no: "Nein" + none: "Keines" + title: "Titel" + note: "Anmerkung" + me: "Ich" + view: "Betrachten" + desc: "Beschreibung" + save: "Speichern" + preview: "Vorschau" + saving: "Speichere..." + loading: "Lade..." + removing: "Entferne..." + unsaved: "Ungesicherte Änderungen" + unlink_account: "Trenne Zugang" + submit: + edit: "Bearbeiten" + create: "Erstellen" + update: "Aktualisieren" + cancel: "Abbrechen" + save: "Speichern" + delete: "Löschen" + back: "Zurück" + discard: "Verwerfen" + + name: "Name" + first_name: "Vorname" + last_name: "Nachname" + first_name_help_text: "Bitte geben Sie ihren Vornamen ein." + surname_help_text: "Bitte geben Sie ihren Familien- bzw. Nachnamen ein." + owner: "Besitzer" + orcid_id: "ORCID Nummer" + orcid_html: "ORCID Nummer ist ein persistenter digitaler Identifikator für Forschende. Weitere Informationen…" + sign_up_shibboleth_alert_text_html: "Hinweis: If you have previously created an account in DMPonline, and you want to link this to your institutional credentials, you need to Sign in to that existing DMPonline account first. If you have never created a DMPonline account, then please complete the form below." + shibboleth_linked_text: "Your account is linked to your institutional credentials." + shibboleth_to_link_text: "Link your DMP Builder account to your institutional credentials" + shibboleth_to_link_question: "link your DMP Builder account to your institutional credentials?" + shibboleth_unlink_label: "Unlink your institutional credentials" + shibboleth_unlink_alert: "Unlink institutional credentials alert" + shibboleth_unlink_dialog_text: "You are about to unlink DMP Builder of your institutional credentials, would you like to continue?
" + shibboleth_wait_confirmation: "Currently waiting confirmation for:" + + section_label: "Abschnitt" + sections_label: "Abschnitte" + questions_label: "Fragen" + answers_label: "Antworten" + answer_questions: "Fragen beantworten" + last_edit: "Zuletzt bearbeitet" + select_action: "Wählen Sie eine Aktion" + answered_by: "Beantwortet " + answered_by_part2: " von " + suggested_answer: "Antwortvorschlag" + suggested_example: "Beispielantwort" + notanswered: "Noch nicht beantwortet" + noquestionanswered: "Keine der Fragen wurden beantwortet" + guidance: "Hilfestellung" + policy_expectations: "Policy Expectations" + export: "Export" + guidance_accordion_label: "Hilfestellung" + add_comment_accordion_label: "Füge Kommentar hinzu" + comment_accordion_label: "Kommentare" + + comments: + add_comment_label: "Füge Kommentar hinzu" + add_comment_text: "Bitte füge einen Kommentar hinzu" + comment_label: "Kommentar" + comments_label: "Kommentare" + view_label: "Ansicht" + edit_label: "Bearbeiten" + retract_label: "Entfernen" + clear_label: "Entfernen" + commented_by: "Kommentar von:" + archive_own_comment_question: "Wollen Sie diesen Kommentar wirklich entfernen?" + archive_own_comment_button_label: "Entfernen" + + archive_comment_button_label: "Entfernen" + clear_by: "Kommentar entfernt von" + retracted: "Kommentar von Ihnen entfernt" + + failures: + email_exists: "Diese E-Mail-Adresse ist bereits registriert." + registration_error: "Fehler bei Bearbeitung der Registrierung. Bitte überprüfen Sie, ob sie eine gültige E-Mail-Adresse angegeben haben und Ihr Passwort mindestens 8 Zeichen lang ist." + notices: + successfully_updated: "Details erfolgreich aktualisiert. " + sharing_updated: "Angaben zum Teilen erfolgreich aktualisiert." + invitation_issued: "Einladungen erfolgreich ausgestellt." + enter_email: "Bitte geben Sie eine E-Mail-Adresse an." + access_removed: "Zugriff entfernt." + user_added: "Nutzer dem Projekt hinzugefügt." + answer_recorded: "Antwort erfolgreich erfasst." + answer_saving_error: "Es gab einen Fehler beim Speichern der Antwort." + answer_not_changed: "Keine Änderung in Frageninhalt - nicht gespeichert." + comment_created: "Kommentar wurde erfolgreich erstellt." + comment_updated: "Kommentar wurde erfolgreich aktualisiert." + theme_created: "Thema wurde erfolgreich erstellt.." + theme_updated: "Thema wurde erfolgreich aktualisiert." + page_created: "Seite wurde erfolgreich erstellt." + page_updated: "Seite wurde erfolgreich aktualisert." + user_created: "Nutzer wurde erfolgreich erstellt.." + project_created: "Projekt wurde erfolgreich erstellt." + user_org_role_created: "?User?org?role? wurde erfolgreich erstellt." + user_org_role_updated: "?User?org?role? wurde erfolgreich aktualisiert." + user_role_created: "Nutzerrollentyp wurde erfolgreich erstellt." + user_role_updated: "Nutzerrollentyp wurde erfolgreich aktualisiert." + user_status_created: "Nutzerstatus wurde erfolgreich erstellt." + user_status_updated: "Nutzerstatus wurde erfolgreich aktualisiert." + user_type_created: "Nutzertyp wurde erfolgreich erstellt." + user_type_updated: "Nutzertyp wurde erfolgreich aktualisiert." + link_account_question: "Möchten Sie" + account_no_access: "Dieser Zugang hat keinen Zugriff auf jenen Plan." + plan_updated: "Plan wurde erfolgreich aktualisiert." + settings_updated: "Einstellungen erfolgreich aktualisiert." + + progress_bar: + answered: "beantwortet" + question: "Frage" + questions: "Fragen" + + org_type: + funder: "Funder" + institution: "Institution" + project: "Projekt" + organisation: "Organisation" + org_name: "Name der Organisation" + school: "Fakultät" + publisher: "Verleger" + other_guidance: "Andere Hilfestellungen" + template: "Vorlage" + templates: "Vorlagen" + child: "Untereinheit" + other_org_help_text: "Bitte geben Sie den Namen Ihrer Organisation an." + org_select_text: "Bitte eine Organisation auswählen: " + + project: + create: "Ja, Plan erstellen" + edit: "Plandetails bearbeiten" + grant_title: "Förderkennzeichen" + grant_help_text: "Das Förderkennzeichen als Referenz, sofern sinnvoll (Nur für Datenmanagement-Pläne nach der Bewilligung)." + not_applicable: "Nicht anwendbar / nicht gelistet." + multi_templates: "Es stehen verschiedene mögliche Vorlagen zur Auswahl. Bitte wählen Sie eine aus." + project_name: "Name des Plans" + my_project_name: "Mein Plan" + success: "Plan wurde erfolgreich angelegt." + principal_investigator: "Projektleitung / Principal Investigator" + principal_investigator_help_text: "Name des Principal Investigators oder der Leitung des Projektes." + principal_investigator_id: "Principal Investigator ID" + principal_investigator_id_help_text: "z.B. die ORCID (http://orcid.org/)." + funder_help_text: "Der Geldgeber, falls relevant." + funder_name: "Name des Geldgebers" + project_question_desc_label: "Zusammenfassung der Fragen" + tab_plan: "Plandetails" + tab_export: "Export" + export_text_html: "Hier können Sie Ihren Plan in verschiedenen Formaten herunterladen. Das kann nützlich sein, falls Sie den Plan als Teil Ihres Projektantrags einreichen müssen. + Wählen Sie das gewünschte Format aus und wählen Sie 'Exportieren'.
" + questions_answered: "Fragen beantwortet" + not_saved_answers_text_alert: "Geänderte Antworten wurden nicht gesichert:" + not_saved_answers_confirmation_alert: "Wollen Sie sie jetzt sichern?" + not_saved_answers_header: "Ungesicherte Antworten" + project_data_contact: "Kontakt für Plan-Daten" + project_data_contact_help_text: "Name (falls abweichend von obigen Angaben), Telefonnummer und E-Mail-Adresse." + project_name_help_text: "Falls Sie einen Förderantrag stellen, geben Sie bitte den Namen exakt genau so an, wie im Förderantrag." + project_desc_help_text_html: "Fassen Sie die Art der Studien / Untersuchungen zusammen, um Dritten den Zweck der erzeugten oder gesammelt Daten zu veranschaulichen.
Willkommen. Sie können nun ihren ersten DMP erstellen. Wählen Sie 'Plan erstellen' weiter unten aus, um zu beginnen.
" + project_text_when_project: "Die folgende Tabelle listet alle von Ihnen erstellten und von anderen mit Ihnen geteilten Pläne. Diese können jederzeit bearbeitet, geteilt, exportiert und gelöscht werden.
" + confirmation_text: "Plandetails bestätigen" + confirmation_text_desc: "An Stellen, an denen Förderer oder Institutionen keine spezifischen Anforderung definiert haben (oder Sie entsprechende Angaben nicht gemacht haben), wird Ihnen die DCC Checkliste angezeigt. Diese bietet eine generische Fragen und Hilfestellungen; Mehr Informationen unter: DMP Check-Liste 2013." + confirmation_button_text: "Ja, Plan erstellen" + project_details_text_html: "Diese Seite bietet Ihnen einen Überblick über Ihren Plan. Sie gibt an, worauf dieser Plan basiert und gibt eine Übersicht über die Fragen, die gestellt werden." + project_details_editing_text_html: "Bitte geben Sie im Folgenden die Projektdetails an und wählen 'Aktualisieren' aus, um die Änderungen zu speichern." + confirm_delete_text: "Sind Sie sicher, dass sie diesen Plan löschen wollen?" + default_confirmation_text_desc: "Sie haben den Standardplan gewählt, der auf dem Katalog der DCC basiert. Dies bietet eine generische Menge von DMP-Fragen and Hilfestellung. Für mehr Einzelheiten: DMP checklist 2013." + default_confirmation_button_text: "Erstelle Plan" + alert_default_template_text_html: "Bitte beachten: %{org_name} stellt eine DMP-Vorlage zur Verfügung. Wenn Sie sie benutzen möchten, wähle 'Abbrechen', ansonsten wähle 'Erstelle Plan'" + share: + tab_share: "Teilen" + shared_label: "Geteilt?" + share_text_html: "Sie können anderen Zugriff zu Ihren Plan gewähren. Es gibt hierbei drei Abstufungen des Zugriffs. +
Neue Mitarbeitende können durch die Angabe ihrer E-Mail-Adresse und das Wählen des Zugriffsrechts hinzugefugt werden. Bestätigen Sie Ihre Angaben mit 'Mitarbeitende(n) hinzufügen'
+Eingeladene Mitarbeitende erhalten eine E-Mail, die sie darüber informiert, dass sie Zugriff zu Ihrem Plan erhalten haben; sofern Mitarbeitende noch nicht bei DMPonline registriert sind, erhalten sie eine Einladung zur Registrierung. Wenn die Zugriffsrechte geändert werden wird ebenfalls eine Benachrichtigungs-E-Mail versand.
" + collaborators: "Mitarbeitende" + add_collaborator: "Mitarbeitende(n) hinzufügen" + add: "Hinzufügen" + permissions: "Zugriffsrechte" + permissions_desc: "Editoren können zu Plan beitragen. Miteigentümer haben zusätzliche Rechte um Plandetails und Zugriffsrechte bearbeiten zu können." + remove: "Mitarbeitende(n) entfernen" + confirmation_question: "Sind Sie sicher?" + owner: "Besitzer" + co_owner: "Miteigentümer" + edit: "Bearbeiten" + read_only: "Nur Lesen" + locked_section_text: "Dieser Abschnitt ist gespert wegen Bearbeitung durch " + email_text: "Ihnnen wurde '%{access_level}'-Zugriff auf den DMP %{project_link}. gegeben.
" + permission_email_text: "Ihre Befugnisse bzgl. des DMP '%{project_link}' haben sich geändert. Sie besitzen jetzt %{access_level}-Zugriff.
" + access_removed_email_text: "Ihr Zugriff auf den DMP '%{project_title}' wurde entzogen.
" + export: + generated_by: "This document was generated by DMP Builder (http://dmp.library.ualberta.ca)" + create_page: + title: "Einen neuen Plan erstellen" + desc_html: "Bitte wählen Sie aus folgendem Drop-Down-Menü, so dass wir bestimmen können, welche Fragen und Hilfestellungen in Ihrem Plan angezeigt werden sollen.
+Falls Sie nicht den spezifischen Anforderungen eines Geldgebers oder einer Institution folgen, + + wählen Sie hier, um einen generischen DMP zu schreiben , der auf den allgemeinsten Themen basiert.
" + default_template: "Standard DMP" + funders_question: "Falls Sie Fördermittel beantragen, wählen Sie bitte den Förderer aus." + funders_question_description: "Falls nicht, lassen Sie dieses Feld bitte unberührt." + institution_question: "Um Fragen und Hilfestellung einer bestimmten Organisation zu integrieren, wählen Sie diese bitte aus." + institution_question_description: "Sie können eine beliebige Organisation wählen, oder das Feld leer lassen." + other_guidance_question: "Wählen Sie jede beliebige andere Quelle für Hilfestellungen." + other_funder_name_label: "Name des Geldgebers, falls anwendbar." + configure: "Konfigurieren" + columns: + name: "Name" + owner: "Besitzer" + shared: "Geteilt?" + template_owner: "Vorlagenbesitzer" + last_edited: "Zuletzt bearbeitet" + identifier: "Bezeichner" + grant_number: "Zuschussnummer" + principal_investigator: "Principal Investigator / Researcher" + data_contact: "Plandatenkontakt" + description: "Beschreibung" + filter: + placeholder: "Filter Pläne" + submit: "Filter" + cancel: "Abbrechen" + no_matches: "Kein Plan erfüllt '%{filter}'" + plan: + export: + default_title: "DMP Titel" + pdf: + question_not_answered: "Frage nicht beantwortet." + generated_by: "Dieses Dokument wurde von DMPonline (http://dmponline.dcc.ac.uk) erzeugt." + space_used: "annährend %{space_used}% des verfügbaren Platzes wird verwendet (max. %{num_pages} Seiten)" + project_name: "Projektname" + project_identifier: "Projektbezeichner" + grant_title: "Grant Title" + principal_investigator: "Principal Investigator / Forscher" + project_data_contact: "Kontakt für Projektdaten" + project_description: "Beschreibung" + funder: "Geldgeber" + institution: "Institution" + + settings: + title: "Einstellungen" + projects: + title: "Einstellungen - Meine Pläne" + desc: "Die untere Tabelle listet die verfügbaren Spalten auf, welche in der Liste 'Meine Pläne' gezeigt werden können. + Wählen Sie, welche erscheinen sollen." + errors: + no_name: "'Name' muss in der Liste von Spalten enthalten sein." + duplicate: "Doppelter Spaltenname. Bitte jede Spalte nur einmal einfügen." + unknown: "Unbekannter Spaltenname." + plans: + title: "Plantitel" + reset: "Zurücksetzen" + custom_formatting: "(Verwende eigene Werte bei PDF-Formatierung)" + template_formatting: "(Verwende Vorlagenwerte bei PDF-Formatting)" + default_formatting: "(Verwende standardmäßige Werte bei PDF-Formatierung)" + included_elements: "Enthaltene Elemente" + pdf_formatting: "PDF Formatierung" + font: "Schrift" + font_face: "Schriftart" + font_size: "Größe" + margin: "Rand" + margins: + top: "Oben" + bottom: "Unten" + left: "Links" + right: "Rechts" + max_pages: "Maximale Anzahl von Seiten" + errors: + missing_key: "Eine benötigte Einstellung wurde nicht erbracht" + invalid_margin: "Randwert ist ungültig" + negative_margin: "Rand darf nicht negativ sein" + unknown_margin: "Unbekannter Rand. Kann nur 'oben', 'unten', 'links' oder 'rechts' sein" + invalid_font_size: "Ungültige Schriftgröße" + invalid_font_face: "Ungültige Schriftart" + unknown_key: "Unbekannte Formatierungseinstellung" + invalid_max_pages: "Ungültige maximale Anzahl von Seiten" + mailer: + sharing_notification: "Ihnen wurde Zugang zu einem Datenmanagementplan gewährt" + permissions_change: "DMP-Zulassungen geändert" + access_removed: "DMP-Zugriff entfernt" + + about_page: + title: "Über DMPonline" + tab_1: "Hintergrund" + tab_2: "Neuigkeiten" + body_text_tab_1_html: "+ Fördergeber verlangen zunehmend die Erstellung von Datenmanagementplänen von den Antragstellern, bzw. Förderempfängern, sowohl in der Antragsphase als auch während der Durchführung. DMPonline wurde vom Digital Curation Centre (UK) erstellt, um es Forschenden zu ermöglichen, auf diese Anforderungen zu reagieren und dabei auch die Vorgaben ihrer Institutionen oder anderen Beteiligten zu erfüllen. +
++ Die Entwicklung fand in Kooperation mit Forschungsförderern und Universitäten statt, um ein Werkzeug für die Erstellung von probaten Datenmanagementplänen während des gesamten Projektverlaufs anbieten zu können. +
++ Es gibt eine Reihe von Vorlagen innerhalb der Applikation, die den Anforderungen der verschiedenen Förderer oder Institutionen entsprechen. Die Nutzer beantworten zu Begin der Erstellung eines Plans drei Fragen, um die Anzeige der geeigneten Vorlage zu erlauben (z.B. die ESRC-Vorlage bei einer ESRC-Förderung). Die Applikation gibt Hilfestellungen zum Verstehen und Beantworten der Fragen; diese werden von Forschenden, Förderern, Universitäten und den verschiedenen Disziplinen bereitgestellt. +
+Falls sie einen Zugang haben, melden sie sich an und beginnen ihren Datenmanagementplan zu erstellen.
+Falls sie keinen Zugang zu DMPonline haben, wählen sie 'Registrieren' auf der Startseite aus.
+Besuchen sie die 'Hilfe'-Seite für eine Anleitung.
+Die deutsche Version von DMPonline wird in Kooperation mit dem Digital Curation Centre (UK) und der Bibliothek der Universität von Alberta (CA) im Rechenzentrum der Christian-Albrechts-Universität gepflegt.
+Die Benutzungsschnittstelle und die Funktionalität von DMPonline wird kontinuierlich verbessert. Falls sie gerne Rückmeldung geben oder Verbesserungsvorschläge machen möchten, freuen wir uns, wenn sie uns eine Nachricht an +vfu@rz.uni-kiel.de schicken.
+Geschichten zu DMPonline auf der DCC-Seite
" + + help_page: + title: "Hilfe" + tab_1: "DMPonline" + tab_2: "Datenmanagement-Planung" + body_text_tab_2_html: " +Nach der Anmeldung in DMPonline werden sie zur 'Meine Pläne'-Seite weitergeleitet. Dies ist der Startpunkt, um ihre Pläne zu Edieren, zu Teilen oder zu löschen. Sie sehen außerdem, welche Pläne sie mit anderen geteilt haben.
+Um einen Plan zu erstellen, klicken sie auf den 'Plan erstellen'-Knopf auf der 'Meine Pläne'-Seite, oder im Hauptmenü. Wählen sie die passenden Optionen in den Ausklappmenüs und Auswahlboxen aus, um zu bestimmen, welche Fragen und Hilfestellungen ihnen angezeigt werden sollen. Bestätigen sie ihre Auswahl durch das Klicken von 'Ja, Plan erstellen'.
+Die Reiter der Benutzerschnittstelle erlauben ihnen durch die verschiedenen Bereiche zu navigieren wenn sie ihren Plan bearbeiten.
+In den Fragereitern sind die verschiedenen Abschnitte ihres Plans dargestellt, die sich durch anklicken zur Bearbeitung auswählen lassen. Die Antworttexte können mit den Textbearbeitungsknöpfen formatiert werden.
+Hilfestellungen werden rechts von den Fragen durch klicken des '+'-Symbols angezeigt.
+Bitte vergessen sie nicht ihre Antworten zu speichern, bevor sie die Seite verlassen.
+Geben sie die E-Mail-Adresse der Person an, die ihren Plan lesen oder bearbeiten können sollen. Mithilfe des Ausklappmenüs können sie die Befugnisse, die die Person im Bezug auf den Plan haben soll, auswählen. Klicken sie abschließend auf 'Mitarbeitende(n) hinzufügen'.
+Wählen sie das Dateiformat aus, in das sie ihren Plan exportieren möchten und klicken sie 'Export'. Unterhalb des Dialogs können sie durch klicken auf das '+'-Symbol detaillierte Einstellungen zum Export vornehmen.
" + + + + contact_page: + title: "Kontakt" + intro_text_html: "DMP Builder is provided by the University of Alberta Libraries. You can find out more about us on our Research Data Management page. If you would like to contact us about DMP Builder, please insert your query into the webform below or email data@ualberta.ca.
+ " + + terms_page: + title: "Nutzungsbedingungen" + body_text_html: "+ Dies ist eine Testinstallation von DMPonline. DMPonline wird vom Digital Curation Centre (DCC) entwickelt und gepflegt und steht unter einer AGPL Lizenz als Open Source Software zur Verfügung. +
++ Die Testinstallation dient lediglich der Weiterentwicklung und Evaluation der Software und ist nicht für den Produktiveinsatz gedacht. +
++ Diese Testinstallation wird in absehbarer Zeit wieder abgeschaltet werden. Die Daten, die in dieser Installation erstellt wurden, werden bei der Abschaltung verloren gehen. Wichtige Daten sollten nicht ausschließlich in der Testinstallation gespeichert werden. +
+Ihr Passwort wird in verschlüsselter Form gespeichert und kann nicht wieder hergestellt werden. Falls Sie es verlieren, muss es neu gesetzt werden.
+Bei Benutzung dieser Anwendung stimmen Sie den Nutzungsbedingungen zu.
+Universität Kiel, Kiel, SH, Deutschland
Nutzungsbedingungen
Willkommen zu DMPonline, %{email}
+Danke für Ihre Registrierung bei %{app_link}. Bitte bestätigen Sie Ihre E-Mail-Adresse:
+%{confirmation_link} (oder kopieren Sie %{confirmation_direct_url} in Ihren Browser).
" + reset_password_instructions: + subject: "DMPonline - Passwort zurücksetzen" + link: "Ändere mein Passwort" + email: "Hallo %{resource_email}!
+Jemand hat einen Link angefordert, um Ihr Passwort für %{app_link} zurückzusetzen. Dies kann durch den unteren Link geschehen.
+%{reset_password_link}
+Wenn diese Anfrage nicht von Ihnen ist, können Sie diese Email ignorieren.
+Ihr Passwort ändert sich erst, wenn Sie obigen Link verwenden, um ein Neues zu setzen.
" + unlock_instructions: + subject: "DMPonline - Zugang entsperren" + link: "Entsperre meinen Zugang" + email: "Hallo %{resource_email}!
+Ihr %{app_link} Zugang würde wegen übermäßiger Anmeldungsversuche gesperrt.
+Verwenden Sie den unteren Link, um Ihren Zugang zu entsperren:
+%{unlock_link}
" + omniauth_callbacks: + failure: "Sie konnten mit Ihrem %{kind}-Zugang nicht authentifiziert werden, da '%{reason}'." + success: "Sie haben sich erfolgreich mit Ihrem %{kind}-Zugang angemeldet." + passwords: + no_token: "Sie können diese Seite nur über einen Verweis in einer E-Mail zum Zurücksetzen des Passworts aufrufen. Sollten Sie einen solchen Verweis aufgerufen haben, stellen Sie bitte sicher, dass Sie die vollständige URL aufgerufen haben." + send_instructions: "Sie erhalten in wenigen Minuten eine E-Mail mit einer Anleitung zum Zurücksetzen Ihres Passworts." + send_paranoid_instructions: "Falls Ihre E-Mail-Adresse in unserer Datenbank existiert, erhalten Sie in wenigen Minuten eine E-Mail mit einer Anleitung zum Zurücksetzen Ihres Passworts." + updated: "Ihr Passwort wurde geändert. Sie sind jetzt angemeldet." + updated_not_active: "Ihr Passwort wurde geändert." + registrations: + destroyed: "Ihr Zugang wurde gelöscht." + signed_up: "Sie haben sich erfolgreich registriert." + signed_up_but_inactive: "Sie haben sich erfolgreich registriert. Sie können sich jedoch z.Z. nicht anmelden, da Ihr Zugang inaktiv ist." + signed_up_but_locked: "Sie haben sich erfolgreich registriert. Sie können sich jedoch z.Z. nicht anmelden, da Ihr Zugang gesperrt ist." + signed_up_but_unconfirmed: "Sie haben kürzlich eine E-Mail mit einer Anleitung zur Bestätigung Ihres Zugangs erhalten. Bitte öffnen Sie den dort angegebenen URL um Ihren Zugang zu aktivieren." + update_needs_confirmation: "Sie haben erfoglreich die Nutzerdetails geändert, jedoch muss Ihre neue E-Mail-Adresse überprüft werden. Sie haben eine entsprechende E-Mail erhalten; bitte öffnen Sie den dort angegebenen URL um Ihre neue E-Mail-Adresse zu bestätigen." + updated: "Ihre Zugang wurde erfolgreich aktualisiert." + sessions: + signed_in: "Erfolgreich angemeldet." + signed_out: "Erfolgreich abgemeldet." + unlocks: + send_instructions: "Sie erhalten in wenigen Minuten eine E-Mail mit einer Anleitung zur Entsperrung Ihres Zugangs." + send_paranoid_instructions: "Falls Deine E-Mail-Adresse in unserer Datenbank existiert, erhalten Sie in wenigen Minuten eine E-Mail mit einer Anleitung zur Entsperrung Ihres Zugangs." + resend_unlock_instructions: "Sende erneut Anleitung zur Entsperrung." + unlocked: "Ihr Zugang wurde erfolgreich entsperrt. Bitte melden Sie sich an um fortzufahren." + errors: + messages: + already_confirmed: "wurde bereits bestätigt. Bitte versuchen Sie, sich anzumelden." + confirmation_period_expired: "muss innerhalb %{period} bestätigt werden, bitte wiederholen Sie den Vorgang." + expired: "ist abgelaufen, bitte erneut anfordern" + not_found: "nicht gefunden" + not_locked: "war nicht gesperrt" + not_saved: + one: "Ein Fehler hat verhindert, dass %{resource} gespeichert werden konnte:" + other: "%{count} Fehler haben verhindert, dass %{resource} gespeichert werden konnte:" diff --git a/config/locales/devise.en-UK.yml b/config/locales/devise.en-UK.yml new file mode 100644 index 0000000..b19053b --- /dev/null +++ b/config/locales/devise.en-UK.yml @@ -0,0 +1,59 @@ +# Additional translations at https://github.com/plataformatec/devise/wiki/I18n + +en: + devise: + confirmations: + confirmed: "Your account was successfully confirmed. Please sign in." + send_instructions: "You will receive an email with instructions about how to confirm your account in a few minutes." + send_paranoid_instructions: "If your email address exists in our database, you will receive an email with instructions about how to confirm your account in a few minutes." + failure: + already_authenticated: "You are already signed in." + inactive: "Your account was not activated yet." + invalid: "Invalid email or password." + invalid_token: "Invalid authentication token." + locked: "Your account is locked." + not_found_in_database: "Invalid email or password." + timeout: "Your session expired, please sign in again to continue." + unauthenticated: "You need to sign in or sign up before continuing." + unconfirmed: "You have to confirm your account before continuing." + mailer: + confirmation_instructions: + subject: "Confirm your DMPonline account" + reset_password_instructions: + subject: "Reset password instructions" + unlock_instructions: + subject: "Unlock Instructions" + omniauth_callbacks: + failure: "Could not authenticate you from %{kind} because \"%{reason}\"." + success: "Successfully authenticated from %{kind} account." + passwords: + no_token: "You can't access this page without coming from a password reset email. If you do come from a password reset email, please make sure you used the full URL provided." + send_instructions: "You will receive an email with instructions about how to reset your password in a few minutes." + send_paranoid_instructions: "If your email address exists in our database, you will receive a password recovery link at your email address in a few minutes." + updated: "Your password was changed successfully. You are now signed in." + updated_not_active: "Your password was changed successfully." + registrations: + destroyed: "Bye! Your account was successfully cancelled. We hope to see you again soon." + signed_up: "Welcome! You have signed up successfully." + signed_up_but_inactive: "You have signed up successfully. However, we could not sign you in because your account is not yet activated." + signed_up_but_locked: "You have signed up successfully. However, we could not sign you in because your account is locked." + signed_up_but_unconfirmed: "A message with a confirmation link has been sent to your email address. Please open the link to activate your account. If you do not receive the confirmation email, please check your spam filter." + update_needs_confirmation: "You updated your account successfully, but we need to verify your new email address. Please check your email and click on the confirm link to finalize confirming your new email address." + updated: "You updated your account successfully." + sessions: + signed_in: "Signed in successfully." + signed_out: "Signed out successfully." + unlocks: + send_instructions: "You will receive an email with instructions about how to unlock your account in a few minutes." + send_paranoid_instructions: "If your account exists, you will receive an email with instructions about how to unlock it in a few minutes." + unlocked: "Your account has been unlocked successfully. Please sign in to continue." + errors: + messages: + already_confirmed: "was already confirmed, please try signing in" + confirmation_period_expired: "needs to be confirmed within %{period}, please request a new one" + expired: "has expired, please request a new one" + not_found: "not found" + not_locked: "was not locked" + not_saved: + one: "1 error prohibited this %{resource} from being saved:" + other: "%{count} errors prohibited this %{resource} from being saved:" diff --git a/config/locales/devise.en.yml b/config/locales/devise.en.yml deleted file mode 100644 index b19053b..0000000 --- a/config/locales/devise.en.yml +++ /dev/null @@ -1,59 +0,0 @@ -# Additional translations at https://github.com/plataformatec/devise/wiki/I18n - -en: - devise: - confirmations: - confirmed: "Your account was successfully confirmed. Please sign in." - send_instructions: "You will receive an email with instructions about how to confirm your account in a few minutes." - send_paranoid_instructions: "If your email address exists in our database, you will receive an email with instructions about how to confirm your account in a few minutes." - failure: - already_authenticated: "You are already signed in." - inactive: "Your account was not activated yet." - invalid: "Invalid email or password." - invalid_token: "Invalid authentication token." - locked: "Your account is locked." - not_found_in_database: "Invalid email or password." - timeout: "Your session expired, please sign in again to continue." - unauthenticated: "You need to sign in or sign up before continuing." - unconfirmed: "You have to confirm your account before continuing." - mailer: - confirmation_instructions: - subject: "Confirm your DMPonline account" - reset_password_instructions: - subject: "Reset password instructions" - unlock_instructions: - subject: "Unlock Instructions" - omniauth_callbacks: - failure: "Could not authenticate you from %{kind} because \"%{reason}\"." - success: "Successfully authenticated from %{kind} account." - passwords: - no_token: "You can't access this page without coming from a password reset email. If you do come from a password reset email, please make sure you used the full URL provided." - send_instructions: "You will receive an email with instructions about how to reset your password in a few minutes." - send_paranoid_instructions: "If your email address exists in our database, you will receive a password recovery link at your email address in a few minutes." - updated: "Your password was changed successfully. You are now signed in." - updated_not_active: "Your password was changed successfully." - registrations: - destroyed: "Bye! Your account was successfully cancelled. We hope to see you again soon." - signed_up: "Welcome! You have signed up successfully." - signed_up_but_inactive: "You have signed up successfully. However, we could not sign you in because your account is not yet activated." - signed_up_but_locked: "You have signed up successfully. However, we could not sign you in because your account is locked." - signed_up_but_unconfirmed: "A message with a confirmation link has been sent to your email address. Please open the link to activate your account. If you do not receive the confirmation email, please check your spam filter." - update_needs_confirmation: "You updated your account successfully, but we need to verify your new email address. Please check your email and click on the confirm link to finalize confirming your new email address." - updated: "You updated your account successfully." - sessions: - signed_in: "Signed in successfully." - signed_out: "Signed out successfully." - unlocks: - send_instructions: "You will receive an email with instructions about how to unlock your account in a few minutes." - send_paranoid_instructions: "If your account exists, you will receive an email with instructions about how to unlock it in a few minutes." - unlocked: "Your account has been unlocked successfully. Please sign in to continue." - errors: - messages: - already_confirmed: "was already confirmed, please try signing in" - confirmation_period_expired: "needs to be confirmed within %{period}, please request a new one" - expired: "has expired, please request a new one" - not_found: "not found" - not_locked: "was not locked" - not_saved: - one: "1 error prohibited this %{resource} from being saved:" - other: "%{count} errors prohibited this %{resource} from being saved:" diff --git a/config/locales/devise.fr.yml b/config/locales/devise.fr.yml new file mode 100644 index 0000000..87a03be --- /dev/null +++ b/config/locales/devise.fr.yml @@ -0,0 +1,82 @@ +# Additional translations at https://github.com/plataformatec/devise/wiki/I18n + +fr: + devise: + confirmations: + confirmed: "Votre compte a bien été validé. Veuillez vous connecter." + send_instructions: "Vous recevrez dans quelques minutes un courriel contenant les directives pour activer votre compte." + resend_instructions: "Envoyer de nouveau les directives" + send_paranoid_instructions: "Si votre adresse électronique existe dans notre base de données, vous recevrez dans quelques minutes un courriel contenant les directives pour valider votre compte." + failure: + already_authenticated: "Vous êtes déjà connecté(e)." + inactive: "Votre compte n'est pas encore activé." + invalid: "Courriel ou mot de passe incorrect." + invalid_token: "Jeton d'authentification incorrect." + locked: "Votre compte est verrouillé." + not_found_in_database: "Courriel ou mot de passe incorrect." + timeout: "Votre session est expirée. Veuillez vous reconnecter pour continuer." + unauthenticated: "Vous devez vous connecter ou vous inscrire pour continuer." + unconfirmed: "Vous devez confirmer votre compte pour continuer." + mailer: + app_name: "Assistant PGD" + confirmation_instructions: + subject: "Valider votre compte Assistant PGD" + link: "Cliquer ici pour activer votre compte" + email: "Bienvenue dans l'Assistant PGD, %{email}
+Merci de vous être inscrit(e) à %{app_link}. Veuillez confirmer votre adresse électronique :
+%{confirmation_link} (ou copier %{confirmation_direct_url} dans votre navigateur).
" + reset_password_instructions: + subject: "Directives pour réinitialiser le mot de passe" + link: "Réinitialiser mon mot de passe" + email: "Bonjour %{resource_email}!
+Un changement de mot de passe a été demandé pour %{app_link}. Vous pouvez le faire en cliquant sur le lien ci-dessous.
+%{reset_password_link}
+Si vous n'avez pas demandé ce changement, veuillez ignorer ce message.
+Votre mot de passe ne sera pas changé tant que vous n'aurez pas accédé au lien ci-dessus pour en créer un nouveau.
" + unlock_instructions: + subject: "Directives de déverrouillage" + link: "Déverrouiller mon compte" + email: "Bonjour %{resource_email}!
+Votre compte %{app_link} a été verrouillé à la suite d'un trop grand nombre de tentatives d'authentification.
+Cliquez sur le lien ci-dessous pour déverrouiller votre compte :
+%{unlock_link}
" + omniauth_callbacks: + failure: "Nous n'avons pas pu vous authentifier à partir de %{kind} parce que '%{reason}'." + success: "Authentification réussie à partir du compte %{kind}." + passwords: + no_token: "Vous ne pouvez pas accéder à cette page sans y avoir été dirigé par un courriel de réinitialisation du mot de passe. Si vous avez été dirigé vers cette page à partir d’un courriel de réinitialisation, assurez-vous d'utiliser l'adresse URL complète fournie." + send_instructions: "Vous recevrez dans quelques minutes un courriel contenant les directives pour réinitialiser le mot de passe." + send_paranoid_instructions: "Si votre adresse électronique existe dans notre base de données, vous recevrez dans quelques minutes un lien de récupération du mot de passe par courriel." + updated: "Votre mot de passe a bien été modifié. Vous êtes maintenant connecté." + updated_not_active: "Votre mot de passe a bien été modifié." + registrations: + destroyed: "Votre compte a bien été supprimé. Nous espérons vous revoir bientôt." + signed_up: "Bienvenu(e)! Vous êtes bien inscrit(e)." + signed_up_but_inactive: "Vous êtes bien inscrit(e). Cependant, vous ne pouvez pas vous connecter, car votre compte n'est pas encore activé." + signed_up_but_locked: "Vous êtes bien inscrit(e). Cependant, vous ne pouvez pas vous connecter, car votre compte est verrouillé." + signed_up_but_unconfirmed: "Un message contenant un lien de confirmation a été envoyé à votre adresse électronique. Ouvrez ce lien pour activer votre compte. Si vous n’avez pas reçu le courriel de confirmation, vérifiez votre filtre antipourriel." + update_needs_confirmation: "Votre compte a bien été mis à jour, mais nous devons vérifier votre nouvelle adresse électronique. Vérifiez vos courriels et cliquez sur le lien de confirmation pour finaliser la validation de votre nouvelle adresse électronique." + updated: "Votre compte a bien été modifié." + sessions: + signed_in: "Connecté" + signed_out: "Déconnecté" + unlocks: + send_instructions: "Vous recevrez dans quelques minutes un courriel contenant les directives pour déverrouiller votre compte." + send_paranoid_instructions: "Si votre compte existe, vous recevrez dans quelques minutes un courriel contenant les directives pour le déverrouiller." + resend_unlock_instructions: "Envoyer de nouveau les directives de déverouillage." + unlocked: "Votre compte a bien été déverrouillé. Veuillez vous connecter pour continuer." + errors: + messages: + already_confirmed: "a déjà été validé, essayez de vous connecter." + confirmation_period_expired: "à confirmer dans les %{period}. Veuillez faire une nouvelle demande." + expired: "a expiré, veuillez faire une nouvelle demande." + not_found: "n'a pas été trouvé" + not_locked: "n'était pas verrouillé" + not_saved: + one: "Une erreur a empêché d’enregistrer ce(tte) %{resource} :" + other: "%{count} erreurs ont empêché d’enregistrer ce(tte) %{resource} :" + blank: "Ce champ ne peut être vide" + activerecord: + attributes: + user: + email: "Courriel: " diff --git a/config/locales/devise_invitable.de.yml b/config/locales/devise_invitable.de.yml new file mode 100644 index 0000000..2f5e1a7 --- /dev/null +++ b/config/locales/devise_invitable.de.yml @@ -0,0 +1,23 @@ +de: + devise: + invitations: + send_instructions: 'Eine Einladungs-E-Mail wurde an %{email} versendet.' + invitation_token_invalid: 'Das bereitgestellte Einladungs-Token ist ungültig.' + updated: 'Ihr Passwort wurde erfolgreich gesetzt. Sie sind jetzt angemeldet.' + no_invitations_remaining: "Keine Einladungen verbleibend." + invitation_removed: 'Ihre Einladung wurde entfernt.' + new: + header: "Einladung versenden" + submit_button: "Einladung senden" + edit: + header: "Passwort setzen" + submit_button: "Passwort setzen" + mailer: + invitation_instructions: + subject: 'DMPonline - Anleitung zur Einladung' + link: "Klicken Sie hier, um die Einladung anzunehmen" + email: "Hallo %{resource_email}!
+Ein Kollege hat Sie eingeladen, um an seinem Datenmanagementplan (DMP) %{app_link}
+%{invitation_link} (oder kopiere %{invitation_direct_url} in Deinen Browser).
+Falls Sie die Einladung nicht annehmen wollen, ignorieren Sie bitte diese E-Mail.
+ Ihr Zugang wird nicht erstellt, bevor sie obigen Link besuchen und Ihr Passwort setzen.
Bonjour %{resource_email}!
+Vous avez été invité(e) par un(e) de vos collègues à contribuer à son plan de gestion de données (PGD) dans %{app_link}
+%{invitation_link} (ou copier %{invitation_direct_url} dans votre navigateur).
+Si vous ne voulez pas accepter l'invitation, veuillez ignorer ce message.
+ Votre compte ne sera pas créé tant que vous n'aurez pas accédé au lien ci-dessus et choisi un mot de passe.
DMPonline has been developed by the Digital Curation Centre to help you write data management plans.
" + screencast_text: "Screencast on how to use DMPonline" + screencast_error_text: "Your browser does not support the video tag." + + admin: + org_title: "Organisation name" + org: "Organisation" + orgs: "Organisations" + org_type: "Organisation type" + org_parent: "Parent organisation" + org_created_message: "Organisation was successfully created." + org_updated_message: "Organisation was successfully updated." + plans: "Plans" + title: "Title" + desc: "Description" + guidance_group: "Guidance group" + no_guidance_group: "No guidance group" + guidance: "Guidance" + guidance_lowercase: "guidance" + guidance_lowercase_on: "guidance on" + name: "Name" + abbrev: "Abbreviation" + question: "Question" + question_format: "Question Format" + questions: "Questions" + template_title: "Template title" + section_title: "Section title" + formatting: "Formatting" + max_pages: "Max Pages" + phase_title: "Phase title" + version_title: "Version title" + user_name: "Username" + firstname: "First name" + surname: "Surname" + user: "User" + user_created: 'User was successfully created.' + user_org_role: "User role on an Organisation" + user_role_type: "User role type" + user_role_type_created: 'User role type was successfully created.' + user_role_type_updated: 'User role type was successfully updated.' + user_role: "User role" + role: "Role" + user_status: "User status" + user_status_created: 'User status was successfully created.' + user_status_updated: 'User status was successfully updated.' + user_type: "User type" + user_type_created: 'User type was successfully created.' + user_type_updated: 'User type was successfully created.' + last_logged_in: "Last logged in" + version_numb: "Version number" + details: "Details" + phases: "Phases" + phase: "Phase" + version: "Version" + versions: "Versions" + sections: "Sections" + section: "Section" + multi_options: "Multiple question options" + templates: "Templates" + template: "Template" + themes: "Themes" + theme: "Theme" + theme_created: 'Theme was successfully created.' + theme_updated: 'Theme was successfully updated.' + sug_answer: "Suggested answer" + sug_answers: "Suggested answers" + old_temp_field: "old template field" + old_theme_field: "old theme field" + token_permission_type: "Token Permission Type" + permission_description: "Permission Description" + token_permission: "Token Permission" + org_token_permission: "Organisation Token Permission" +# choose_api_permissions: "Choose all API Permissions that apply." + + settings_updated: 'Settings updated successfully' + choose_themes: 'Choose all themes that apply.' + all_themes: 'All themes' + selected_themes: "Selected themes" + choose_templates: 'Choose all templates that apply.' + all_templates: 'All templates' + selected_templates: "Selected templates" + select_question_format: "Select question format" + no_template: 'No template' + no_phase: 'No phase' + no_version: 'No version' + no_section: 'No section' + + org_admin: + admin_area: "Admin area" + admin_details: "Admin Details" + template_label: "Templates" + user_list_label: "Users" + org_details_label: "Organisation details" + org_text: "These are the basic details for your organisation." + org_abbr_help_text_html: "This is what displays as a label on your guidance, e.g. 'Glasgow guidance on Metadata'. It's best to use an abbreviation or short name." + users_list: "List of users" + user_full_name: "Name" + user_name: "Email address" + last_logged_in: "Last logged in" + how_many_plans: "How many plans?" + user_text_html: "Below is a list of users registered for your organisation. You can sort the data by each field." + org_name: "Name" + org_abbr: "Abbreviation" + org_desc: "Description" + org_banner_text: "Top banner text" + org_target_url: "Website" + org_type: "Organisation type" + parent_org: "Main organisation" + last_updated: "Last updated" + desc_help_text_html: "You can write pieces of guidance to be displayed by theme (e.g. generic guidance on storage and backup that should present across the board) or you can write guidance for specific questions. Writing generic guidance by theme saves you time and effort as your advice will be automatically displayed across all templates rather than having to write guidance to accompany each.
+You will usually want your guidance to display on all templates, however there may be cases where you only want it to show for specific funders e.g. if you have specific instructions for applicants to BBSRC for example. This can be set too if needed.
" + delete_message_html: "You are about to delete '%{guidance_summary}'. Are you sure?" + guidance_group: + add_guidance_group: "Add guidance group" + guidance_group_list: "Guidance group list" + name_label: "Name" + subset: "Optional subset" + subset_eg: "e.g. School/ Department" + all_temp: "All templates" + help_text_add: "Please enter the group title" + subset_option_help_text: "If the guidance is only meant for a subset of users e.g. those in a specific college or institute, check this box. Users will be able to select to display this subset guidance when answering questions in the 'create plan' wizard." + template_help_text_html: "Select which templates you want the guidance to display on. This will usually be all templates." + title_help_text_html: "Add an appropriate name for your guidance group e.g. Glasgow guidance. This name will be used to tell the end user where the guidance has come from e.g. 'Glasgow Guidance on Metadata'" + guidance_group_text_html: "First create a guidance group. This could be institution wide or a subset e.g. a particular College / School, Institute or department. When you create guidance you'll be asked to assign it to a guidance group.
" + delete_message: "You are about to delete '%{guidance_group_name}'. This will affect guidance. Are you sure?" + created_message: "Guidance group was successfully created." + updated_message: "Guidance group was successfully updated." + destroyed_message: "Guidance group was successfully deleted." + templates: + create_template: "Create a template" + new_label: "New template" + template_details: "Template details" + edit_details: "Edit template details" + view_all_templates: "View all templates" + funders_temp: "Funders templates" + title_help_text: "Please enter a title for your template." + section_title_help_text: "Please enter section title" + help_text_html: "If you wish to add an institutional template for a Data Management Plan, use the 'create template' button. You can create more than one template if desired e.g. one for researchers and one for PhD students.
+Your template will be presented to users within your institution when no funder templates apply. If you want to add questions to funder templates use the 'customise template' options below.
" + create_new_template_text_html: "To create a new template, first enter a title and description. Once you have saved this you will be presented with options to add one or more phases.
" + desc_help_text_html: "Enter a description that helps you to differentiate between templates e.g. if you have ones for different audiences" + own_temp: "Own templates" + add_phase_label: "Add new phase +" + view_phase_label: "View phase" + edit_phase_label: "Edit phase" + back_to_edit_phase_label: "Back to edit view" + edit_phase_details_label: "Edit phase details" + phase_details_label: "Phase details" + phase_order_label: "Order of display" + phase_details_text_html: "Here you set the title that users will see. If you intend to have multiple phases for you DMP, this should be clear in the title and description.
" + phase_title_help_text: "Enter a title for the phase e.g. intial DMP, full DMP... This is what users will see in the tabs when completing a plan. If you only have one phase, call it something generic e.g. Glasgow DMP" + phase_number_help_text: "This allows you to order the phases of your template." + phase_desc_help_text_html: "Enter a basic description. This will be presented to users on the 'Admin Plan' tab, above the summary of the sections and questions which they will be asked to answer." + phase_delete_message: "You are about to delete '%{phase_title}'. This will affect versions, sections and questions linked to this phase. Are you sure?" + phase_new_text_html: "When you create a new phase for your template, a version will automatically be created. Once you complete the form below you will be provided with options to create sections and questions." + versions_label: "Versions" + version_details_label: "Version details" + add_section: "Add section" + new_section: "New section title" + section_title_placeholder: "New section title" + section_desc_help_text_html: "Select themes that are relevant to this question.
+This allows your generic institution-level guidance to be drawn in, as well as that from other sources e.g. the DCC or any Schools/Departments that you provide guidance for.
+You can select multiple themes by using the CTRL button.
" + default_answer_label: "Default answer" + guidance_label: "Guidance" + question_guidance_help_text_html: "Enter specific guidance to accompany this question. If you have guidance by themes too, this will be pulled in based on your selections below so it's best not to duplicate too much text." + delete_message: "You are about to delete '%{question_text}'. Are you sure?" + question_options_help_text_html: "Enter any options that you wish to display. If you want to pre-set one option as selected, check the default box." + + + + + + helpers: + home: "Home" + return_home: "Return to the home page" + admin_area: "Super admin area" + edit_profile: "Edit profile" + view_plans_label: "View plans" + create_plan_label: "Create plan" + about_us_label: "About" + roadmap_label: "Future plans" + help_label: "Help" + contact_label: "Contact" + jisc: "The DCC is funded by" + format: "format" + + sign_in: "Sign in" + sign_out: "Sign out" + sign_up: "Sign up" + sign_up_text: "New to DMPonline? Sign up today." + signed_in: "Signed in as " + institution_sign_in_link: "Or, sign in with your institutional credentials" + institution_sign_in: " (UK users only)" + + user_name: "Email address" + email: "Email" + subject: "Subject" + message: "Message" + valid_email: "You must enter a valid email address." + user_details_text_html: "Please note that your email address is used as your username. If you change this, remember to use your new email address on sign in.
" + user_details_paragraph_html: "You can edit any of the details below." + remember_me: "Remember me" + org_not_listed: "My organisation isn't listed." + + password: "Password" + current_password: "Current password" + new_password: "New password" + password_conf: "Password confirmation" + change_password: "Change your password" + forgot_password: "Forgot your password?" + password_too_small: "Your password must contain at least 8 characters." + password_no_match: "This must match what you entered in the previous field." + no_pass_instructions: "Didn't receive confirmation instructions?" + no_unlock_instructions: "Didn't receive unlock instructions?" + send_password_info: "Reset password instructions" + edit_password_info: "If you would like to change your password please complete the following fields." + accept_terms_html: " I accept the terms and conditions *" + you_must_accept: 'You must accept the terms and conditions to register.' + email_already_registered: 'That email address is already registered.' + email_must_valid_confirmation_message: "This must be a valid email address - a message will be sent to it for confirmation." + error_registration_check: 'Error processing registration. Please check that you have entered a valid email address and that your chosen password is at least 8 characters long.' + api_token: 'API token' + api_info: 'API Information' + api_use: 'How to use the API' + api_granted: 'You have been granted permission by your organisation to use our API.' + api_view_token: 'Your API token and instructions for using the API endpoints can be found here.' + api_mail_subject: 'API Permission Granted' + + + text_area: "Text area" + text_field: "Text field" + radio_buttons: "Radio buttons" + checkbox: "Check box" + dropdown: "Dropdown" + multi_select_box: "Multi select box" + export: "Export" + + about: + by: "By " + on: " on " + read_more: "Read more on the " + + mailer: + permission_relating: "Your permissions relating to " + changed: " have changed. You now have " + access: "access." + access_to: "Your access to " + removed: " has been removed." + given: "You have been given " + access_two: " access to " + + truncate_continued: "... (continued)" + security_check: "Security check" + error: "Error!" + comment: "Comment" + send: "Send" + yes_label: "Yes" + no_label: "No" + ok_label: "Ok" + none: "None" + false_lowercase: "false" + title: "Title" + note: "Note" + me: "Me" + view: "View" + desc: "Description" + save: "Save" + preview: "Preview" + saving: "Saving..." + loading: "Loading..." + removing: "Removing..." + unsaved: "Unsaved changes" + unlink_account: "Unlink account" + submit: + edit: "Edit" + create: "Create" + update: "Update" + cancel: "Cancel" + save: "Save" + delete: "Delete" + back: "Back" + discard: "Discard" + publish: "Publish" + + before_submitting_consider: "Before submitting, please consider:" + name: "Name" + first_name: "First name" + last_name: "Last name" + first_name_help_text: "Please enter your first name." + surname_help_text: "Please enter your surname or family name." + owner: "Owner" + orcid_id: "ORCID number" + orcid_html: "ORCID number is a persistent digital identifier that distinguishes each researcher, more info." + sign_up_shibboleth_alert_text_html: "DMPonline doesn't recognise your institutional credentials - either you haven't created an account with us or you haven't linked these details to your existing account. + --> If you do not have an account with DMPonline, please complete the form below. + --> If you have an account with DMPonline, please Sign in so we can link your account to your institutional credentials. + Once you have created and/or linked your account, you'll be able to sign in with your institutional credentials directly." + shibboleth_linked_text: "Your account is linked to your institutional credentials." + shibboleth_to_link_text: "Link your DMPonline account to your institutional credentials (UK users only)" + shibboleth_unlink_label: "Unlink your institutional credentials" + shibboleth_unlink_alert: "Unlink institutional credentials alert" + shibboleth_unlink_dialog_text: "You are about to unlink DMPonline of your institutional credentials, would you like to continue?
" + + select_phase: "Select a phase" + select_version: "Select a version" + select_section: "Select a section" + select_question: "Select a question" + select_template: "Select a template" + + main_email: + from: 'info@dcc.ac.uk' + access_given: "You have been given access to a Data Management Plan" + permission_changed: "DMP permissions changed" + access_removed: "DMP access removed" + + + section_label: "Section" + sections_label: "Sections" + questions_label: "Questions" + answers_label: "Answers" + answer_questions: "Answer questions" + last_edit: "Last edited" + select_action: "Select an action" + answered_by: "Answered " + answered_by_part2: " by " + suggested_answer: "Suggested answer" + suggested_example: "Example answer" + notanswered: "Not answered yet" + noquestionanswered: "No questions have been answered" + guidance: "Guidance" + policy_expectations: "Policy Expectations" + export: "Export" + guidance_accordion_label: "Guidance" + add_comment_accordion_label: "Share note" + comment_accordion_label: "Notes" + + comments: + add_comment_label: "Add note" + add_comment_text: "Share note with collaborators" + comment_label: "Note" + comments_label: "Notes" + view_label: "View" + edit_label: "Edit" + retract_label: "Remove" + clear_label: "Remove" + commented_by: "Noted by:" + archive_own_comment_question: "Are you sure you would like to remove this note?" + archive_own_comment_button_label: "Remove" + archive_comment_question: "Are you sure you would like to remove this note?" + archive_comment_button_label: "Remove" + clear_by: "Note removed by" + retracted: "Note removed by you" + comment_created: 'Comment was successfully created.' + comment_updated: 'Comment was successfully updated.' + comment_removed: 'Comment has been removed.' + + + org_type: + funder: "Funder" + institution: "Institution" + project: "Project" + organisation: "Organisation" + org_name: "Organisation name" + school: "School" + publisher: "Publisher" + other_guidance: "Other guidance" + template: "Template" + templates: "Templates" + child: "Unit" + other_org_help_text: "Please enter the name of your organisation." + + + project: + create: "Create plan" + edit: "Edit plan details" + grant_title: "Grant number" + grant_help_text: "Grant reference number if applicable [POST-AWARD DMPs ONLY]" + not_applicable: "Not applicable/not listed." + multi_templates: "There are a number of possible templates you could use. Please choose one." + project_name: "Plan name" + my_project_name: "My plan" + success: "Plan was successfully created." + success_update: "Plan was successfully updated." + principal_investigator: "Principal Investigator/Researcher" + principal_investigator_help_text: "Name of Principal Investigator(s) or main researcher(s) on the project." + principal_investigator_id: "Principal Investigator/Researcher ID" + principal_investigator_id_help_text: "E.g ORCID http://orcid.org/." + funder_help_text: "Research funder if relevant" + funder_name: "Funder name" + project_question_desc_label: "Summary about the questions" + tab_plan: "Plan details" + tab_export: "Export" + export_text_html: "From here you can download your plan in various formats. This may be useful if you need to submit your plan as part of a grant application. +Select what format you wish to use and click to 'Export'.
" + questions_answered: "questions answered" + not_saved_answers_text_alert: "You have altered answers but have not saved them:" + not_saved_answers_confirmation_alert: "Would you like to save them now?" + not_saved_answers_header: "Unsaved answers" + answer_recorded: 'Answer was successfully recorded.' + answer_error: 'There was an error saving the answer.' + answer_no_change: 'No change in answer content - not saved.' + project_data_contact: "Plan data contact" + project_data_contact_help_text: "Name (if different to above), telephone and email contact details" + project_name_help_text: "If applying for funding, state the name exactly as in the grant proposal." + project_desc_help_text_html: "Briefly summarise the type of study (or studies) to help others understand the purposes for which the data are being collected or created.
Welcome. You are now ready to create your first DMP.Click the 'Create plan' button below to begin.
" + project_text_when_project: "The table below lists the plans that you have created, and any that have been shared with you by others.These can be edited, shared, exported or deleted at anytime.
" + project_details_text_html: "This page gives you an overview of your plan. It tells what your plan is based on and gives an overview of the questions that you will be asked." + project_details_editing_text_html: "Please fill in the basic project details below and click 'Update' to save" + confirm_delete_text: "Are you sure you wish to delete this plan? If the plan is being shared with other users, by deleting it from your list, the plan will be deleted from their plan list as well" + confirmation_text: "Confirm plan details" + confirmation_text_desc: "Where your funder or institution doesn't have specific requirements (or if you left these options blank), you will see the DCC Checklist. This offers a generic set of DMP questions and guidance. For more details see: DMP checklist 2013." + confirmation_button_text: "Yes, create plan" + default_confirmation_text_desc: "You have selected the Default DMP, which is based on the DCC Checklist. This offers a generic set of DMP questions and guidance. For more details see: DMP checklist 2013." + default_confirmation_button_text: "Create plan" + alert_default_template_text_html: "Please note: %{org_name} provides a DMP template. If you wish to use it select 'Cancel', otherwise select 'Create plan'" + share: + tab_share: "Share" + shared_label: "Shared?" + share_text_html: "You can give other people access to your plan here. There are three permission levels.
Add each collaborator in turn by entering their email address below, choosing a permission level and clicking \"Add collaborator\".
Those you invite will receive an email notification that they have access to this plan, inviting them to register with DMPonline if they don't already have an account. A notification is also issued when a user's permission level is changed.
" + collaborators: "Collaborators" + add_collaborator: "Add collaborator" + add: "Add" + permissions: "Permissions" + permissions_desc: "Editors can contribute to plans. Co-owners have additional rights to edit plan details and control access." + remove: "Remove user access" + confirmation_question: "Are you sure?" + owner: "Owner" + co_owner: "Co-owner" + edit: "Edit" + read_only: "Read only" + locked_section_text: "This section is locked for editing by " + create_page: + title: "Create a new plan" + desc_html: "Please select from the following drop-downs so we can determine what questions and guidance should be displayed in your plan.
+If you aren't responding to specific requirements from a funder or an institution, select here to write a generic DMP based on the most common themes.
" + default_template: "Default DMP" + funders_question: "If applying for funding, select your research funder." + funders_question_description: "Otherwise leave blank." + other_funder_name_label: "Name of funder, if applicable." + institution_question: "To see institutional questions and/or guidance, select your organisation." + institution_question_description: "You may leave blank or select a different organisation to your own." + other_guidance_question: "Tick to select any other sources of guidance you wish to see." + configure: "Configure" + columns: + name: "Name" + owner: "Owner" + shared: "Shared?" + template_owner: "Template Owner" + last_edited: "Last edited" + identifier: "Identifier" + grant_number: "Grant number" + principal_investigator: "Principal Investigator / Researcher" + data_contact: "Plan data contact" + description: "Description" + filter: + placeholder: "Filter plans" + submit: "Filter" + cancel: "Cancel" + no_plans_match: "No plans match '%{filter}'" + no_matches: "No matches" + user_added: "User added to project" + invitation_success: 'Invitation issued successfully.' + enter_email: "Please enter an email address" + sharing_updated: 'Sharing details successfully updated.' + access_removed: 'Access removed' + update_success: 'Project was successfully updated.' + create_success: 'Project was successfully created.' + details_update_success: "Details successfully updated." + choose_template: "Choose a template" + + plan: + export: + pdf: + question_not_answered: "Question not answered." + generated_by: "This document was generated by DMPonline (http://dmponline.dcc.ac.uk)" + space_used: "approx. %{space_used}% of available space used (max %{num_pages} pages)" + space_used_without_max: "approx. %{space_used}% of available space used" + project_name: "Project Name" + project_identifier: "Project Identifier" + grant_title: "Grant Title" + principal_investigator: "Principal Investigator / Researcher" + project_data_contact: "Project Data Contact" + project_description: "Description" + funder: "Funder" + institution: "Institution" + not_valid_format: '%{value}% is not a valid format' + + settings: + title: "Settings" + projects: + title: "Settings - My plans" + desc: "The table below lists the available columns that can be shown on the 'My plans' list. Choose which you would like to appear." + errors: + no_name: "'name' must be included in column list." + duplicate: "Duplicate column name. Please only include each column once." + unknown: "Unknown column name." + plans: + title: "Plan title" + reset: "Reset" + description: "Description" + custom_formatting: "(Using custom PDF formatting values)" + template_formatting: "(Using template PDF formatting values)" + default_formatting: "(Using default PDF formatting values)" + included_elements: "Included Elements" + pdf_formatting: "PDF Formatting" + font_face: "Face" + font_size: "Size" + font: "Font" + margin: "Margin" + margins: + top: "Top" + bottom: "Bottom" + left: "Left" + right: "Right" + max_pages: "Maximum number of pages" + errors: + missing_key: "A required setting has not been provided" + invalid_margin: "Margin value is invalid" + negative_margin: "Margin cannot be negative" + unknown_margin: "Unknown margin. Can only be 'top', 'bottom', 'left' or 'right'" + invalid_font_size: "Invalid font size" + invalid_font_face: "Invalid font face" + unknown_key: "Unknown formatting setting" + invalid_max_pages: "Invalid maximum pages" + no_access_account: "This account does not have access to that plan." + + about_page: + title: "About DMPonline" + tab_1: "Background" + tab_2: "Latest news" + + body_text_tab_1_html: "Funding bodies increasingly require their grant-holders to produce Data Management Plans(DMP), both during the bid-preparation stage and after funding has been secured. DMPonline has been produced by the UK's Digital Curation Centre to help research teams respond to this requirement, and any expectations that their institution or others may apply.
+The DCC has worked closely with research funders and universities to produce a tool that assists researchers to produce an effective data management plan (DMP) to cater for the whole lifecycle of a project, from bid-preparation stage through to completion.
+ +There are a number of templates within the tool that represent the requirements of different funders and institutions. Users are asked three questions at the outset so we can determine the appropriate template to display (e.g. the ESRC template when applying for an ESRC grant). Guidance is provided to help you interpret and answer the questions. This guidance is provided by researcher funders, universities and disciplines.
+ +If you have an account please sign in and start creating or editing your DMP.
+If you do not have a DMPonline account, click on 'Sign up' on the homepage.
+Please visit the 'Help' page for guidance.
+ +We are constantly improving the user interface and functionality of DMPonline. + If you would like to contribute with feedback and suggestions, please contact us by emailing + dmponline@dcc.ac.uk. You can also report bugs and request new features directly on GitHub
+If you need to access plans from the earlier version of the tool please visit DMPonline v3.
" + + body_text_tab_2_html: "DMPonline stories from the DCC website
" + + help_page: + title: "Help" + tab_1: "On DMPonline" + tab_2: "On data management planning" + body_text_tab_2_html: "When you login to DMPonline you will be directed to the 'My plans' page. From here you can edit, share, export or delete any of your plans. You will also see plans that have been shared with you by others.
+To create a plan, click the 'Create plan' button from the 'My plans' page or the top menu. Select options from the drop-down menus and tickboxes to determine what questions and guidance you should be presented with. Confirm your selection by clicking 'Yes, create plan'
+The tabbed interface allows you to navigate through different functions when editing your plan.
+When viewing any of the question tabs, you will see the different sections of your plan displayed. Click into these in turn to answer the questions. You can format your responses using the text editing buttons.
+Guidance is displayed in the right-hand panel. Click the '+' symbol to view this.
+Remember to 'save' your responses before moving on.
+Insert the email address of any collaborators you would like to invite to read or edit your plan. Set the level of permissions you would like to grant them via the drop-down options and click to 'Add collaborator'
+From here you can download your plan in various formats. This may be useful if you need to submit your plan as part of a grant application. Choose what format you would like to view/download your plan in and click to export. When you login to DMPonline you will be directed to the 'My plans' page. From here you can edit, share, export or delete any of your plans. You will also see plans that have been shared with you by others.
+If you need to access plans from the earlier version of the tool please visit DMPonline v3.
" + + contact_page: + title: "Contact us" + intro_text_html: "DMPonline is provided by the Digital Curation Centre. You can find out more about us on our website. If you would like to contact us about DMPonline, please enter your query in the form below or email dmponline@dcc.ac.uk.
" + github_text_html: "If you have a feature request or think you have found a bug, please check out the list of issues on GitHub. If your issue isn't listed there, please add it; if it is, please add a comment if you have more information or just to let us know how important it is to you. This will help us to help us prioritise future developments.
" + address_text_html: "Tel. +44 (0) 131 651 1239
+Email dmponline@dcc.ac.uk
" + + roadmap_page: + title: "Future plans" + tab_1: "Releases" + tab_2: "Get involved" + body_text_tab_1_html: "The DCC is collaborating with the DMPTool team to develop a joint codebase for Data Management Planning called DMP Roadmap. Both of our tools will be delivered using this in the future. We've agreed what features need to be included and are planning a few sprints to deliver these. The initial release will include all of the main priorities we already had flagged, including:
+DMPonline has an active and growing user base, and we are grateful to the members who suggest ideas for new and improved features. If you would like to help shape our future plans, please join the user group. More information on how you can engage with us is available under the 'Get involved' tab.
+ +The current version of DMPonline is 4.2. This was released in August 2015 and included Institutional branding, optional guidance for funders, improvements to the question area, improvements to the admin interface, GitHub pull requests, new seed file, and an update of the gemfile.
+ +The code is available on GitHub
+ +The previous version of DMPonline is 4.1. This was released in May 2015 and included a comment feature, improved guidance on signing in with institutional credentials, enhanced deployment guidance and proposed methods for internationalisation. Full details can be found in the release note and associated documents.
+DMPonline is developed and maintained by the UK Digital Curation Centre. We’re a small team, and are happy to collaborate with others. There are various ways you can get involved:
+We run a listserv for the DMPonline user group that you can request to join. We also host periodic meetings to consult on our plans. Being part of the user group gives you the opportunity to be informed about future developments and to provide feedback to help shape our plans.
+Our user group sessions are usually focused around a certain topic (e.g. fleshing out use cases for an API) so invites are sent based on your areas of expertise. It is helpful for us to know your role and interests to invite relevant people to each session. Please introduce yourself on the list and share your ideas.
+Notes from previous user group sessions are provided below:
+Please let us know your interests and share your ideas for future developments via the mailing list so the community as a whole can feedback on them.
+ +DMPonline can be customised by institutions and disciplines. You can add templates for users in your organisation and tailored guidance that explains local support and services. Example answers can also be offered to help users understand what to write in a Data Management Plan. To do this you’ll need to request admin access, so please email us on dmponline@dcc.ac.uk.
+Futher guidance on customising DMPonline is available on the DCC website.
+ +DMPonline is a Ruby on Rails application. The source code is made available under a GNU Affero General Public License. This permits others to reuse the code freely, but obligates you to share the source code for any extensions in the same way. Please inform us if you install an instance of DMPonline and offer your contributions back to the community.
+If you install an instance of DMPonline we require that you credit the DCC as originators of the tool. We recommend that the acknowledgement takes the form of the DMPonline logo with a link back to the DCC-hosted version of the tool.
+We are willing to work with external developers to add new features to the tool. We are also open to delivering new features on a chargeable basis. If there are extensions you would like to see prioritised and have resource to support additional developer effort, please contact us on dmponline@dcc.ac.uk to negotiate terms.
+ +We are impressed by the uptake of DMPonline both in the UK and internationally and are really keen to hear how you are using the tool and promoting it in your context. We are aware that others have run training courses, developed guidance materials and advocated use of the tool. Please notify us of this as it helps to show impact.
+We are currently investigating options for revenue generation. This will help us serve the increased demand more effectively and safeguard the long-term sustainability of DMPonline. Plans will be released for consultation soon but we also welcome your suggestions on how best to support our work.
" + + terms_page: + title: "Terms of use" + body_text_html: "The Digital Curation Centre ('DCC') is a consortium supported by Jisc and based at the Universities of Edinburgh, Glasgow and Bath. Our primary constituency is the UK research community, particularly the higher and further education sector.
+DMPonline ('the tool', 'the system') is a tool developed by the DCC as a shared resource for the research community. It is hosted at the University of Edinburgh.
+In order to help identify and administer your account with DMPonline, we need to store your email address. We may also use it to contact you to obtain feedback on your use of the tool, or to inform you of the latest developments or releases. The information may be transferred between the DCC partner institutions but only for legitimate DCC purposes. We will not sell, rent or trade any personal information you provide to us.
+The information you enter into this system can be seen by you, people you have chosen to share access with, and - solely for the purposes of maintaining the service - system administrators at the University of Edinburgh. We compile anonymised, automated and aggregated information from plans, but we will not directly access, make use of, or share your content with anyone else without your permission. Authorised officers of your home institution may access your plans for specific purposes - for example, to track compliance with funder/institutional requirements or to calculate storage requirements.
+The University of Edinburgh holds your plans on your behalf, but they are your property and responsibility. Any FOI applicants will be referred back to your home institution.
+Your password is stored in encrypted form and cannot be retrieved. If forgotten it has to be reset.
+Please note that DMPonline uses Cookies. Further information about Cookies and how we use them is available on the main DCC website.
+Use of the tool indicates that you understand and agree to these terms and conditions.
If you don't want to accept the invitation, please ignore this email.
+ Your account won't be created until you access the link above and set your password.
If you didn't request this, please ignore this email.
+Your password won't change until you access the link above and create a new one.
" + hello: "Hello" + 1st_part_locked: "Your " + 2nd_part_locked: " account has been locked due to an excessive number of unsuccessful sign in attempts." + click_to_unlock: "Click the link below to unlock your account:" + unlock: 'Unlock my account' + waiting_for_confirmation: "Currently waiting confirmation for: " + resend_unlock: "Resend unlock instructions" + api: + bad_credentials: '{"Error":"Bad credentials"}' + org_dosent_exist: '{"Error":"Organisation does not exist"}' + org_not_funder: '{"Error":"Organisation specified is not a funder"}' + org_multiple_templates: '{"Error":"Organisation has more than one template and template name unspecified or invalid"}' + no_auth_for_endpoint: '{"Error":"You do not have authorisation to view this endpoint"}' + bad_resource: '{"Error":"You do not have authorisation to view this resource"}' + + + diff --git a/config/locales/en.bootstrap.yml b/config/locales/en.bootstrap.yml deleted file mode 100644 index 664de2b..0000000 --- a/config/locales/en.bootstrap.yml +++ /dev/null @@ -1,18 +0,0 @@ -# Sample localization file for English. Add more files in this directory for other locales. -# See https://github.com/svenfuchs/rails-i18n/tree/master/rails%2Flocale for starting points. - -en: - helpers: - actions: "Actions" - links: - back: "Back" - cancel: "Cancel" - confirm: "Are you sure?" - destroy: "Delete" - new: "New" - edit: "Edit" - titles: - edit: "Edit" - save: "Save" - new: "New" - delete: "Delete" diff --git a/config/locales/en.yml b/config/locales/en.yml deleted file mode 100644 index 7465458..0000000 --- a/config/locales/en.yml +++ /dev/null @@ -1,920 +0,0 @@ -# [+Project:+] DMPonline v4 -# [+Description:+] This file contains all the text present on DMPonline that is not being retrieve from the database. -# [+Copyright:+] Digital Curation Centre - -en: - date: - formats: - # Use the strftime parameters for formats. - # When no format has been given, it uses default. - # You can provide other formats here if you like! - default: "%d-%m-%Y" - short: "%d/%m/%Y" - long: "%d %B, %Y" - - day_names: [Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday] - abbr_day_names: [Sun, Mon, Tue, Wed, Thu, Fri, Sat] - - # Don't forget the nil at the beginning; there's no such thing as a 0th month - month_names: [~, January, February, March, April, May, June, July, August, September, October, November, December] - abbr_month_names: [~, Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec] - # Used in date_select and datetime_select. - order: - - day - - month - - year - - time: - formats: - default: "%a, %d %b %Y %H:%M:%S %z" - short: "%d %b %H:%M" - custom: "%d/%m/%Y %H:%M" - long: "%B %d, %Y %H:%M" - am: "am" - pm: "pm" - - tool_title: "DMPonline" - dmponline3_text: "DMPonline previous version" - dcc_name: "Digital Curation Centre" - welcome_title: "Welcome." - welcome_text: "DMPonline has been developed by the Digital Curation Centre to help you write data management plans.
" - screencast_text: "Screencast on how to use DMPonline" - screencast_error_text: "Your browser does not support the video tag." - - admin: - org_title: "Organisation name" - org: "Organisation" - orgs: "Organisations" - org_type: "Organisation type" - org_parent: "Parent organisation" - org_created_message: "Organisation was successfully created." - org_updated_message: "Organisation was successfully updated." - plans: "Plans" - title: "Title" - desc: "Description" - guidance_group: "Guidance group" - no_guidance_group: "No guidance group" - guidance: "Guidance" - name: "Name" - abbrev: "Abbreviation" - question: "Question" - question_format: "Question Format" - questions: "Questions" - template_title: "Template title" - section_title: "Section title" - formatting: "Formatting" - max_pages: "Max Pages" - phase_title: "Phase title" - version_title: "Version title" - user_name: "Username" - firstname: "First name" - surname: "Surname" - user: "User" - user_created: 'User was successfully created.' - user_org_role: "User role on an Organisation" - user_role_type: "User role type" - user_role_type_created: 'User role type was successfully created.' - user_role_type_updated: 'User role type was successfully updated.' - user_role: "User role" - role: "Role" - user_status: "User status" - user_status_created: 'User status was successfully created.' - user_status_updated: 'User status was successfully updated.' - user_type: "User type" - user_type_created: 'User type was successfully created.' - user_type_updated: 'User type was successfully created.' - last_logged_in: "Last logged in" - version_numb: "Version number" - details: "Details" - phases: "Phases" - phase: "Phase" - version: "Version" - versions: "Versions" - sections: "Sections" - section: "Section" - multi_options: "Multiple question options" - templates: "Templates" - template: "Template" - themes: "Themes" - theme: "Theme" - theme_created: 'Theme was successfully created.' - theme_updated: 'Theme was successfully updated.' - sug_answer: "Suggested answer" - sug_answers: "Suggested answers" - old_temp_field: "old template field" - old_theme_field: "old theme field" - token_permission_type: "Token Permission Type" - permission_description: "Permission Description" - token_permission: "Token Permission" - org_token_permission: "Organisation Token Permission" -# choose_api_permissions: "Choose all API Permissions that apply." - - settings_updated: 'Settings updated successfully' - choose_themes: 'Choose all themes that apply.' - all_themes: 'All themes' - selected_themes: "Selected themes" - choose_templates: 'Choose all templates that apply.' - all_templates: 'All templates' - selected_templates: "Selected templates" - select_question_format: "Select question format" - no_template: 'No template' - no_phase: 'No phase' - no_version: 'No version' - no_section: 'No section' - - org_admin: - admin_area: "Admin area" - admin_details: "Admin Details" - template_label: "Templates" - user_list_label: "Users" - org_details_label: "Organisation details" - org_text: "These are the basic details for your organisation." - org_abbr_help_text_html: "This is what displays as a label on your guidance, e.g. 'Glasgow guidance on Metadata'. It's best to use an abbreviation or short name." - users_list: "List of users" - user_full_name: "Name" - user_name: "Email address" - last_logged_in: "Last logged in" - how_many_plans: "How many plans?" - user_text_html: "Below is a list of users registered for your organisation. You can sort the data by each field." - org_name: "Name" - org_abbr: "Abbreviation" - org_desc: "Description" - org_banner_text: "Top banner text" - org_target_url: "Website" - org_type: "Organisation type" - parent_org: "Main organisation" - last_updated: "Last updated" - desc_help_text_html: "You can write pieces of guidance to be displayed by theme (e.g. generic guidance on storage and backup that should present across the board) or you can write guidance for specific questions. Writing generic guidance by theme saves you time and effort as your advice will be automatically displayed across all templates rather than having to write guidance to accompany each.
-You will usually want your guidance to display on all templates, however there may be cases where you only want it to show for specific funders e.g. if you have specific instructions for applicants to BBSRC for example. This can be set too if needed.
" - delete_message_html: "You are about to delete '%{guidance_summary}'. Are you sure?" - guidance_group: - add_guidance_group: "Add guidance group" - guidance_group_list: "Guidance group list" - name_label: "Name" - subset: "Optional subset" - subset_eg: "e.g. School/ Department" - all_temp: "All templates" - help_text_add: "Please enter the group title" - subset_option_help_text: "If the guidance is only meant for a subset of users e.g. those in a specific college or institute, check this box. Users will be able to select to display this subset guidance when answering questions in the 'create plan' wizard." - template_help_text_html: "Select which templates you want the guidance to display on. This will usually be all templates." - title_help_text_html: "Add an appropriate name for your guidance group e.g. Glasgow guidance. This name will be used to tell the end user where the guidance has come from e.g. 'Glasgow Guidance on Metadata'" - guidance_group_text_html: "First create a guidance group. This could be institution wide or a subset e.g. a particular College / School, Institute or department. When you create guidance you'll be asked to assign it to a guidance group.
" - delete_message: "You are about to delete '%{guidance_group_name}'. This will affect guidance. Are you sure?" - created_message: "Guidance group was successfully created." - updated_message: "Guidance group was successfully updated." - destroyed_message: "Guidance group was successfully deleted." - templates: - create_template: "Create a template" - new_label: "New template" - template_details: "Template details" - edit_details: "Edit template details" - view_all_templates: "View all templates" - funders_temp: "Funders templates" - title_help_text: "Please enter a title for your template." - section_title_help_text: "Please enter section title" - help_text_html: "If you wish to add an institutional template for a Data Management Plan, use the 'create template' button. You can create more than one template if desired e.g. one for researchers and one for PhD students.
-Your template will be presented to users within your institution when no funder templates apply. If you want to add questions to funder templates use the 'customise template' options below.
" - create_new_template_text_html: "To create a new template, first enter a title and description. Once you have saved this you will be presented with options to add one or more phases.
" - desc_help_text_html: "Enter a description that helps you to differentiate between templates e.g. if you have ones for different audiences" - own_temp: "Own templates" - add_phase_label: "Add new phase +" - view_phase_label: "View phase" - edit_phase_label: "Edit phase" - back_to_edit_phase_label: "Back to edit view" - edit_phase_details_label: "Edit phase details" - phase_details_label: "Phase details" - phase_order_label: "Order of display" - phase_details_text_html: "Here you set the title that users will see. If you intend to have multiple phases for you DMP, this should be clear in the title and description.
" - phase_title_help_text: "Enter a title for the phase e.g. intial DMP, full DMP... This is what users will see in the tabs when completing a plan. If you only have one phase, call it something generic e.g. Glasgow DMP" - phase_number_help_text: "This allows you to order the phases of your template." - phase_desc_help_text_html: "Enter a basic description. This will be presented to users on the 'Admin Plan' tab, above the summary of the sections and questions which they will be asked to answer." - phase_delete_message: "You are about to delete '%{phase_title}'. This will affect versions, sections and questions linked to this phase. Are you sure?" - phase_new_text_html: "When you create a new phase for your template, a version will automatically be created. Once you complete the form below you will be provided with options to create sections and questions." - versions_label: "Versions" - version_details_label: "Version details" - add_section: "Add section" - new_section: "New section title" - section_title_placeholder: "New section title" - section_desc_help_text_html: "Select themes that are relevant to this question.
-This allows your generic institution-level guidance to be drawn in, as well as that from other sources e.g. the DCC or any Schools/Departments that you provide guidance for.
-You can select multiple themes by using the CTRL button.
" - default_answer_label: "Default answer" - guidance_label: "Guidance" - question_guidance_help_text_html: "Enter specific guidance to accompany this question. If you have guidance by themes too, this will be pulled in based on your selections below so it's best not to duplicate too much text." - delete_message: "You are about to delete '%{question_text}'. Are you sure?" - question_options_help_text_html: "Enter any options that you wish to display. If you want to pre-set one option as selected, check the default box." - - - - - - helpers: - home: "Home" - return_home: "Return to the home page" - admin_area: "Super admin area" - edit_profile: "Edit profile" - view_plans_label: "View plans" - create_plan_label: "Create plan" - about_us_label: "About" - roadmap_label: "Future plans" - help_label: "Help" - contact_label: "Contact" - jisc: "The DCC is funded by" - format: "format" - - sign_in: "Sign in" - sign_out: "Sign out" - sign_up: "Sign up" - sign_up_text: "New to DMPonline? Sign up today." - signed_in: "Signed in as " - institution_sign_in_link: "Or, sign in with your institutional credentials" - institution_sign_in: " (UK users only)" - - user_name: "Email address" - email: "Email" - valid_email: "You must enter a valid email address." - user_details_text_html: "Please note that your email address is used as your username. If you change this, remember to use your new email address on sign in.
" - user_details_paragraph_html: "You can edit any of the details below." - remember_me: "Remember me" - org_not_listed: "My organisation isn't listed." - - password: "Password" - current_password: "Current password" - new_password: "New password" - password_conf: "Password confirmation" - change_password: "Change your password" - forgot_password: "Forgot your password?" - password_too_small: "Your password must contain at least 8 characters." - password_no_match: "This must match what you entered in the previous field." - no_pass_instructions: "Didn't receive confirmation instructions?" - no_unlock_instructions: "Didn't receive unlock instructions?" - send_password_info: "Reset password instructions" - edit_password_info: "If you would like to change your password please complete the following fields." - accept_terms_html: " I accept the terms and conditions *" - you_must_accept: 'You must accept the terms and conditions to register.' - email_already_registered: 'That email address is already registered.' - email_must_valid_confirmation_message: "This must be a valid email address - a message will be sent to it for confirmation." - error_registration_check: 'Error processing registration. Please check that you have entered a valid email address and that your chosen password is at least 8 characters long.' - api_token: 'API token' - api_info: 'API Information' - api_use: 'How to use the API' - api_granted: 'You have been granted permission by your organisation to use our API.' - api_view_token: 'Your API token and instructions for using the API endpoints can be found here.' - api_mail_subject: 'API Permission Granted' - - - text_area: "Text area" - text_field: "Text field" - radio_buttons: "Radio buttons" - checkbox: "Check box" - dropdown: "Dropdown" - multi_select_box: "Multi select box" - export: "Export" - - about: - by: "By " - on: " on " - read_more: "Read more on the " - - mailer: - permission_relating: "Your permissions relating to " - changed: " have changed. You now have " - access: "access." - access_to: "Your access to " - removed: " has been removed." - given: "You have been given " - access_two: " access to " - - truncate_continued: "... (continued)" - security_check: "Security check" - error: "Error!" - comment: "Comment" - send: "Send" - yes_label: "Yes" - no_label: "No" - ok_label: "Ok" - none: "None" - false_lowercase: "false" - title: "Title" - note: "Note" - me: "Me" - view: "View" - desc: "Description" - save: "Save" - preview: "Preview" - saving: "Saving..." - loading: "Loading..." - removing: "Removing..." - unsaved: "Unsaved changes" - unlink_account: "Unlink account" - submit: - edit: "Edit" - create: "Create" - update: "Update" - cancel: "Cancel" - save: "Save" - delete: "Delete" - back: "Back" - discard: "Discard" - - before_submitting_consider: "Before submitting, please consider:" - name: "Name" - first_name: "First name" - last_name: "Last name" - first_name_help_text: "Please enter your first name." - surname_help_text: "Please enter your surname or family name." - owner: "Owner" - orcid_id: "ORCID number" - orcid_html: "ORCID number is a persistent digital identifier that distinguishes each researcher, more info." - sign_up_shibboleth_alert_text_html: "DMPonline doesn't recognise your institutional credentials - either you haven't created an account with us or you haven't linked these details to your existing account. - --> If you do not have an account with DMPonline, please complete the form below. - --> If you have an account with DMPonline, please Sign in so we can link your account to your institutional credentials. - Once you have created and/or linked your account, you'll be able to sign in with your institutional credentials directly." - shibboleth_linked_text: "Your account is linked to your institutional credentials." - shibboleth_to_link_text: "Link your DMPonline account to your institutional credentials (UK users only)" - shibboleth_unlink_label: "Unlink your institutional credentials" - shibboleth_unlink_alert: "Unlink institutional credentials alert" - shibboleth_unlink_dialog_text: "You are about to unlink DMPonline of your institutional credentials, would you like to continue?
" - - - section_label: "Section" - sections_label: "Sections" - questions_label: "Questions" - answers_label: "Answers" - answer_questions: "Answer questions" - last_edit: "Last edited" - select_action: "Select an action" - answered_by: "Answered " - answered_by_part2: " by " - suggested_answer: "Suggested answer" - suggested_example: "Example answer" - notanswered: "Not answered yet" - noquestionanswered: "No questions have been answered" - guidance: "Guidance" - policy_expectations: "Policy Expectations" - export: "Export" - guidance_accordion_label: "Guidance" - add_comment_accordion_label: "Share note" - comment_accordion_label: "Notes" - - comments: - add_comment_label: "Add note" - add_comment_text: "Share note with collaborators" - comment_label: "Note" - comments_label: "Notes" - view_label: "View" - edit_label: "Edit" - retract_label: "Remove" - clear_label: "Remove" - commented_by: "Noted by:" - archive_own_comment_question: "Are you sure you would like to remove this note?" - archive_own_comment_button_label: "Remove" - archive_comment_question: "Are you sure you would like to remove this note?" - archive_comment_button_label: "Remove" - clear_by: "Note removed by" - retracted: "Note removed by you" - comment_created: 'Comment was successfully created.' - comment_updated: 'Comment was successfully updated.' - comment_removed: 'Comment has been removed.' - - - org_type: - funder: "Funder" - institution: "Institution" - project: "Project" - organisation: "Organisation" - org_name: "Organisation name" - school: "School" - publisher: "Publisher" - other_guidance: "Other guidance" - template: "Template" - templates: "Templates" - child: "Unit" - other_org_help_text: "Please enter the name of your organisation." - - - project: - create: "Create plan" - edit: "Edit plan details" - grant_title: "Grant number" - grant_help_text: "Grant reference number if applicable [POST-AWARD DMPs ONLY]" - not_applicable: "Not applicable/not listed." - multi_templates: "There are a number of possible templates you could use. Please choose one." - project_name: "Plan name" - my_project_name: "My plan" - success: "Plan was successfully created." - success_update: "Plan was successfully updated." - principal_investigator: "Principal Investigator/Researcher" - principal_investigator_help_text: "Name of Principal Investigator(s) or main researcher(s) on the project." - principal_investigator_id: "Principal Investigator/Researcher ID" - principal_investigator_id_help_text: "E.g ORCID http://orcid.org/." - funder_help_text: "Research funder if relevant" - funder_name: "Funder name" - project_question_desc_label: "Summary about the questions" - tab_plan: "Plan details" - tab_export: "Export" - export_text_html: "From here you can download your plan in various formats. This may be useful if you need to submit your plan as part of a grant application. -Select what format you wish to use and click to 'Export'.
" - questions_answered: "questions answered" - not_saved_answers_text_alert: "You have altered answers but have not saved them:" - not_saved_answers_confirmation_alert: "Would you like to save them now?" - not_saved_answers_header: "Unsaved answers" - answer_recorded: 'Answer was successfully recorded.' - answer_error: 'There was an error saving the answer.' - answer_no_change: 'No change in answer content - not saved.' - project_data_contact: "Plan data contact" - project_data_contact_help_text: "Name (if different to above), telephone and email contact details" - project_name_help_text: "If applying for funding, state the name exactly as in the grant proposal." - project_desc_help_text_html: "Briefly summarise the type of study (or studies) to help others understand the purposes for which the data are being collected or created.
Welcome. You are now ready to create your first DMP.Click the 'Create plan' button below to begin.
" - project_text_when_project: "The table below lists the plans that you have created, and any that have been shared with you by others.These can be edited, shared, exported or deleted at anytime.
" - project_details_text_html: "This page gives you an overview of your plan. It tells what your plan is based on and gives an overview of the questions that you will be asked." - project_details_editing_text_html: "Please fill in the basic project details below and click 'Update' to save" - confirm_delete_text: "Are you sure you wish to delete this plan? If the plan is being shared with other users, by deleting it from your list, the plan will be deleted from their plan list as well" - confirmation_text: "Confirm plan details" - confirmation_text_desc: "Where your funder or institution doesn't have specific requirements (or if you left these options blank), you will see the DCC Checklist. This offers a generic set of DMP questions and guidance. For more details see: DMP checklist 2013." - confirmation_button_text: "Yes, create plan" - default_confirmation_text_desc: "You have selected the Default DMP, which is based on the DCC Checklist. This offers a generic set of DMP questions and guidance. For more details see: DMP checklist 2013." - default_confirmation_button_text: "Create plan" - alert_default_template_text_html: "Please note: %{org_name} provides a DMP template. If you wish to use it select 'Cancel', otherwise select 'Create plan'" - share: - tab_share: "Share" - shared_label: "Shared?" - share_text_html: "You can give other people access to your plan here. There are three permission levels.
Add each collaborator in turn by entering their email address below, choosing a permission level and clicking \"Add collaborator\".
Those you invite will receive an email notification that they have access to this plan, inviting them to register with DMPonline if they don't already have an account. A notification is also issued when a user's permission level is changed.
" - collaborators: "Collaborators" - add_collaborator: "Add collaborator" - add: "Add" - permissions: "Permissions" - permissions_desc: "Editors can contribute to plans. Co-owners have additional rights to edit plan details and control access." - remove: "Remove user access" - confirmation_question: "Are you sure?" - owner: "Owner" - co_owner: "Co-owner" - edit: "Edit" - read_only: "Read only" - locked_section_text: "This section is locked for editing by " - create_page: - title: "Create a new plan" - desc_html: "Please select from the following drop-downs so we can determine what questions and guidance should be displayed in your plan.
-If you aren't responding to specific requirements from a funder or an institution, select here to write a generic DMP based on the most common themes.
" - default_template: "Default DMP" - funders_question: "If applying for funding, select your research funder." - funders_question_description: "Otherwise leave blank." - other_funder_name_label: "Name of funder, if applicable." - institution_question: "To see institutional questions and/or guidance, select your organisation." - institution_question_description: "You may leave blank or select a different organisation to your own." - other_guidance_question: "Tick to select any other sources of guidance you wish to see." - configure: "Configure" - columns: - name: "Name" - owner: "Owner" - shared: "Shared?" - template_owner: "Template Owner" - last_edited: "Last edited" - identifier: "Identifier" - grant_number: "Grant number" - principal_investigator: "Principal Investigator / Researcher" - data_contact: "Plan data contact" - description: "Description" - filter: - placeholder: "Filter plans" - submit: "Filter" - cancel: "Cancel" - no_plans_match: "No plans match '%{filter}'" - no_matches: "No matches" - user_added: "User added to project" - invitation_success: 'Invitation issued successfully.' - enter_email: "Please enter an email address" - sharing_updated: 'Sharing details successfully updated.' - access_removed: 'Access removed' - update_success: 'Project was successfully updated.' - create_success: 'Project was successfully created.' - details_update_success: "Details successfully updated." - choose_template: "Choose a template" - - plan: - export: - pdf: - question_not_answered: Question not answered. - generated_by: This document was generated by DMPonline (http://dmponline.dcc.ac.uk) - space_used: "approx. %{space_used}% of available space used (max %{num_pages} pages)" - space_used_without_max: "approx. %{space_used}% of available space used" - project_name: "Project Name" - project_identifier: "Project Identifier" - grant_title: "Grant Title" - principal_investigator: "Principal Investigator / Researcher" - project_data_contact: "Project Data Contact" - project_description: "Description" - funder: "Funder" - institution: "Institution" - not_valid_format: '%{value}% is not a valid format' - - settings: - title: "Settings" - projects: - title: "Settings - My plans" - desc: "The table below lists the available columns that can be shown on the 'My plans' list. Choose which you would like to appear." - errors: - no_name: "'name' must be included in column list." - duplicate: "Duplicate column name. Please only include each column once." - unknown: "Unknown column name." - plans: - title: "Plan title" - reset: "Reset" - custom_formatting: "(Using custom PDF formatting values)" - template_formatting: "(Using template PDF formatting values)" - default_formatting: "(Using default PDF formatting values)" - included_elements: "Included Elements" - pdf_formatting: "PDF Formatting" - font_face: "Face" - font_size: "Size" - font: "Font" - margin: "Margin" - margins: - top: "Top" - bottom: "Bottom" - left: "Left" - right: "Right" - max_pages: "Maximum number of pages" - errors: - missing_key: "A required setting has not been provided" - invalid_margin: "Margin value is invalid" - negative_margin: "Margin cannot be negative" - unknown_margin: "Unknown margin. Can only be 'top', 'bottom', 'left' or 'right'" - invalid_font_size: "Invalid font size" - invalid_font_face: "Invalid font face" - unknown_key: "Unknown formatting setting" - invalid_max_pages: "Invalid maximum pages" - no_access_account: "This account does not have access to that plan." - - about_page: - title: "About DMPonline" - tab_1: "Background" - tab_2: "Latest news" - - body_text_tab_1_html: "Funding bodies increasingly require their grant-holders to produce Data Management Plans(DMP), both during the bid-preparation stage and after funding has been secured. DMPonline has been produced by the UK's Digital Curation Centre to help research teams respond to this requirement, and any expectations that their institution or others may apply.
-The DCC has worked closely with research funders and universities to produce a tool that assists researchers to produce an effective data management plan (DMP) to cater for the whole lifecycle of a project, from bid-preparation stage through to completion.
- -There are a number of templates within the tool that represent the requirements of different funders and institutions. Users are asked three questions at the outset so we can determine the appropriate template to display (e.g. the ESRC template when applying for an ESRC grant). Guidance is provided to help you interpret and answer the questions. This guidance is provided by researcher funders, universities and disciplines.
- -If you have an account please sign in and start creating or editing your DMP.
-If you do not have a DMPonline account, click on 'Sign up' on the homepage.
-Please visit the 'Help' page for guidance.
- -We are constantly improving the user interface and functionality of DMPonline. - If you would like to contribute with feedback and suggestions, please contact us by emailing - dmponline@dcc.ac.uk. You can also report bugs and request new features directly on GitHub
-If you need to access plans from the earlier version of the tool please visit DMPonline v3.
" - - body_text_tab_2_html: "DMPonline stories from the DCC website
" - - help_page: - title: "Help" - tab_1: "On DMPonline" - tab_2: "On data management planning" - body_text_tab_2_html: "When you login to DMPonline you will be directed to the 'My plans' page. From here you can edit, share, export or delete any of your plans. You will also see plans that have been shared with you by others.
-To create a plan, click the 'Create plan' button from the 'My plans' page or the top menu. Select options from the drop-down menus and tickboxes to determine what questions and guidance you should be presented with. Confirm your selection by clicking 'Yes, create plan'
-The tabbed interface allows you to navigate through different functions when editing your plan.
-When viewing any of the question tabs, you will see the different sections of your plan displayed. Click into these in turn to answer the questions. You can format your responses using the text editing buttons.
-Guidance is displayed in the right-hand panel. Click the '+' symbol to view this.
-Remember to 'save' your responses before moving on.
-Insert the email address of any collaborators you would like to invite to read or edit your plan. Set the level of permissions you would like to grant them via the drop-down options and click to 'Add collaborator'
-From here you can download your plan in various formats. This may be useful if you need to submit your plan as part of a grant application. Choose what format you would like to view/download your plan in and click to export. When you login to DMPonline you will be directed to the 'My plans' page. From here you can edit, share, export or delete any of your plans. You will also see plans that have been shared with you by others.
-If you need to access plans from the earlier version of the tool please visit DMPonline v3.
" - - contact_page: - title: "Contact us" - intro_text_html: "DMPonline is provided by the Digital Curation Centre. You can find out more about us on our website. If you would like to contact us about DMPonline, please enter your query in the form below or email dmponline@dcc.ac.uk.
" - github_text_html: "If you have a feature request or think you have found a bug, please check out the list of issues on GitHub. If your issue isn't listed there, please add it; if it is, please add a comment if you have more information or just to let us know how important it is to you. This will help us to help us prioritise future developments.
" - address_text_html: "Tel. +44 (0) 131 651 1239
-Email dmponline@dcc.ac.uk
" - - roadmap_page: - title: "Future plans" - tab_1: "Releases" - tab_2: "Get involved" - body_text_tab_1_html: "The DCC is collaborating with the DMPTool team to develop a joint codebase for Data Management Planning called DMP Roadmap. Both of our tools will be delivered using this in the future. We've agreed what features need to be included and are planning a few sprints to deliver these. The initial release will include all of the main priorities we already had flagged, including:
-DMPonline has an active and growing user base, and we are grateful to the members who suggest ideas for new and improved features. If you would like to help shape our future plans, please join the user group. More information on how you can engage with us is available under the 'Get involved' tab.
- -The current version of DMPonline is 4.2. This was released in August 2015 and included Institutional branding, optional guidance for funders, improvements to the question area, improvements to the admin interface, GitHub pull requests, new seed file, and an update of the gemfile.
- -The code is available on GitHub
- -The previous version of DMPonline is 4.1. This was released in May 2015 and included a comment feature, improved guidance on signing in with institutional credentials, enhanced deployment guidance and proposed methods for internationalisation. Full details can be found in the release note and associated documents.
-DMPonline is developed and maintained by the UK Digital Curation Centre. We’re a small team, and are happy to collaborate with others. There are various ways you can get involved:
-We run a listserv for the DMPonline user group that you can request to join. We also host periodic meetings to consult on our plans. Being part of the user group gives you the opportunity to be informed about future developments and to provide feedback to help shape our plans.
-Our user group sessions are usually focused around a certain topic (e.g. fleshing out use cases for an API) so invites are sent based on your areas of expertise. It is helpful for us to know your role and interests to invite relevant people to each session. Please introduce yourself on the list and share your ideas.
-Notes from previous user group sessions are provided below:
-Please let us know your interests and share your ideas for future developments via the mailing list so the community as a whole can feedback on them.
- -DMPonline can be customised by institutions and disciplines. You can add templates for users in your organisation and tailored guidance that explains local support and services. Example answers can also be offered to help users understand what to write in a Data Management Plan. To do this you’ll need to request admin access, so please email us on dmponline@dcc.ac.uk.
-Futher guidance on customising DMPonline is available on the DCC website.
- -DMPonline is a Ruby on Rails application. The source code is made available under a GNU Affero General Public License. This permits others to reuse the code freely, but obligates you to share the source code for any extensions in the same way. Please inform us if you install an instance of DMPonline and offer your contributions back to the community.
-If you install an instance of DMPonline we require that you credit the DCC as originators of the tool. We recommend that the acknowledgement takes the form of the DMPonline logo with a link back to the DCC-hosted version of the tool.
-We are willing to work with external developers to add new features to the tool. We are also open to delivering new features on a chargeable basis. If there are extensions you would like to see prioritised and have resource to support additional developer effort, please contact us on dmponline@dcc.ac.uk to negotiate terms.
- -We are impressed by the uptake of DMPonline both in the UK and internationally and are really keen to hear how you are using the tool and promoting it in your context. We are aware that others have run training courses, developed guidance materials and advocated use of the tool. Please notify us of this as it helps to show impact.
-We are currently investigating options for revenue generation. This will help us serve the increased demand more effectively and safeguard the long-term sustainability of DMPonline. Plans will be released for consultation soon but we also welcome your suggestions on how best to support our work.
" - - terms_page: - title: "Terms of use" - body_text_html: "The Digital Curation Centre ('DCC') is a consortium supported by Jisc and based at the Universities of Edinburgh, Glasgow and Bath. Our primary constituency is the UK research community, particularly the higher and further education sector.
-DMPonline ('the tool', 'the system') is a tool developed by the DCC as a shared resource for the research community. It is hosted at the University of Edinburgh.
-In order to help identify and administer your account with DMPonline, we need to store your email address. We may also use it to contact you to obtain feedback on your use of the tool, or to inform you of the latest developments or releases. The information may be transferred between the DCC partner institutions but only for legitimate DCC purposes. We will not sell, rent or trade any personal information you provide to us.
-The information you enter into this system can be seen by you, people you have chosen to share access with, and - solely for the purposes of maintaining the service - system administrators at the University of Edinburgh. We compile anonymised, automated and aggregated information from plans, but we will not directly access, make use of, or share your content with anyone else without your permission. Authorised officers of your home institution may access your plans for specific purposes - for example, to track compliance with funder/institutional requirements or to calculate storage requirements.
-The University of Edinburgh holds your plans on your behalf, but they are your property and responsibility. Any FOI applicants will be referred back to your home institution.
-Your password is stored in encrypted form and cannot be retrieved. If forgotten it has to be reset.
-Please note that DMPonline uses Cookies. Further information about Cookies and how we use them is available on the main DCC website.
-Use of the tool indicates that you understand and agree to these terms and conditions.
If you don't want to accept the invitation, please ignore this email.
- Your account won't be created until you access the link above and set your password.
If you didn't request this, please ignore this email.
-Your password won't change until you access the link above and create a new one.
" - hello: "Hello" - 1st_part_locked: "Your " - 2nd_part_locked: " account has been locked due to an excessive number of unsuccessful sign in attempts." - click_to_unlock: "Click the link below to unlock your account:" - unlock: 'Unlock my account' - waiting_for_confirmation: "Currently waiting confirmation for: " - resend_unlock: "Resend unlock instructions" - api: - bad_credentials: '{"Error":"Bad credentials"}' - org_dosent_exist: '{"Error":"Organisation does not exist"}' - org_not_funder: '{"Error":"Organisation specified is not a funder"}' - org_multiple_templates: '{"Error":"Organisation has more than one template and template name unspecified or invalid"}' - no_auth_for_endpoint: '{"Error":"You do not have authorisation to view this endpoint"}' - bad_resource: '{"Error":"You do not have authorisation to view this resource"}' - - - diff --git a/config/locales/fr.bootstrap.yml b/config/locales/fr.bootstrap.yml new file mode 100644 index 0000000..2e52bb1 --- /dev/null +++ b/config/locales/fr.bootstrap.yml @@ -0,0 +1,17 @@ + +fr: + helpers: + actions: "Actions" + links: + back: "Retour" + cancel: "Annuler" + confirm: "Êtes-vous sûr?" + destroy: "Supprimer" + new: "Nouveau" + edit: "Modifier" + titles: + edit: "Modifier" + save: "Enregistrer" + new: "Nouveau" + delete: "Supprimer" + diff --git a/config/locales/fr.yml b/config/locales/fr.yml new file mode 100644 index 0000000..e8a1178 --- /dev/null +++ b/config/locales/fr.yml @@ -0,0 +1,787 @@ +fr: + date: + formats: + # Use the strftime parameters for formats. + # When no format has been given, it uses default. + # You can provide other formats here if you like! + default: "%d-%m-%Y" + short: "%d/%m/%Y" + custom: "%d/%m/%Y %H:%M" + long: "%d %B, %Y" + + day_names: [Dimanche, Lundi, Mardi, Mercredi, Jeudi, Vendredi, Samedi] + abbr_day_names: [Dim, Lun, Mar, Mer, Jeu, Ven, Sam] + + # Don't forget the nil at the beginning; there's no such thing as a 0th month + month_names: [~, Janvier, Février, Mars, Avril, Mai, Juin, Juillet, Août, Septembre, Octobre, Novembre, Décembre] + abbr_month_names: [~, Janv., Févr., Mars, Avr., Mai, Juin, Juill., Août, Sept., Oct., Nov., Déc.] + # Used in date_select and datetime_select. + order: + - day + - month + - year + + time: + formats: + default: "%a, %d %b %Y %H:%M:%S %z" + short: "%d %b %H:%M" + long: "%B %d, %Y %H:%M" + custom: "%d/%m/%Y %H:%M" + am: "a.m." + pm: "p.m." + + tool_title: "Assistant PGD – Réseau Portage" + dmponline3_text: "Version antérieure de l'Assistant PGD" + subhead: "Services partagés pour les données de recherche" + dcc_name: "Digital Curation Centre" + welcome_title: "Bienvenue" + welcome_text: "L'Assistant PGD est un outil bilingue d'aide à la préparation d'un plan de gestion des données (PGD). Cet outil, qui s'appuie sur des normes internationales et sur les meilleures pratiques en matière de gestion des données, guide le chercheur pas à pas à travers les questions clés pour développer son plan.
" +# welcome_links: "En savoir plus sur les plans de gestion des données
Vous souhaitez partager vos données de recherche?
Pour en savoir plus sur les services de données de recherche du service des bibliothèques
Vous pouvez rédiger des directives à afficher par thème (p. ex. des directives générales sur l'entreposage et la sauvegarde qui devraient être présentées à tous les échelons) ou vous pouvez rédiger des directives pour des questions précises. La rédaction de directives générales par thème vous permet d'économiser du temps et des efforts, car vos conseils seront automatiquement affichés dans tous les modèles au lieu d'avoir à rédiger des directives qui accompagneraient chaque modèle.
+De manière générale, vous voudrez que vos directives soient affichées dans tous les modèles. Vous voudrez toutefois, dans certains cas, que les directives soient seulement affichées pour des bailleurs de fonds précis, par exemple, si vous avez des consignes précises pour les candidats qui présentent une demande au Biotechnology and Biological Sciences Research Council (BBSRC). Vous pouvez également le préciser, au besoin.
" + delete_message_html: "Vous êtes sur le point de supprimer '%{guidance_summary}'. Êtes-vous sûr de vouloir le supprimer?" + guidance_group: + add_guidance_group: "Ajouter un groupe de directives" + guidance_group_list: "Liste des groupes de directives" + name_label: "Nom" + published: "Publié(e)" + subset: "Sous-ensemble facultatif" + subset_eg: "p. ex. école/département" + all_temp: "Tous les modèles" + help_text_add: "Veuillez indiquer le titre du groupe." + subset_option_help_text: "Si les directives s'adressent uniquement à un sous-ensemble d'utilisateurs, par exemple ceux d'un collège ou d'un institut précis, cochez cette case. Les utilisateurs pourront choisir d'afficher les directives destinées à ce sous-ensemble en répondant aux questions dans l'assistant « créer un plan »." + template_help_text_html: "Sélectionnez les modèles pour lesquels vous voulez que les directives soient affichées. Ce sera généralement pour tous les modèles." + title_help_text_html: "Donnez un nom approprié à votre groupe de directives, p. ex. directives de Glasgow. Ce nom sera utilisé pour indiquer à l'utilisateur final la provenance des directives, par exemple « Les directives sur les métadonnées de Glasgow »." + guidance_group_text_html: "Vous devez d'abord créer un groupe de directives. Ces directives peuvent s'adresser à l'ensemble d'un établissement ou à un sous-ensemble, par exemple un collège ou une école, un institut ou un département précis. Lorsque vous créez des directives, on vous demandera de les assigner à un groupe de directives.
" + delete_message: "Vous êtes sur le point de supprimer '%{guidance_group_name}', ce qui modifiera les directives. Êtes-vous sûr de vouloir le supprimer?" + created_message: "Le groupe de directives a été créé avec succès." + updated_message: "Le groupe de directives a bien été mis à jour." + destroyed_message: "Le groupe de directives a bien été supprimé." + templates: + create_template: "Créer un modèle" + new_label: "Nouveau modèle" + template_details: "Renseignements sur le modèle" + edit_details: "Modifier les renseignements sur le modèle" + view_all_templates: "Voir tous les modèles" + funders_temp: "Modèles des bailleurs de fonds" + title_help_text: "Veuillez indiquer un titre pour votre modèle." + section_title_help_text: "Veuillez indiquer le titre de la section." + help_text_html: "Si vous souhaitez ajouter un modèle institutionnel pour un plan de gestion des données, utilisez le bouton « créer un modèle ». Vous pouvez créer plus d'un modèle, au besoin, par exemple un modèle pour les chercheurs et un modèle pour les étudiants au doctorat.
+Votre modèle sera présenté aux utilisateurs de votre établissement lorsqu'aucun modèle de bailleur de fonds ne s'applique. Si vous souhaitez ajouter des questions aux modèles de bailleur de fonds, utilisez les options « personnaliser le modèle » ci-dessous.
" + create_new_template_text_html: "Pour créer un nouveau modèle, vous devez d'abord indiquer un titre et une description. Une fois que vous les avez enregistrés, des options vous seront présentées pour ajouter une ou plusieurs phases.
" + desc_help_text_html: "Entrez une description qui vous aide à faire la différence entre les autres modèles, par exemple si vous en avez pour différents publics." + own_temp: "Vos modèles" + add_phase_label: "Ajouter une nouvelle phase +" + view_phase_label: "Voir la phase" + edit_phase_label: "Modifier la phase" + back_to_edit_phase_label: "Retour au mode de modification" + edit_phase_details_label: "Modifier les renseignements sur la phase" + phase_details_label: "Renseignements sur la phase" + phase_order_label: "Ordre d'affichage" + phase_details_text_html: "Vous indiquez ici le titre que les utilisateurs verront. Si vous prévoyez que votre plan de gestion des données comptera plusieurs phases, vous devez l'indiquer clairement dans le titre et la description.
" + phase_title_help_text: "Indiquez un titre pour la phase, par exemple plan de gestion des données initial, plan de gestion des données complet… Il s'agit du titre que les utilisateurs verront dans les onglets lorsqu'ils établiront un plan. Si votre plan compte une seule phase, choisissez un nom général, par exemple plan de gestion des données de Glasgow." + phase_number_help_text: "Cela vous permet de mettre les phases de votre modèle en ordre." + phase_desc_help_text_html: "Indiquez une description de base qui sera présentée aux utilisateurs et qui sera affichée au-dessus du résumé des sections et des questions auxquelles ils devront répondre." + phase_delete_message: "Vous êtes sur le point de supprimer '%{phase_title}', ce qui modifiera les versions, les sections et les questions en lien avec cette phase. Êtes-vous sûr de vouloir le supprimer?" + phase_new_text_html: "Lorsque vous créez une nouvelle phase pour votre modèle, une version sera automatiquement créée. Une fois que vous avez rempli le formulaire ci-dessous, des options vous seront présentées pour créer des sections et des questions." + versions_label: "Versions" + version_details_label: "Renseignements sur la version" + add_section: "Ajouter une section" + new_section: "Titre de la nouvelle section" + section_title_placeholder: "Titre de la nouvelle section" + section_desc_help_text_html: "Sélectionnez les thèmes applicables à cette question.
+Cela permet ainsi d'intégrer vos directives générales destinées à l'établissement ainsi que celles provenant d'autres sources, par exemple de DCC ou de tous les départements ou les écoles pour lesquels vous fournissez des directives.
+Vous pouvez sélectionner plusieurs thèmes à l'aide de la touche CTRL.
" + default_answer_label: "Réponse par défaut" + guidance_label: "Directives" + question_guidance_help_text_html: "Indiquez des directives précises pour accompagner cette question. Si vous possédez également des directives par thème, elles seront ajoutées en fonction de vos choix ci-dessous, il vaut mieux donc ne pas reproduire en double une trop grande quantité de texte." + delete_message: "Vous êtes sur le point de supprimer '%{question_text}'. Êtes-vous sûr de vouloir le supprimer?" + question_options_help_text_html: "Indiquez toute option que vous souhaitez afficher. Si vous désirez qu'une option soit sélectionnée au préalable, cochez la case par défaut." + + + + + helpers: + home: "Accueil" + return_home: "Revenir à la page d'accueil" + admin_area: "Section du super administrateur" + edit_profile: "Modifier le profil" + view_plans_label: "Mes plans" + create_plan_label: "Créer un plan" + about_us_label: "À propos" + news_label: "Nouvelles" + help_label: "Aide" + contact_label: "Contact" + jisc: "Le DCC est financé par" + + greeting: "Bonjour" + sign_in: "Se connecter" + sign_in_text: "Si vous avez déjà un compte avec l'Assistant PGD ou avec une version antérieure de l'Assistant PGD." + sign_out: "Se déconnecter" + sign_up: "S'inscrire" + sign_up_text: "Nouvel utilisateur de l'Assistant PGD? Inscrivez-vous aujourd'hui." + signed_in: "Connecté en tant que " + institution_sign_in_link: "Ou encore, connectez-vous avec l'authentifiant de votre établissement" + institution_sign_in: "Authentification à l'aide du compte institutionnel bientôt disponible!" + + + user_name: "Adresse électronique" + email: "Courriel" + org_not_listed: "Mon organisme n'est pas inscrit sur la liste." + email_tip: "Ceci doit être une adresse courriel valide - un message y sera envoyé pour le confirmer." + organisation_name_tip: "Veuillez saisir le nom de votre organisme." + password_tip: "Le mot de passe doit comprendre au moins huit caractères." + password_reentry_tip: "Celui-ci doit concorder avec ce que vous avez indiqué dans le champ précédent." + valid_email: "Vous devez entrer une adresse électronique valide." + user_details_text_html: "Veuillez noter que votre adresse électronique sert de nom d'utilisateur. Si vous la modifiez, n'oubliez pas d'utiliser votre nouvelle adresse électronique pour vous connecter.
" + user_details_paragraph_html: "Vous pouvez modifier les renseignements ci-dessous." + remember_me: "Se souvenir de moi" + org_not_listed: "Mon organisme n'est pas inscrit sur la liste." + + password: "Mot de passe" + current_password: "Mot de passe actuel" + new_password: "Nouveau mot de passe" + password_conf: "Confirmation du mot de passe" + change_password: "Modifier votre mot de passe" + forgot_password: "Vous avez oublié votre mot de passe?" + password_too_small: "Votre mot de passe doit comprendre au moins huit caractères." + password_no_match: "La saisie doit correspondre à ce que vous avez indiqué dans le champ précédent." + no_pass_instructions: "Vous n'avez pas reçu les directives de confirmation?" + no_unlock_instructions: "Vous n'avez pas reçu les directives de déverrouillage?" + send_password_info: "Directives pour réinitialiser le mot de passe" + edit_password_info: "Si vous souhaitez modifier votre mot de passe, veuillez remplir les champs suivants." + accept_terms_html: "J'accepte les conditions *" + + text_area: "Zone de texte" + text_field: "Case de saisie simple" + radio_buttons: "Boutons d'option" + checkbox: "Case à cocher" + dropdown: "Liste déroulante" + multi_select_box: "Case à options multiples" + + error: "Erreur!" + comment: "Commentaire" + send: "Envoyer" + yes_text: "Oui" + no_text: "Non" + with: "avec" + singular_people: "personne" + plural_people: "personnes" + none: "Aucun" + title: "Titre" + note: "Remarque" + me: "Moi" + view: "Voir" + desc: "Description" + save: "Enregistrer" + preview: "Aperçu" + saving: "Enregistrement..." + loading: "Téléchargement..." + removing: "Suppression..." + unsaved: "Modifications non enregistrées" + unlink_account: "Dissocier le compte" + submit: + edit: "Modifier" + create: "Créer" + update: "Mettre à jour" + cancel: "Annuler" + save: "Enregistrer" + delete: "Supprimer" + back: "Retour" + discard: "Rejeter" + + name: "Nom" + first_name: "Prénom" + last_name: "Nom" + first_name_help_text: "Veuillez indiquer votre prénom." + surname_help_text: "Veuillez indiquer votre nom ou nom de famille." + owner: "Propriétaire" + orcid_id: "Numéro ORCID" + orcid_html: "Le numéro ORCID est un identifiant numérique constant qui différencie chaque chercheur, pour de plus amples renseignements." + sign_up_shibboleth_alert_text_html: "Remarque : Si vous avez déjà créé un compte de l'Assistant PGD et que vous désirez associer le compte à votre authentifiant de l'établissement, vous devez d'abord vous connecter à un compte existant de l'Assistant PGD. Si vous n'avez jamais créé de compte dans l'Assistant PDG, veuillez remplir le formulaire ci-dessous." + shibboleth_linked_text: "Votre compte est associé à votre authentifiant de l'établissement." + shibboleth_to_link_text: "Associez votre compte de l'Assistant PGD à votre authentifiant de l'établissement." + shibboleth_to_link_question: "Voulez-vous associer votre compte de l'Assistant PGD à votre authentifiant de l'établissement?" + shibboleth_unlink_label: "Dissociez votre authentifiant de l'établissement." + shibboleth_unlink_alert: "Alerte concernant la dissociation de votre authentifiant de l'établissement" + shibboleth_unlink_dialog_text: "Vous êtes sur le point de dissocier l'Assistant PGD de votre authentifiant de l'établissement, voulez-vous continuer?
" + shibboleth_wait_confirmation: "En attente d'une confirmation pour :" + + section_label: "Section" + sections_label: "Sections" + questions_label: "Questions" + answers_label: "Réponses" + answer_questions: "Répondre aux questions" + last_edit: "Dernière modification" + select_action: "Choisir une action" + answered_by: "a répondu à cette question " + answered_by_part2: "" + suggested_answer: "Suggestion de réponse" + suggested_example: "Exemple de réponse" + notanswered: "Aucune réponse consignée" + noquestionanswered: "Aucune réponse aux questions" + guidance: "Directives" + policy_expectations: "Attentes de la politique" + export: "Exporter" + guidance_accordion_label: "Directives" + add_comment_accordion_label: "Ajouter une annotation" + comment_accordion_label: "Annotations" + + comments: + add_comment_label: "Ajouter une annotation" + add_comment_text: "Veuillez ajouter une annotation" + comment_label: "Annotations" + comments_label: "Annotations" + view_label: "Voir" + edit_label: "Modifier" + retract_label: "Supprimer" + clear_label: "Supprimer" + commented_by: "Annotation par :" + archive_own_comment_question: "Êtes-vous certain de vouloir supprimer cette annotation?" + archive_own_comment_button_label: "Supprimer" + archive_comment_question: "Êtes-vous certain de vouloir supprimer cette annotation?" + archive_comment_button_label: "Supprimer" + clear_by: "Annotation supprimée par" + retracted: "Annotation supprimée par vous" + + failures: + email_exists: "Cette adresse électronique est déjà inscrite." + registration_error: "Une erreur est survenue lors de l'inscription. Veuillez vérifier que l'adresse électronique saisie soit valide et que le mot de passe choisi soit d'au moins huit caractères." + notices: + successfully_updated: "Les renseignements ont bien été mis à jour. " + sharing_updated: "Les renseignements partagés ont bien été mis à jour." + invitation_issued: "L'invitation a bien été lancée." + enter_email: "Veuillez saisir votre adresse électronique." + access_removed: "Accès révoqué." + user_added: "L'utilisateur a été ajouté au projet." + answer_recorded: "La réponse a bien été sauvegardée." + answer_saving_error: "Une erreur est survenue lors de la sauvegarde de la réponse." + answer_not_changed: "Il n'y a aucun changement au contenu de la réponse - aucune sauvegarde." + comment_created: "Le commentaire a bien été créé." + comment_updated: "Le commentaire a bien été mis à jour." + comment_removed: "Le commentaire a été supprimé." + theme_created: "Le thème a bien été créé." + theme_updated: "Le thème a bien été mis à jour." + page_created: "La page a bien été créée." + page_updated: "La page a bien été mise à jour." + user_created: "L'utilisateur a bien été créé." + project_created: "Le projet a bien été créé." + project_updated: "Le projet a bien été mis à jour." + user_org_role_created: "Le rôle de l'utilisateur a bien été créé." + user_org_role_updated: "Le rôle de l'utilisateur a bien été mis à jour." + user_role_created: "Le type de rôle d'utilisateur a bien été créé." + user_role_updated: "Le type de rôle d'utilisateur a bien été mis à jour." + user_status_created: "Le statut de l'utilisateur a bien été créé." + user_status_updated: "Le statut de l'utilisateur a bien été mis à jour." + user_type_created: "Le type d'utilisateur a bien été créé." + user_type_updated: "Le type d'utilisateur a bien été mis à jour." + link_account_question: "Désirez-vous" + account_no_access: "Ce compte ne permet pas l'accès à ce plan." + plan_updated: "Le plan a bien été mis à jour." + settings_updated: "Les paramètres ont bien été mis à jour." + + progress_bar: + answered: "complétée(s)" + question: "question" + questions: "questions" + + org_type: + funder: "Bailleur de fonds" + institution: "Établissement" + project: "Projet" + organisation: "Organisme" + org_name: "Nom de l'organisme" + school: "École" + publisher: "Éditeur" + other_guidance: "Autres directives" + template: "Modèle" + templates: "Modèles" + child: "Unité" + other_org_help_text: "Veuillez indiquer le nom de votre organisme." + org_select_text: "Veuillez sélectionner un organisme: " + + + + + project: + create: "Créer un plan" + edit: "Modifier les renseignements sur le plan" + grant_title: "Numéro de la subvention" + grant_help_text: "Le numéro de référence de la subvention, le cas échéant [PLANS DE GESTION DES DONNÉES SUIVANT L'OCTROI SEULEMENT]" + not_applicable: "Sans objet / non inscrit dans la liste" + multi_templates: "Il existe un certain nombre de modèles que vous pouvez utiliser. Veuillez en choisir un." + project_name: "Nom du plan" + my_project_name: "Mon plan" + tips_label: "Conseils" + tips_text: "Toutes les questions ne s'appliquent pas à tous les types de projets de recherche; les chercheurs sont invités à répondre aux questions pertinentes à leur projet.
Les chercheurs devraient revenir tout au long du projet pour réviser ou compléter des réponses.
" + success: "Le plan a été créé avec succès." + principal_investigator: "Chercheur principal/Chercheur" + principal_investigator_help_text: "Nom du ou des chercheurs principaux participant au projet" + principal_investigator_id: "Identification du chercheur principal/chercheur" + principal_investigator_id_help_text: "p. ex. ORCID http://orcid.org/." + funder_help_text: "Bailleur de fonds pour la recherche, s'il y a lieu" + funder_name: "Nom du bailleur de fonds" + project_question_desc_label: "Résumé au sujet des questions" + tab_plan: "Renseignements sur le plan" + tab_export: "Exporter" + export_text_html: "Vous pouvez maintenant télécharger votre plan en divers formats, ce qui peut être utile si vous devez joindre votre plan à une demande de subvention. +Sélectionnez le format que vous souhaitez utiliser et cliquez sur « Exporter ».
" + questions_answered: "questions complétées" + not_saved_answers_text_alert: "Vous avez modifié des réponses mais ne les avez pas sauvegardés :" + not_saved_answers_confirmation_alert: "Voulez-vous les sauvegarder maintenant?" + not_saved_answers_header: "Réponses non sauvegardées" + project_data_contact: "Personne-ressource pour les données du plan" + project_data_contact_help_text: "Nom (si différent de celui susmentionné), numéro de téléphone et adresse électronique" + project_name_help_text: "Si vous présentez une demande de financement, inscrivez le nom de la même façon que dans la demande de subvention." + project_desc_help_text_html: "Résumez brièvement le type d'étude (ou les études) afin d'aider les autres à comprendre les raisons pour lesquelles les données sont recueillies ou créées.
Bienvenue Vous êtes maintenant prêt à créer votre premier plan de gestion des données.Cliquez sur le bouton « Créer un plan » ci-dessous pour commencer.
" + project_text_when_project: "Le tableau ci-dessous contient une liste des plans que vous avez créés et de ceux que d'autres personnes partagent avec vous.Ces plans peuvent être modifiés, partagés, exportés ou supprimés en tout temps.
" + confirmation_text: "Confirmer les renseignements sur le plan" + confirmation_text_desc: "Vous utilisez le modèle générique de plan de gestion des données Portage. Si vous avez des suggestions pour améliorer ce modèle, ou si vous souhaiteriez ajouter de nouveaux modèles basés sur les exigences d'un organisme subventionnaire ou sur les besoins d'une discipline, communiquez avec nous à l'adresse suivante : portage@carl-abrc.ca." + confirmation_button_text: "Oui, créer un plan" + project_details_text_html: "Cette page vous donne un aperçu de votre plan. Elle indique les éléments sur lesquels votre plan s'appuie et donne un aperçu des questions qui vous seront posées." + project_details_editing_text_html: "Répondre aux questions de base ci-dessous sur votre projet et cliquer sur 'Enregistrer' pour sauvegarder." + confirm_delete_text: "Êtes-vous sûr de vouloir supprimer ce plan? En supprimant le plan de votre liste, il sera également supprimé de la liste de plans des personnes avec lesquelles le plan est partagé, le cas échéant." + confirmation_text: "Confirmer les renseignements sur le plan" + confirmation_text_desc: "Vous utilisez le modèle générique de plan de gestion des données Portage. Si vous avez des suggestions pour améliorer ce modèle, ou si vous souhaiteriez ajouter de nouveaux modèles basés sur les exigences d'un organisme subventionnaire ou sur les besoins d'une discipline, communiquez avec nous à l'adresse suivante : portage@carl-abrc.ca." + + confirmation_button_text: "Oui, créer un plan" + default_confirmation_text_desc: "Vous avez sélectionné le plan de gestion des données par défaut, qui est établi en fonction de la liste de vérification du Digital Curation Center (UK). Vous avez ainsi accès à une série générale de questions et de directives sur le plan de gestion des données. Pour de plus amples renseignements, consultez la : DMP checklist 2013 (Liste de vérification 2013 pour un plan de gestion des données)." + default_confirmation_button_text: "Créer un plan" + alert_default_template_text_html: " Veuillez noter que %{org_name} fournit un modèle de plan de gestion des données. Si vous désirez l'utiliser, sélectionnez « Annuler », autrement cliquez sur « Créer un plan »." + share: + tab_share: "Partager" + shared_label: "Partagé?" + share_text_html: "Vous pouvez permettre aux autres d'avoir accès à votre plan. Il y a trois niveaux d'autorisation.
Ajoutez chaque collaborateur à tour de rôle en indiquant son adresse électronique ci-dessous, en choisissant un niveau d'autorisation et en cliquant sur \"Ajouter un collaborateur\".
Les personnes invitées recevront un avis par courriel pour les informer qu'elles ont accès à ce plan et pour les inviter à s'inscrire à l'Assistant PGD si elles n'ont pas déjà un compte. Un avis est également émis lorsque le niveau d'autorisation d'un utilisateur est modifié.
" + collaborators: "Collaborateurs" + add_collaborator: "Ajouter un collaborateur" + add: "Ajouter" + permissions: "Autorisations" + permissions_desc: "Les éditeurs peuvent collaborer aux plans. Les copropriétaires ont des droits supplémentaires et peuvent modifier les renseignements sur le plan et contrôler l'accès." + remove: "Supprimer l'accès d'un utilisateur" + confirmation_question: "Êtes-vous sûr?" + owner: "Propriétaire" + co_owner: "Copropriétaire" + edit: "Éditer" + read_only: "Lecture seule" + locked_section_text: "Cette section est verouillée pour permettre sa modification par " + email_text: "Des droits d'accès '%{access_level}' au projet PGD %{project_link} vous ont été octroyés.
" + permission_email_text: "Les droits d'accès au projet PGD '%{project_link}' ont été changés. Vous avez maintenant un accès %{access_level}.
" + access_removed_email_text: "Votre droit d'accès au projet PGD '%{project_title}' a été révoqué.
" + export: + generated_by: "Ce document a été généré par l'Assistant PGD (https://reseauportage.ca)" + admin_details: "Renseignements administratifs" + create_page: + title: "Créer un nouveau plan" + desc_html: "Choisissez parmi les listes déroulantes suivantes pour que nous puissions déterminer les questions et les directives à afficher dans votre plan.
+Si vous n'avez pas à répondre aux exigences spécifiques d'un organisme subventionnaire ou d'un établissement, vous pouvez choisir le modèle de plan de gestion Portage qui s'appuie sur des normes internationales et sur les meilleures pratiques. Il a été préparé et est gardé à jour par un groupe d'experts en gestion des données de recherche travaillant au sein de bibliothèques de recherche à travers le Canada.
" + default_template: "Plan de gestion des données par défaut" + funders_question: "Si vous présentez une demande de financement, sélectionnez votre bailleur de fonds pour la recherche." + funders_question_description: "Autrement, laissez l'espace vide." + institution_question: "Choisir l'option appropriée dans le menu déroulant pour que les questions et conseils appropriés s'affichent dans votre plan." + institution_question_description: "Vous pouvez ne faire aucune sélection ou choisir un établissement ou organisme autre que le vôtre. Le modèle Portage sera utilisé par défaut s'il n'y a aucune sélection." + other_guidance_question: "Cochez les cases correspondantes pour sélectionner d'autres directives que vous aimeriez consulter." + other_funder_name_label: "Nom du bailleur de fonds, le cas échéant" + template_question: "Choisir un modèle" + configure: "Configurer" + columns: + name: "Nom" + owner: "Propriétaire" + shared: "Partagé?" + template_owner: "Propriétaire du modèle" + last_edited: "Dernière modification" + identifier: "Identifiant" + grant_number: "Numéro de la subvention" + principal_investigator: "Chercheur principal/chercheur" + data_contact: "Personne-ressource pour les données du plan" + description: "Description" + filter: + placeholder: "Filtrer les plans" + submit: "Filtrer" + cancel: "Annuler" + no_matches: "Aucune correspondance pour '%{filter}'" + + plan: + export: + default_title: "Titre PGD" + pdf: + question_not_answered: "Question sans réponse." + generated_by: "Ce document a été généré par l'Assistant PGD (https://reseauportage.ca)" + space_used: "Environ %{space_used}% de l'espace disponible utilisé (%{num_pages} pages maximum)" + project_name: "Nom du projet" + project_identifier: "Identifiant du projet" + grant_title: "Titre de la subvention" + principal_investigator: "Chercheur principal/chercheur" + project_data_contact: "Personne-ressource pour les données du plan" + project_description: "Description" + funder: "Bailleur de fonds" + institution: "Établissement" + section: "Section" + question: "Question" + answer: "Réponse" + selected_options: "Option(s) choisie(s)" + answered_by: "Réponse faite par" + answered_at: "Réponse faite à" + settings: + title: "Paramètres" + projects: + title: "Paramètres - Mes plans" + desc: "Le tableau ci-dessous indique les colonnes disponibles qui peuvent être affichées dans la liste « Mes plans ». Choisissez celles que vous souhaitez voir apparaître." + errors: + no_name: "La colonne « nom » doit faire partie de la liste de colonnes." + duplicate: "Copiez le nom de la colonne. Sélectionnez chaque colonne une seule fois." + unknown: "Nom de colonne inconnu" + plans: + admin_details: "Renseignements administratifs" + sections: "Sections" + title: "Titre du plan" + reset: "Réinitialiser" + custom_formatting: "(À l'aide des valeurs de mise en forme de PDF personnalisées)" + template_formatting: "(À l'aide des valeurs de mise en forme de PDF modèles)" + default_formatting: "(À l'aide des valeurs de mise en forme de PDF par défaut)" + included_elements: "Éléments inclus" + pdf_formatting: "Mise en forme du PDF" + font: "Police" + font_face: "Caractère" + font_size: "Taille" + margin: "Marges" + margins: + top: "Haut" + bottom: "Bas" + left: "Gauche" + right: "Droite" + max_pages: "Nombre maximal de pages" + errors: + missing_key: "Un paramètre demandé n'a pas été fourni." + invalid_margin: "La valeur de la marge est invalide." + negative_margin: "La valeur de la marge ne peut pas être négative." + unknown_margin: "Marge inconnue. On peut seulement choisir « haut », « bas », « gauche » ou « droite »." + invalid_font_size: "Taille de la police invalide" + invalid_font_face: "Caractère de la police invalide" + unknown_key: "Paramètre de mise en forme inconnu" + invalid_max_pages: "Nombre maximal de pages invalide" + mailer: + sharing_notification: "Des droits d'accès à un plan de gestion de données vous ont été octroyés" + permissions_change: "Plan de gestion de données : droits d'accès modifiés" + access_removed: "Plan de gestion de données : accès révoqué" + + about_page: + title: "À propos de l'Assistant PGD" + tab_1: "Assistant PGD" + tab_2: "Modèle de plan de gestion des données Portage" + body_text_tab_1_html: "+L'Assistant PGD est un outil d'aide à la préparation d'un plan de gestion des données (PGD). +
+Les meilleures pratiques en matière de gestion des données sont utilisées pour conseiller le chercheur.
+L'Assistant PGD comprend un modèle générique de plan de gestion des données, Portage, que les chercheurs peuvent utiliser. Des directives sont fournies afin de les aider à interpréter les questions et à y répondre.
+ +Nous souhaitons obtenir vos commentaires! Si vous avez des suggestions sur la façon d'améliorer le modèle existant, ou si vous aimeriez ajouter d'autres modèles basés sur les exigences d'organismes de financement ou sur les besoins des disciplines, communiquez avec votre établissement universitaire ou communiquez avec nous à portage@carl-abrc.ca. + +
+Si vous avez un compte, connectez-vous et commencez à créer ou modifier votre plan de gestion des données.
+Si vous ne possédez pas de compte dans l'Assistant PGD, cliquez sur « S'inscrire » dans la page d'accueil.
+Veuillez noter que nous travaillons actuellement à un système d'authentification unique. Vous pourrez éventuellement associer votre compte existant à votre identifiant campus dès que la fonction sera disponible. + +
Visitez la page « Aide » pour consulter l'aide disponible.
+Si vous avez des questions ou des commentaires au sujet de l'Assistant PGD, communiquez avec votre établissement universitaire ou communiquez avec nous par courriel à portage@carl-abrc.ca.
+Le modèle de plan de gestion des données Portage s'appuie sur des normes internationales et sur les meilleures pratiques. Il a été préparé et est gardé à jour par un groupe d'experts en gestion des données de recherche travaillant au sein de bibliothèques de recherche à travers le Canada.
+ +Les organismes peuvent rendre disponible leur propre modèle de plan dans l'Assistant PGD. Le modèle Portage est le modèle par défaut. On peut sélectionner le modèle d'un autre organisme à l'aide du menu déroulant.
+ +Les organismes subventionnaires, universités et autres organismes qui souhaiteraient faire intégrer leur modèle de plan peuvent communiquer leur demande à l'adresse suivante : portage@carl-abrc.ca.
" + + + + help_page: + title: "Aide" + tab_1: "Concernant l'Assistant PGD" + tab_2: "Concernant la planification de la gestion des données" + tab_3: "Personne-ressource dans votre institution" + #body_text_tab_2_html: "Le service des bibliothèques de l'Université de l'Alberta a mis au point un research data management guide (guide sur la gestion des données de recherche) qui peut fournir d'autres directives sur la planification de la gestion des données. Si vous avez besoin de plus de directives, communiquez avec nous par courriel à portage@carl-abrc.ca.
" + body_text_tab_2_html: "Si vous avez besoin de plus de directives, communiquez avec nous par courriel à portage@carl-abrc.ca." + + + body_text_tab_1_html: "Lorsque vous vous connectez à l'Assistant PGD, vous serez dirigé vers la page « Mes plans ». À partir de cette page, vous pouvez modifier, partager, exporter ou supprimer l'un ou l'autre de vos plans. Vous verrez également les plans qui ont été partagés avec vous par d'autres personnes.
+Pour créer un plan, cliquez sur le bouton « Créer un plan » à la page « Mes plans » ou dans le menu du haut. Faites des choix dans les listes déroulantes et les cases à cocher afin de déterminer les questions et les directives qui seront affichées. Confirmez votre choix en cliquant sur « Oui, créer un plan ».
+L'interface à onglets vous permet de naviguer dans diverses fonctions lorsque vous mettez au point votre plan.
+Lorsque vous consultez l'un ou l'autre des onglets de questions, vous verrez les différentes sections de votre plan affichées. Cliquez sur ces onglets à tour de rôle pour répondre aux questions. Vous pouvez choisir le format de vos réponses à l'aide des boutons de mise en forme.
+Les directives sont affichées dans la partie de droite. Cliquez sur le symbole « + » pour les consulter.
+N'oubliez pas d'enregistrer vos réponses avant de poursuivre.
+Inscrivez l'adresse électronique de tout collaborateur que vous aimeriez inviter à lire ou à modifier votre plan. Choisissez le niveau d'autorisation que vous souhaitez lui accorder dans les options de la liste déroulante et cliquez sur « Ajouter un collaborateur ».
+En choisissant cette option, vous pouvez télécharger votre plan en divers formats, ce qui peut être utile si vous devez joindre votre plan à une demande de subvention. Choisissez le format dans lequel vous aimeriez voir ou télécharger votre plan et cliquez pour l'exporter. Lorsque vous vous connectez à l'Assistant PGD, vous êtes dirigé vers la page « Mes plans ». À partir de cette page, vous pouvez modifier, partager, exporter ou supprimer l'un ou l'autre de vos plans. Vous voyez également les plans qui ont été partagés avec vous par d'autres personnes.
" + + + body_text_tab_3_html: "Votre bibliothèque universitaire offre peut-être déjà du soutien dans le développement de plans de gestion de données. Communiquez avec le bibliothécaire responsable de votre discipline au sein de votre établissement pour en en savoir davantage. Vous trouverez ci-dessous les coordonnées dans le cas des bibliothèques universitaires qui ont une personne-ressource désignée ou un service spécialisé dans la gestion des données de recherche.
+Si votre établissement n'est pas listé, vous pourriez aussi communiquer avec le Réseau Portage à l'adresse suivante : portage@carl-abrc.ca. On pourra vous rediriger vers la ressource la plus appropriée à votre demande.
+Acadia University: Maggie Neilson
+Brandon University: Carmen Kazakoff-Lane, Betty Braaksma
+Brock University: Heather Whipple
+Carleton University: Jane Fry, Sylvie Lafortune
+Concordia University: Alex Guindon, Danielle Dennie
+Kwantlen Polytechnic University: Chris Burns, Todd Mundle
+Lakehead University: Debra Gold
+MacEwan University: Tara Stieglitz
+McGill University : K. Jane Burpee, Jenn Riley
+McMaster University: RDM@McMaster, Jay Brodeur
+Mount Allison University: Ruth Collings
+Queen's University: Jeff Moon, Alexandra Cooper
+Simon Fraser University: Carla Graebner
+Université de Moncton: Victoria Volkanova
+University of British Columbia: Eugene Barsky, Research Data Team
+University of Alberta: Research Data Management Group, Larry Laliberte
+University of Calgary: John Brosz, Susan Powelson
+University of Guelph: Research Enterprise & Scholarly Communication Team
+University of Lethbridge: Research Services Group [U. of Lethbridge Library]
+University of Manitoba: Mayu Ishida, Gary Strike
+University of Ontario Institute of Technology: Katie Harding
+University of Ottawa / Université d\'Ottawa: uOttawa Library Research Data Management Group, Talia Chung
+University of Regina: Marilyn Andrews
+University of Victoria: Kathleen Matthews, Daniel Brendle-Moczuk
+University of Waterloo: Research Data Management Services
+Western University: Western RDM Group, Western Libraries RDM Subcommittee
+Wilfrid Laurier University: Michael Steeleworthy
" + + + + contact_page: + title: "Communiquez avec nous" + intro_text_html: "L'Assistant PGD est rendu disponible par les Bibliothèques de l'Université d'Alberta. Pour en savoir plus sur les services offerts par ces bibliothèques, consulter la page suivante : Research Data Management page. Si vous désirez communiquer avec nous concernant l'Assistant PGD, merci de saisir votre message dans le formulaire Web ci-dessous ou nous écrire à portage@carl-abrc.ca.
+" + + terms_page: + title: "Exploitation sous licence et conditions d'utilisation" + body_text_html: " + +Le Réseau Portage est un regroupement de bibliothèques travaillant à la gestion des données de recherche au Canada.
+L'Assistant PGD (\"l'outil\",\"le système\") est fourni grâce à une application à code source libre appelée DMPOnline qui a été mise au point par le Digital Curation Centre (DCC) et partagée en vertu de la AGPL license (licence publique générale Affero).
+ +Le modèle de plan de gestion des données Portage ainsi que les directives reliées de l'Assistant PGD Portage (mais pas sur les plans mêmes) sont distribués en vertu d'une Creative Commons Zero License (licence Creative Commons Zéro).
+ + + +Les modèles institutionnels de plan de gestion des données ainsi que les directives qui y sont reliées sont distribués en vertu de leurs propres licences Creative Commons. Contacter chaque institution pour obtenir plus d'information.
+Le service des bibliothèques de l'Université de l'Alberta héberge l'Assistant PGD et conserve vos plans de gestion des données en votre nom, mais les plans vous appartiennent et sont sous votre responsabilité. Les renseignements conservés par Assistant PGD sont régis par la politique de confidentialité du Site Web du service des bibliothèques de l'Université de l'Alberta.
+Votre mot de passe est mémorisé sous forme codée et ne peut pas être récupéré. Si vous avez oublié votre mot de passe, vous devez le réinitialiser.
+En utilisant l'outil, vous comprenez et acceptez ces conditions.
Questions to consider:
Guidance:
Give a brief description of the data, including any existing data or third-party sources that will be used, in each case noting its content, type and coverage. Outline and justify your choice of format and consider the implications of data format and data volumes in terms of storage, backup and access.
", - themes: ["Theme 1", "Theme 2"] - }, - "How will the data be collected or created?" => { - text: "How will the data be collected or created?", - section: "Data Collection", - number: 2, - guidance: "Questions to consider:
Guidance:
Outline how the data will be collected/created and which community data standards (if any) will be used. Consider how the data will be organised during the project, mentioning for example naming conventions, version control and folder structures. 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: ["Theme 3"] - }, - "What documentation and metadata will accompany the data?" => { - text: "What documentation and metadata will accompany the data?", - section: "Documentation and Metadata", - number: 1, - guidance: "Questions to consider:
Guidance:
Describe the types of documentation that will accompany the data to help secondary users to understand and reuse it. This should at least include basic details that will help people to find the data, including who created or contributed to the data, its title, date of creation and under what conditions it can be accessed.
Documentation may also include details on the methodology used, analytical and procedural information, definitions of variables, vocabularies, units of measurement, any assumptions made, and the format and file type of the data. Consider how you will capture this information and where it will be recorded. Wherever possible you should identify and use existing community standards.
", - themes: ["Theme 1", "Theme 4"] - }, - "How will you manage any ethical issues?" => { - text: "How will you manage any ethical issues?", - section: "Ethics and Legal Compliance", - number: 1, - guidance: "Questions to consider:
Guidance:
Ethical issues affect how you store data, who can see/use it and how long it is kept. Managing ethical concerns may include: anonymisation of data; referral to departmental or institutional ethics committees; and formal consent agreements. You should show that you are aware of any issues and have planned accordingly. If you are carrying out research involving human participants, you must also ensure that consent is requested to allow data to be shared and reused.
", - themes: ["Theme 4"] - }, - "How will you manage copyright and Intellectual Property Rights (IPR) issues?" => { - text: "How will you manage copyright and Intellectual Property Rights (IPR) issues?", - section: "Ethics and Legal Compliance", - number: 2, - guidance: "Questions to consider:
Guidance:
State who will own the copyright and IPR of any data that you will collect or create, along with the licence(s) for its use and reuse. For multi-partner projects, IPR ownership may be worth covering in a consortium agreement. Consider any relevant funder, institutional, departmental or group policies on copyright or IPR. Also consider permissions to reuse third-party data and any restrictions needed on data sharing.
", - themes: ["Theme 1"] - }, - "How will the data be stored and backed up during the research?" => { - text: "How will the data be stored and backed up during the research?", - section: "Storage and Backup", - number: 1, - guidance: "Questions to consider:
Guidance:
State how often the data will be backed up and to which locations. How many copies are being made? 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. Similarly, it is normally better to use automatic backup services provided by IT Services than rely on manual processes. If you choose to use a third-party service, you should ensure that this does not conflict with any funder, institutional, departmental or group policies, for example in terms of the legal jurisdiction in which data are held or the protection of sensitive data.
", - themes: ["Theme 2"] - }, - "4a: Preserving Your Data" => { - text: "4a: Preserving Your Data", - section: "4: Preservation, Sustainability and Use", - number: 1, - guidance: "Preservation of digital outputs is necessary in order for them to endure changes in the technological environment and remain potentially re-usable in the future. In this section you must state what, if any, digital outputs of your project you intend to preserve beyond the period of funding.
The length and cost of preservation should be proportionate to the value and significance of the digital outputs. If you believe that none of these should be preserved this must be justified, and if the case is a good one the application will not be prejudiced.
You must consider preservation in four ways: what, where, how and for how long. You must also consider any institutional support needed in order to carry out these plans, whether from an individual, facility, organisation or service.
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 re-usability, you should use standards and formats that facilitate this.
The Technical Reviewer will be looking for evidence that you understand the reasons for the choice of technical standards and formats described in Section 2.a Technical Methodology: Standards and Formats.
You should describe the types of documentation which will accompany the data. Documentation in this sense means technical documentation as well as user documentation. It includes, for instance, technical description, code commenting, project-build guidelines, the documentation of technical decisions and resource metadata which is additional to the standards which you have described in Section 2.a. Not all types of documentation will be relevant to a project and the quantity of documentation proposed should be proportionate to the envisaged value of the data.
", - themes: ["Theme 2", "Theme 3", "Theme 4"] - }, - "4b: Ensuring Continued Accessibility and Use of Your Digital Outputs" => { - text: "4b: Ensuring Continued Accessibility and Use of Your Digital Outputs", - section: "4: Preservation, Sustainability and Use", - number: 2, - guidance: "In this section you must provide information about any plans for ensuring that digital outputs remain sustainable in the sense of immediately accessible and usable beyond the period of funding. There are costs to ensuring sustainability in this sense over and above the costs of preservation. The project's sustainability plan should therefore be proportionate to the envisaged longer-term value of the data for the research community and should be closely related to your plans for dissemination and Pathways to Impact.
If you believe that digital outputs should not be sustained beyond the period of funding then this should be justified. It is not mandatory to sustain all digital outputs. While you should consider the long-term value of the digital outputs to the research community, where they are purely ancillary to a project’s research outputs there may not be a case for sustaining them (though there would usually be a case for preservation).
You must consider the sustainability of your digital outputs in five ways: what, where, how, for how long, and how the cost will be covered. You must make appropriate provision for user consultation and user testing in this connection, and plan the development of suitable user documentation.
You should provide justification if you do not envisage open, public access. A case can be made for charging for or otherwise limiting access, but the default expectation is that access will be open. The Technical Reviewer will be looking for realistic commitments to sustaining public access in line with affordability and the longer-term value of the digital output.
You must consider any institutional support needed in order to carry out these plans, if not covered under Section 3, as well as the cost of keeping the digital output publicly available in the future, including issues relating to maintenance, infrastructure and upgrade (such as the need to modify aspects of a web interface or software application in order to account for changes in the technological environment). In order to minimise sustainability costs, it is generally useful that the expertise involved in the development of your project is supported by expertise in your own or a partner institution.
A sustainability plan does not necessarily mean a requirement to generate income or prevent resources from being freely available. Rather it is a requirement to consider the direct costs and expertise of maintaining digital outputs for continued access. Some applicants might be able to demonstrate that there will be no significant sustainability problems with their digital output; in some cases the university’s computing services or library might provide a firm commitment to sustaining the resource for a specified period; others might see the benefit of Open Source community development models. You should provide reassurances of sustainability which are proportionate to the envisaged longer-term value of the digital outputs for the research community.
When completing this section, you should consider the potential impact of the data on research in your field (if research in the discipline will be improved through the creation of the digital output, how will it be affected if the resource then disappears?), and make the necessary connections with your Impact Plan. You must factor in the effects of any IP, copyright and ethical issues during the period in which the digital output will be publicly accessible, connecting what you say with the relevant part of your Case for Support.
You must identify whether or not you envisage the academic content (as distinct from the technology) of the digital output being extended or updated beyond the period of funding, addressing the following issues: how this will be done, by who and at what cost. You will need to show how the cost of this will be sustained after the period of funding ends.
", - themes: ["Theme 2"] - } - } - - questions.each do |q, details| - question = Question.new - question.text = details[:text] - question.number = details[:number] - question.guidance = details[:guidance] - question.section = Section.find_by_title(details[:section]) - details[:themes].each do |theme| - question.themes << Theme.find_by_title(theme) - end - question.save! - end - - formatting = { - 'Funder' => { - font_face: "Arial, Helvetica, Sans-Serif", - font_size: 11, - margin: { top: 20, bottom: 20, left: 20, right: 20 } - }, - 'DCC' => { - font_face: "Arial, Helvetica, Sans-Serif", - font_size: 12, - margin: { top: 20, bottom: 20, left: 20, right: 20 } - } } - formatting.each do |org, settings| +users.each do |user, details| + user = User.new + user.email = details[:email] + user.password = details[:password] + user.password_confirmation = details[:password_confirmation] + user.confirmed_at = details[:confirmed_at] + details[:roles].each do |role| + user.roles << Role.find_by( name: role ) + end + user_roles = UserOrgRole.new + user_roles.organisation = Organisation.find_by( abbreviation: details[:organisation]) + user_roles.user = user + user_roles.save! + user.user_org_roles << user_roles + user.accept_terms = details[:accept_terms] + user.save! + +end + + +themes = { + "Theme 1" => { + title: "Theme 1", + locale: "en" + }, + "Theme 2" => { + title: "Theme 2", + locale: "en" + }, + "Theme 3" => { + title: "Theme 3", + locale: "en", + description: "Theme 3 description." + }, + "Theme 4" => { + title: "Theme 4", + locale: "en", + description: "Theme 4 description." + } +} + +themes.each do |t, details| + theme = Theme.new + theme.title = details[:title] + theme.locale = details[:locale] + theme.description = details[:description] + theme.save! +end + +question_formats = { + "Text area" => { + title: "Text area" + }, + "Text field" => { + title: "Text field" + }, + "Radio buttons" => { + title: "Radio buttons" + }, + "Check box" => { + title: "Check box" + }, + "Dropdown" => { + title: "Dropdown" + }, + "Multi select box" => { + title: "Multi select box" + }, +} + +question_formats.each do |qf, details| + question_format = QuestionFormat.new + question_format.title = details[:title] + question_format.save! +end + +guidance_groups = { + "Default Guidance group" => { + name: "Default Guidance group name", + organisation: "Institution_example", + optional_subset: false + }, + "Optional Guidance group" => { + name: "Optional Guidance group name", + organisation: "Funder_example", + optional_subset: true + } +} + +guidance_groups.each do |gg, details| + guidance_group = GuidanceGroup.new + guidance_group.name = details[:name] + guidance_group.organisation = Organisation.find_by_abbreviation(details[:organisation]) + guidance_group.optional_subset = details[:optional_subset] + guidance_group.save! +end + +guidances = { + "Guidance 1" => { + text: "Guidance text", + guidance_group: "Default Guidance group name", + themes: ["Theme 4"] + }, + "Guidance 2" => { + text: "Guidance text", + guidance_group: "Optional Guidance group name", + themes: ["Theme 2"] + }, + "Guidance 3" => { + text: "Guidance text", + guidance_group: "Default Guidance group name", + themes: ["Theme 3"] + }, + "Guidance 4" => { + text: "Guidance text", + guidance_group: "Optional Guidance group name", + themes: ["Theme 1"] + } +} + +guidances.each do |g, details| + guidance = Guidance.new + guidance.text = details[:text] + guidance.guidance_groups << GuidanceGroup.find_by_name(details[:guidance_group]) + details[:themes].each do |theme| + guidance.themes << Theme.find_by_title(theme) + end + guidance.save! +end + +templates = { + "DCC" => { + title: "DCC Template", + description: "The default DCC template", + published: true, + organisation: "DCC", + locale: "en", + is_default: true + }, + "Funder Template" => { + title: "Funder Template", + description: "Funder template description", + published: true, + organisation: "Funder_example", + locale: "en", + is_default: false + } +} + +templates.each do |t, details| + template = Dmptemplate.new + template.title = details[:title] + template.description = details[:description] + template.published = details[:published] + template.locale = details[:locale] + template.is_default = details[:is_default] + template.organisation = Organisation.find_by_abbreviation(details[:organisation]) + template.save! +end + +phases = { + "DCC" => { + title: "DCC Data Management Plan", + number: 1, + template: "DCC Template" + }, + "Funder Template" => { + title: "Funder Technical Plan", + number: 1, + template: "Funder Template" + }, +} + +phases.each do |p, details| + phase = Phase.new + phase.title = details[:title] + phase.number = details[:number] + phase.dmptemplate = Dmptemplate.find_by_title(details[:template]) + phase.save! +end + +versions = { + "DCC" => { + title: "DCC Template Version 1", + number: 1, + phase: "DCC Template" + }, + "Funder" => { + title: "Funder Data Management Plan (Version 1)", + number: 1, + phase: "Funder Technical Plan" + }, +} + +versions.each do |v, details| + version = Version.new + version.title = details[:title] + version.number = details[:number] + version.phase = Phase.find_by_title(details[:phase]) + version.save! +end + +sections = { + "Section 1" => { + title: "Data Collection", + number: 1, + 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.", + version: "DCC Template Version 1", + organisation: "DCC" + }, + "Section 2" => { + title: "Documentation and Metadata", + number: 2, + 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.", + version: "DCC Template Version 1", + organisation: "DCC" + }, + "1: Section" => { + title: "1: Section", + number: 1, + version: "Funder Data Management Plan (Version 1)", + organisation: "Funder_example" + }, + "2: Section" => { + title: "2: Section", + number: 2, + version: "Funder Data Management Plan (Version 1)", + organisation: "Funder_example" + }, + "3: Section" => { + title: "3: Section", + number: 3, + version: "Funder Data Management Plan (Version 1)", + organisation: "Funder_example" + }, + "4: Section" => { + title: "4: Section", + number: 4, + version: "Funder Data Management Plan (Version 1)", + organisation: "Institution_example" + } +} + +sections.each do |s, details| + section = Section.new + section.title = details[:title] + section.number = details[:number] + section.description = details[:description] + section.version = Version.find_by_title(details[:version]) + section.organisation = Organisation.find_by_abbreviation(details[:organisation]) + section.save! +end + +questions = { + "What data will you collect or create?" => { + text: "What data will you collect or create?", + section: "Data Collection", + number: 1, + guidance: "Questions to consider:
Guidance:
Give a brief description of the data, including any existing data or third-party sources that will be used, in each case noting its content, type and coverage. Outline and justify your choice of format and consider the implications of data format and data volumes in terms of storage, backup and access.
", + themes: ["Theme 1", "Theme 2"] + }, + "How will the data be collected or created?" => { + text: "How will the data be collected or created?", + section: "Data Collection", + number: 2, + guidance: "Questions to consider:
Guidance:
Outline how the data will be collected/created and which community data standards (if any) will be used. Consider how the data will be organised during the project, mentioning for example naming conventions, version control and folder structures. 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: ["Theme 3"] + }, + "What documentation and metadata will accompany the data?" => { + text: "What documentation and metadata will accompany the data?", + section: "Documentation and Metadata", + number: 1, + guidance: "Questions to consider:
Guidance:
Describe the types of documentation that will accompany the data to help secondary users to understand and reuse it. This should at least include basic details that will help people to find the data, including who created or contributed to the data, its title, date of creation and under what conditions it can be accessed.
Documentation may also include details on the methodology used, analytical and procedural information, definitions of variables, vocabularies, units of measurement, any assumptions made, and the format and file type of the data. Consider how you will capture this information and where it will be recorded. Wherever possible you should identify and use existing community standards.
", + themes: ["Theme 1", "Theme 4"] + }, + "How will you manage any ethical issues?" => { + text: "How will you manage any ethical issues?", + section: "Ethics and Legal Compliance", + number: 1, + guidance: "Questions to consider:
Guidance:
Ethical issues affect how you store data, who can see/use it and how long it is kept. Managing ethical concerns may include: anonymisation of data; referral to departmental or institutional ethics committees; and formal consent agreements. You should show that you are aware of any issues and have planned accordingly. If you are carrying out research involving human participants, you must also ensure that consent is requested to allow data to be shared and reused.
", + themes: ["Theme 4"] + }, + "How will you manage copyright and Intellectual Property Rights (IPR) issues?" => { + text: "How will you manage copyright and Intellectual Property Rights (IPR) issues?", + section: "Ethics and Legal Compliance", + number: 2, + guidance: "Questions to consider:
Guidance:
State who will own the copyright and IPR of any data that you will collect or create, along with the licence(s) for its use and reuse. For multi-partner projects, IPR ownership may be worth covering in a consortium agreement. Consider any relevant funder, institutional, departmental or group policies on copyright or IPR. Also consider permissions to reuse third-party data and any restrictions needed on data sharing.
", + themes: ["Theme 1"] + }, + "How will the data be stored and backed up during the research?" => { + text: "How will the data be stored and backed up during the research?", + section: "Storage and Backup", + number: 1, + guidance: "Questions to consider:
Guidance:
State how often the data will be backed up and to which locations. How many copies are being made? 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. Similarly, it is normally better to use automatic backup services provided by IT Services than rely on manual processes. If you choose to use a third-party service, you should ensure that this does not conflict with any funder, institutional, departmental or group policies, for example in terms of the legal jurisdiction in which data are held or the protection of sensitive data.
", + themes: ["Theme 2"] + }, + "4a: Preserving Your Data" => { + text: "4a: Preserving Your Data", + section: "4: Preservation, Sustainability and Use", + number: 1, + guidance: "Preservation of digital outputs is necessary in order for them to endure changes in the technological environment and remain potentially re-usable in the future. In this section you must state what, if any, digital outputs of your project you intend to preserve beyond the period of funding.
The length and cost of preservation should be proportionate to the value and significance of the digital outputs. If you believe that none of these should be preserved this must be justified, and if the case is a good one the application will not be prejudiced.
You must consider preservation in four ways: what, where, how and for how long. You must also consider any institutional support needed in order to carry out these plans, whether from an individual, facility, organisation or service.
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 re-usability, you should use standards and formats that facilitate this.
The Technical Reviewer will be looking for evidence that you understand the reasons for the choice of technical standards and formats described in Section 2.a Technical Methodology: Standards and Formats.
You should describe the types of documentation which will accompany the data. Documentation in this sense means technical documentation as well as user documentation. It includes, for instance, technical description, code commenting, project-build guidelines, the documentation of technical decisions and resource metadata which is additional to the standards which you have described in Section 2.a. Not all types of documentation will be relevant to a project and the quantity of documentation proposed should be proportionate to the envisaged value of the data.
", + themes: ["Theme 2", "Theme 3", "Theme 4"] + }, + "4b: Ensuring Continued Accessibility and Use of Your Digital Outputs" => { + text: "4b: Ensuring Continued Accessibility and Use of Your Digital Outputs", + section: "4: Preservation, Sustainability and Use", + number: 2, + guidance: "In this section you must provide information about any plans for ensuring that digital outputs remain sustainable in the sense of immediately accessible and usable beyond the period of funding. There are costs to ensuring sustainability in this sense over and above the costs of preservation. The project's sustainability plan should therefore be proportionate to the envisaged longer-term value of the data for the research community and should be closely related to your plans for dissemination and Pathways to Impact.
If you believe that digital outputs should not be sustained beyond the period of funding then this should be justified. It is not mandatory to sustain all digital outputs. While you should consider the long-term value of the digital outputs to the research community, where they are purely ancillary to a project’s research outputs there may not be a case for sustaining them (though there would usually be a case for preservation).
You must consider the sustainability of your digital outputs in five ways: what, where, how, for how long, and how the cost will be covered. You must make appropriate provision for user consultation and user testing in this connection, and plan the development of suitable user documentation.
You should provide justification if you do not envisage open, public access. A case can be made for charging for or otherwise limiting access, but the default expectation is that access will be open. The Technical Reviewer will be looking for realistic commitments to sustaining public access in line with affordability and the longer-term value of the digital output.
You must consider any institutional support needed in order to carry out these plans, if not covered under Section 3, as well as the cost of keeping the digital output publicly available in the future, including issues relating to maintenance, infrastructure and upgrade (such as the need to modify aspects of a web interface or software application in order to account for changes in the technological environment). In order to minimise sustainability costs, it is generally useful that the expertise involved in the development of your project is supported by expertise in your own or a partner institution.
A sustainability plan does not necessarily mean a requirement to generate income or prevent resources from being freely available. Rather it is a requirement to consider the direct costs and expertise of maintaining digital outputs for continued access. Some applicants might be able to demonstrate that there will be no significant sustainability problems with their digital output; in some cases the university’s computing services or library might provide a firm commitment to sustaining the resource for a specified period; others might see the benefit of Open Source community development models. You should provide reassurances of sustainability which are proportionate to the envisaged longer-term value of the digital outputs for the research community.
When completing this section, you should consider the potential impact of the data on research in your field (if research in the discipline will be improved through the creation of the digital output, how will it be affected if the resource then disappears?), and make the necessary connections with your Impact Plan. You must factor in the effects of any IP, copyright and ethical issues during the period in which the digital output will be publicly accessible, connecting what you say with the relevant part of your Case for Support.
You must identify whether or not you envisage the academic content (as distinct from the technology) of the digital output being extended or updated beyond the period of funding, addressing the following issues: how this will be done, by who and at what cost. You will need to show how the cost of this will be sustained after the period of funding ends.
", + themes: ["Theme 2"] + } +} + +questions.each do |q, details| + question = Question.new + question.text = details[:text] + question.number = details[:number] + question.guidance = details[:guidance] + question.section = Section.find_by_title(details[:section]) + details[:themes].each do |theme| + question.themes << Theme.find_by_title(theme) + end + question.save! +end + +formatting = { + 'Funder' => { + font_face: "Arial, Helvetica, Sans-Serif", + font_size: 11, + margin: { top: 20, bottom: 20, left: 20, right: 20 } + }, + 'DCC' => { + font_face: "Arial, Helvetica, Sans-Serif", + font_size: 12, + margin: { top: 20, bottom: 20, left: 20, right: 20 } + } +} + +formatting.each do |org, settings| template = Dmptemplate.find_by_title("#{org} Template") template.settings(:export).formatting = settings template.save! end token_permission_types = { - 'guidances' => { - description: "allows a user access to the guidances api endpoint" - }, - 'plans' => { - description: "allows a user access to the plans api endpoint" - } + 'guidances' => { + description: "allows a user access to the guidances api endpoint" + }, + 'plans' => { + description: "allows a user access to the plans api endpoint" + } } token_permission_types.each do |title,settings| @@ -458,6 +458,30 @@ token_permission_type.save! end +languages = { + 'EN-UK' => { + abbreviation: "en-UK", + description: "", + name: "en-UK" + }, + 'FR' => { + abbreviation: "fr", + description: "", + name: "fr" + }, + 'DE' => { + abbreviation: "de", + description: "", + name: "de" + } +} +languages.each do |l, details| + language = Language.new + language.abbreviation = details[:abbreviation] + language.description = details[:description] + language.name = details[:name] + language.save! +end