Skip to content
  • v3.0.1
  • aa01147
  • Compare
    Choose a tag to compare
    Search for a tag
  • v3.0.1
  • aa01147
  • Compare
    Choose a tag to compare
    Search for a tag

@briri briri released this Dec 18, 2020

Researchers:

Administrators:

  • Added feature that lets admins generate or refresh their API token #2410
  • Fixed bug with sorting template sections via the drag and drop feature #2735
  • Fixed a bug that was preventing the plans.complete flag from being set which prevented the plan from appearing in the list of Organizational plans #2745
  • Fixed several bugs on the edit Org details page:
    • You can now update and delete a shibboleth entityID #2288
    • You can now add/edit/remove links #2737
    • You can now edit the Org type #2760

Developers:

A bug in the Organization typeahead boxes on the create account and edit profile pages prevented the v3.0.0 code from calling out to the ROR API. This may have resulted in Org records created via manual user entry with names that do not match the official ROR record and that do not have ROR or Crossref funder ids.

We have added 2 new Rake tasks to assist with cleanup of any affected data.

  • rails org_cleanup:rorify Will collect all of your Orgs that do not have a ROR id in the identifiers table. It will then call out to the ROR API and attempt to locate their identifiers. If found, it will add them to the database. Note that the names must match closely for this task to determine that it found a match in the ROR API.
  • rails org_cleanup:find_dups Will review your Org records and attempt to find duplicates by comparing their names and abbreviations. It will generate a report upon completion that identifies possible duplicates. You will then need to either manually clean up these duplicates in the database or wait until the next release which will include a UI function that allows Super Admins to merge Orgs.

Bug fixes and administrative tasks

  • Updated the README to clarify our level of support #2756
  • Added DB and models to support future UI work to allow users to define multiple research outputs for their plans #2739
  • Add api_clients.org_id as a nillable fkey on that table. Updated the v1 API to use this fkey when determining access to a plan #2725
  • Updated the api_clients.last_access from a t.date to t.datetime in the DB
  • Bug fix for Shibboleth login #2686
  • Fixed a bug that was preventing Org typeahead boxes from searching the ROR API #2746
  • Fixed a bug with the Google Analytics tracker #2732
  • Improved performance of loading an Org's Plans by using Rails.cache #2726
  • Fixed issue with ORCID and Shib auth from the Edit profile page opening in a new tab/window #2752
  • Fixed an issue with using Socket.hostname which was causing issues in certain scenarios #2729
  • Removed uglifier gem since this is now handled via Webpacker #2741
  • Fixed a typo in action for deleting a theme and fixed rendering in shib actions on orgs_controller #2771
  • Synced up the latest translations #2772
Assets 2
  • v3.0.0
  • 1d80bb4
  • Compare
    Choose a tag to compare
    Search for a tag
  • v3.0.0
  • 1d80bb4
  • Compare
    Choose a tag to compare
    Search for a tag

@briri briri released this Nov 6, 2020 · 101 commits to master since this release

Researchers

No major changes to report.

Administrators

  • Introduction of API v1. This new API conforms to the new [common standard metadata format for DMPs](RDA Common Standard Metadata schema v1.0) that was defined an RDA working group. It currently supports: retrieving the list of your DMPs (and any public DMPs), retrieving the metadata for a single DMP, and creating DMPs. All of the JSON that this new API consumes and produces follows the metadata standard. You should continue using API v0 if you need access to a plan's full text or any other features that have not yet been ported over to v1.

Developers

  • Fixed a bug that was preventing users from creating a plan by clicking the icon on the Public Plans page and from the organizational plans table on the My Dashaboard page - Issue 2580
  • Soft launch of the new APIClients section (introduced in v2.2 but worth re-mentioning) that allows you to define systems that will integrate with your installation (as opposed to organizational admins). These new API clients can only API v1 and have very restricted access to DMPs. The functionality available for these clients will continue to grow over the coming years. Please refer to our development roadmap for details.

Upgrade to Rails 5.2

This upgrade brings the codebase from Rails 4.2.x to Rails 5.2.x. This was a major version upgrade and we advise you to review Rails' official upgrade guide to see what has changed. If you have customized the code in any way, you may need to make changes to work with this new version. We have highlighted some of the major changes below along with some changes we've made to consolidate the application's configuration.

The upgrade guides can be found here:

  • Dependencies - This release includes an upgrade to Rails 5.2, Ruby 2.6.3, Node 10.x+ and Yarn 1.22+
    • Upgraded most Gems and Yarn dependencies (see the Gemfile.lock and yarn.lock for details). The primary exceptions are TinyMCE and Bootstrap.
  • Credentials - The application's sensitive credentials have moved from the various YAML files and initializers ito Rails' new encrypted credentials system.
    • Run EDITOR=vi rails credentials:edit (Note: you can use editors other than vi) and copy the content of the config/credentials.yml.example.
    • Update any custom code you have that references those old values (e.g. Rails.application.credentials.devise[:secret_key])
  • Configuration - All custom configuration has been moved from config/application.rb, config/branding.yml and various config/initializers/*.rb into a single config/initializers/_dmproadmap.rb file. This was done to consolidate the applications configuration and make it easier for installations to manage their config.
    • You will need to evaluate your existing configuration and update this new file accordingly.
    • You will also need to evaluate any custom code you may have to use these new files. For example: Rails.configuration.branding[:organisation][:name] becomes Rails.configuration.x.organisation[:name]
  • Strong Parameters - Rails 5.2 no longer passes request parameters around as a Hash. They have instead moved to ActionController::StrongParemeters. This is a breaking change so you will need to review any customizations you have made to controllers.
  • Rake - You no longer run any 'rake' commands. You should instead use 'rails' (e.g. rails db:migrate RAILS_ENV=production)
  • Warning -- check your customized code! If you have placed any customizations to the base DMPRoadmap code in the lib/ directory, you will need to move them into the app/ directory. Rails 5+ has disabled the autoload feature in the production environment. You will need to move your code into the app/ directory and update the module/class hierarchies accordingly (e.g. MyApp::Controllers::PublicPages which was in lib/my_app/controllers/public_pages.rb would become MyApp::PublicPages if moved to app/controllers/my_app/public_pages.rb)
  • Enabled Rubocop for verification that our Ruby code follows the latest community standards
  • The timeago JS strings are now translatable. The 'updated by john.doe@uni.org - 2 days ago' messages are now part of the translation ecosystem - issue 1974

Introduction of Translation.io

We're moving our translation backend to Translation.io. Previously, we were using a combination of FastGetText and I18n for translation. The translation gem simplifies the management of these two transation systems, and provides a web-based service to allow translators to collaborate. This approach allows us to retain the Gettext style translations (full strings in the code and the _("") markup for translation), and gives the flexibility to separately maintain translations for the open-source DMPRoadmap codebase, along with your customization to the codebase and to static-pages.

For more details on how the translations will be managed, along with instructions for translating your customization, see the wiki page on translations

Upgrade guide

Please review the following changes and back up your DB before upgrading!

  • Install the latest versions of Ruby, Node and Yarn (See above for specific version info)
  • Merge in the latest changes (resolving any conflicts it may have with your customizations)
  • Run EDITOR=vi rails credentials:edit (swap 'vi' with your favorite editor) and copy the contents of config/credentials.yml.example into the editor. Replace all of the values with the ones appropriate for your installation. This will generate a config/master.key and config/credentials.yml.enc file. DO NOT commit your master.key into GitHub! See the Rails 5.2 docs for more info on the new approach to managing credentials.
  • Run rails db:migrate
  • Run rails v3:upgrade_3_0_0. This will run scripts that sets your orgs.language_id, users.language_id, orgs.feedback_email_subject and orgs.feedback_email_msg values to the default.
  • Update your customizations to comply with Rails 5.2 (see notes above)
  • Thoroughly test your application
Assets 2
  • v2.2.1
  • 3fdceea
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.2.1
  • 3fdceea
  • Compare
    Choose a tag to compare
    Search for a tag

@briri briri released this Oct 28, 2020 · 531 commits to master since this release

Minor patches to v2.2.0. Including some that address issues with the v2.2.0 upgrade tasks

  • added missing DB indexes
  • fixed bug with one-click plan creation
  • fixed bug with missing contributor names in API v1
  • fixed several bugs with the v2.2.0 upgrade scripts that transform data

If you have not already done so, please follow the upgrade notes in the developer section for release v2.2.0

Assets 2
  • v2.2.0
  • 29737ce
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.2.0
  • 29737ce
  • Compare
    Choose a tag to compare
    Search for a tag

@briri briri released this Jun 19, 2020 · 551 commits to master since this release

Researchers

  • You can now provide Project Start and End Dates on the Project Details tab when editing your DMP. #2409
  • You can now provide information on your Project's collaborators / contributors on the new 'Contributors' tab when editing your project. For example, you can identify more than one PI, project administrators and data curators. #2349 #2408
  • The new 'Contributors' tab provides a typeahead box for organizational affiliation. This box searches the Research Organization Registry (ROR) as you type. #2339
  • Fixed a bug that was sometimes confusing the funder and template names on PDF exports #2419

Organizational Admins

  • You can now make some checkboxes, dropdown lists or radio buttons on your templates trigger conditional logic. For example if a user selects a particular value from a dropdown then logic can be triggered to send an email or hide other questions related to their response. #1772 #2476 #2405 #2451
  • The Usage Statistics page now allows you to filter out test plans and the filters now apply to the same graphs instead of the static plan and user counts (which have been removed) #2158 #2343
  • You can now click on one of the bars in the bar charts on the Usage Dashboard page which will drill into the results.
  • You can now filter the results of the Plans and Users pages by month and year #2450
  • You can now provide us with a Google Analytics code that you can then use to monitor your user's activity within the system. #2344
  • Updated the API to allow you to update your User's departmental affiliations. See the wiki documentation for more details #2235
  • Fixed a bug that prevented you from viewing historical versions of your templates #2509
  • Fixed a bug that was giving new templates the incorrect visibility selection by default. This was preventing published templates from being used. #2518
  • Fixed a bug that was prevent users from creating more than 5 templates #2458
  • Fixed a bug that was preventing you from deleting questions from a published template #2304
  • ORCID and Shibboleth ids now appear on the Users page #2353

Super Admins

  • You can now deactivate a notification #2382
  • You now have the ability to export all plans #2346
  • Added filter by permission level to the Users page #2352

Developers
This release contains many structural DB changes and data transformations to help your system move towards the RDA Common Metadata Standard for DMPs. These changes will make future integrations with external systems easier. Please read the following instructions carefully before proceeding with your upgrade.

Please read through these notes BEFORE deploying this release!

If you are running on a machine that has 2 or fewer CPUs then you will need to modify the upgrade Rake tasks. See Issue 2723

  • All of the Org selection boxes have been updated. The ones on the 'Create account', 'Edit profile', 'New Org', 'Funder selection Project Details' and the new 'Contributors' tab provide a typeahead that queries the list of Orgs in your DB as well as the [Research Organization Registry (ROR) API] (https://ror.org). The results prioritize results from your DB. It also allows the user to enter their own value for scenarios where an Organization does not appear in the ROR API. If the user selects (or enters their own value) in the box, a new Org record is created and the user is associated with the org.
  • The old user_identifiers and org_identifiers tables have been consolidated into the new polymorphic identifiers table. The upgrade script will migrate your existing records into this new table. These legacy tables will be dropped in the next release.
  • Two new Identifier Schemes have been added: Fundref and ROR. When new Orgs are created via the org selection box described above, the ROR and Fundref (if applicable) identifiers are added to the new identifiers table. An upgrade script is provided that will retrieve the ROR and Fundref identifiers for all of your existing Org records.
  • Introduced a 'managed' flag to the Orgs table. This will eventually replace the old 'is_other' flag. A 'managed' org has administrators. New Orgs created in the future by a user's selection of a ROR Org (or entering free text) will be 'unmanaged' by default
  • An upgrade script is supplied that will attempt to match any User's associated with the default is_other Org with a result from the ROR API (using the user's email domain and the org's name stored on the user record). If an appropriate match is found, the org record will be created and the user will be associated with the new org.
  • Introduced the 1st half of the RDA metadata standard for DMP compliant API api/v1/. The API currently only allows for the following: templates#index, plans#index (no filters yet), plans#show and plans#create #2390 (Note that the 2nd half of the API work is scheduled for late summer / early fall .. the draft of the new spec can be found here)
  • Added a new 'Api Clients' section to allow you register clients for the new v1 API. The v1 API uses JSON Web Tokens for security and allows either an Api Client or User to authenticate. Api Clients are meant for communication with external systems. See the API spec linked above for further details

Updates to the Gemfile dependencies

  • We added Httparty to handle communications with external APIs
  • We added JWT to handle auth for the new v1 API
  • We added Capybara-Webmock to ensure that calls are not made to external apis when running tests.

Most gems were upgraded to their latest patch release. The following gems had minor or major version updates:

Dependency from to
Annotate gem 3.0 3.1
Better Errors 2.5 2.7
Brakeman 4.7 4.8
Bullet 6.0 6.1
Bundler Audit 0.6 0.7
Byebug 11.0 11.1
Capybara 3.29 3.32
Database Cleaner 1.7 1.8
Excon 0.71 0.75
FactoryBot & FactoryBot Rails 5.1 5.2
Faraday 0.17 1.0
FFI 1.11 1.13
FOG AWS 3.5 3.6
FOG Core 2.1 2.2
Hashie 3.6 4.1
Launchy 2.4 2.5
Libv8 6.9 7.3
Loofah 2.5 2.6
Lumberjack 1.0 1.2
Method Source 0.9 1.0
Parser 2.6 2.7
Pry 0.12 0.13
MiniProfiler 1.1 2.0
Recaptcha 5.2 5.5
Regex Parser 1.6 1.7
Rollbar 2.22 2.25
Rspec 3.9 4.0
Rubocop 0.77 0.85
Sassc 2.2 2.4
Shoulda 3.6 4.0
Simplecov 0.17 0.18
Thor 0.20 1.0
Unicode Display Width 1.6 1.7
Webmock 3.7 3.8
---------- ----- -----

Updates to the Yarn JS dependencies

  • Added bootstrap-select to support conditional questions feature
  • Most JS files were upgraded to their latest minor or patch release.

Database Changes

  • New table conditions to support conditional questions
  • New table api_clients
  • New contributors table
  • New table identifiers (replaces the user_identifiers and org_identifiers)
  • New table trackers to store org Google Analytics codes
  • Add a orgs.managed flag
  • Added plans.funder_id and plans.org_id (replaces old funder string) relationships
  • Added plans.start_date and plans.end_date
  • Added plans.api_client_id to identify the provenance of plans created via api v1
  • Added a notifications.enabled flag
  • Added a users.last_api_access field
  • Added a identifier_schemes.context bit flag
  • Added question_options.versionable_id
  • Added filtered to the stats tables

Upgrade process
This upgrade involves changes to the database structure (see above). It also requires scripts to be run that will transform your existing data to fit into these new structures. We recommend that you run through the upgrade process in a development or staging environment prior to production. Any cleanup that may need to be done can then be scripted to help speed up the upgrade process in production.

  1. Back up your database!

  2. Update your branding.yml file as follows:

  • Add use_recaptcha: false to the application section. Set the value to 'true' to add a reCAPTCHA to the create account form.
  • Review the config/initializers/external_apis/ files. The DOI one is a placeholder, this functionality will appear in a future release. You can set the open_aire.rb file's active attribute to enable/disable the API typeahead for the 'Grant ID' field on the Project Details page. You can set the ror.rb file's active attribute to enable/disable calls to the ROR API (this will force the new Org selection boxes to only look at your local database ... users may still enter free text into the field to create a new Org record)
  1. Run bundle exec rake db:migrate RAILS_ENV=[env] to make the necessary changes to the DB.

  2. We highly recommend that you run the following scripts in the latest version of v2.2.x! For example, v2.2.1 includes several bug fixes to the v2_0_0_part2 script.

  3. Run the 1st data transformation script that will populate the new question_options.versionable_id field. This step can take over 5 minutes to run depending on the size of your table: bundle exec rake upgrade:v2_1_6 RAILS_ENV=[env]

  4. Run the upgrade:v2_2_0_part1 upgrade script that will add 'fundref' and 'ror' to the 'identifier_schemes' table, populate the 'context' field on the 'identifier_schemes' table, migrate your 'user_identifiers' and 'org_identifiers' into the new 'identifiers' table and search the ROR api and add the 'ror' and 'fundref' ids for your existing orgs into the 'identifiers' table: bundle exec rake upgrade:v2_2_0_part1 RAILS_ENV=[env]

  5. Take a moment to review the output of the upgrade:v2_2_0_part1 script and then open the tmp/ror_fundref_ids.csv file. This file shows a side by side comparison of the Org's name in your DB and the Org's name that was found by the ROR API. In some circumstances you may need to correct the match that was found. For example if you had 'University of Example' in your DB, ROR may have selected 'University of Example Medical School'. Follow the suggested instructions in the upgrade:v2_2_0_part1 script's output to resolve any items that need correction. Some example SQL scripts that may be useful are located at the end of the release notes.

  6. You should also at this point see if there were any Orgs that did not get a ROR identifier. In some circumstances an organization may not appear within the registry. If this is not the case, you can manually add the entry to the table.

  7. Run the upgrade:v2_2_0_part2 upgrade script which will attempt to migrate as many users associated with the is_other Org to new Org records (by searching the ROR API for the email address' domain and the text stored in the 'users.other_organisation' field), convert the old 'data_contact' and 'principal_investigator' fields on the 'plans' table into 'contributors' records, set the 'plans.org_id' field to the plan owner's org_id, lookup the 'plans.funder_name' in the 'orgs' table or ROR api (creating the Org if needed) and setting the 'plans.funder_id', and convert the old 'plans.grant_id' field into an 'identifiers' record. Note that this script can take in excess of 45 minutes to complete depending on the size of your DB.

  8. Review the output from the upgrade:v2_2_0_part2 script and then spot check any new Org records that were created for duplicates. You should prefer the Org with the lowest id value (the original record) when merging since the new Org record will only have 'users' and a 'guidance_group' associated with it.

  9. Note that the old values were left in the 'user_identifiers', 'org_identifiers', 'plans' 'data_contact', 'principal_investigator', 'funder_name' and 'grant_id' fields for reference. These DB entities will be removed in a future release

The following are some useful queries that can be used to manually correct Org changes or add new ones not created during the upgrade process (note: ROR and FundRef identifiers are expected to be URLs so do not forget the URL prefix when making changes manually!):

# Add a new Org and its corresponding ROR and FundRef IDs found while searching https://ror.org
# ------------------------------------------------------------------------------------------------------
INSERT INTO orgs (name, managed, is_other, org_type, created_at, updated_at) 
VALUES ('Institution Name (website.edu)', 1, false, false, CURDATE(), CURDATE());
# ROR:
INSERT INTO identifiers (identifier_scheme_id, identifiable_id, identifiable_type, value, attrs, created_at, updated_at) 
  (SELECT [identifier_scheme_id for "ror"], id, 'Org', 'https://ror.org/[code]', '{}', CURDATE(), CURDATE() FROM orgs WHERE name = 'Institution Name (website.edu)');
# FUNDREF:
INSERT INTO identifiers (identifier_scheme_id, identifiable_id, identifiable_type, value, attrs, created_at, updated_at) 
  (SELECT [identifier_scheme_id for "fund ref"], id, 'Org', 'https://api.crossref.org/funders/[code]', '{}', CURDATE(), CURDATE() FROM orgs WHERE name = 'Institution Name (website.edu)');

# Attach users with a specific email domain to an Org
# ------------------------------------------------------------------------------------------------------
UPDATE users SET org_id = (SELECT id FROM orgs WHERE name = 'Institution Name (website.edu)') 
WHERE id IN (SELECT id FROM users WHERE email LIKE '%@website.edu');

# Remove a duplicate Org created by the upgrade scripts
# ------------------------------------------------------------------------------------------------------
UPDATE users SET org_id = [corret org] WHERE org_id = (SELECT id FROM orgs WHERE name = ‘Institution Name (website.edu)’);
UPDATE plans SET org_id = [correct org] WHERE org_id = (SELECT id FROM orgs WHERE name = ‘Institution Name (website.edu)’);
DELETE FROM guidance_groups WHERE id = (SELECT id FROM orgs WHERE name = ‘Institution Name (website.edu)’);
DELETE FROM orgs WHERE name = ‘Institution Name (website.edu)’;
Assets 2
  • v2.1.7
  • 483569f
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.1.7
  • 483569f
  • Compare
    Choose a tag to compare
    Search for a tag

@briri briri released this Jun 11, 2020 · 769 commits to master since this release

  • Bug fix for Shibboleth logins that were creating an empty record in the user_identifiers table
Assets 2
  • v2.1.6
  • aaa6d98
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.1.6
  • aaa6d98
  • Compare
    Choose a tag to compare
    Search for a tag

@briri briri released this Apr 3, 2020 · 789 commits to master since this release

Upgrade Process

  • Run bundle install to update your rubygems dependancies
  • Run rake assets:precomipile to update your webpack assets and dependancies
  • The content of statistics objects has been restructured, and will need to be re-run for all previous months. Use rake stat:build or rake stat:build_parallel to update these. NOTE: this can take a long time to run if not parallel. See comments below around connection pooling if you hit issues with the parallel tasks

Changes

Researchers

  • The option to create a copy of an existing DMP is now called "Copy". #2418

Org-admins

  • It's now possible to select a comma ,, pipe, |, or hash # characters as your delimiter for CSV exports from the usage dashboard. #2375
  • It's no longer possible to download an overview of tool usage from the usage dashboard. #2345
  • It's possible to download a CSV with statistics on your New Plans, New Users, Downloads, and Plans Shared broken down by month from the usage dashboard. #2345
  • There is an additional accordion on the usage dashboard to show statistics on how your templates are used (by all organisations) #1682
  • Admins from Funder orgs have their usage-dashboard replaced with the statistics on their template usage (detailed above). #1682
  • The CSV export of users now includes the School/Department field. #2213

Bugfixes

  • Headers now follow hierarchical order, fixes an accessibility issue for screen-readers. #1451
  • Org-admins can now view plans shared by users of different organisations. #2415
  • The super-admin list of plans no longer throws an error when a plan's owner does not exist. #2428
  • The 'Opens in a new Window' tool-tip is no longer truncated on links within guidance. #2305
  • tinymce content css no longer fails to load. #2379

Security

  • Update nokogiri to 1.10.8
  • Fix for XSS vulnerability. #2437
  • Update Karma to 4.4.1

Developer Notes

  • Lots of changes to ensure GitHub workflows/tests are working correctly
  • Removed the feedjira Gem as it was un-used by the DMPRoadmap project. If your customization depended on the gem, see the suggested fix by @benjaminfaure in #2411
  • The statistics rake-tasks are now able to be run in parallel to reduce the runtime. Use rake stat:build_parallel and rake stat:build_last_month_parallel. NOTE: there must be as many database connections available to Rails as total threads attempting to make connection, as such, you may need to increase your pool size in config/database.yml. The default in config/database.yml.sample has been changed to 16
  • It's now possible to use js.erb files from the asset-pipeline. See PR #2379 for an example of usage
Assets 2
  • v2.1.5
  • a54f85a
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.1.5
  • a54f85a
  • Compare
    Choose a tag to compare
    Search for a tag

@briri briri released this Feb 14, 2020 · 834 commits to master since this release

Release Notes V2.1.5

Upgrade Process

A few dependencies were updated so you will need to run a bundle install and a yarn install to update your assets

Changes

Researchers

  • When exporting a DMP, the coversheet will separately list the template and funder names #2371
  • Browser-spellcheck is now enabled in all text boxes #2169
  • You can now create a plan from the Funder Requirements or Public DMPs tab #2296
  • Copied plans now behave like normal plans when requesting feedback #2180

Org-admins

Usage Dashboard

  • The plans_by_template chart counts now add up to the monthly plans chart counts. There was a bug where non-customised funder-templates would not be included. #2083
  • Fixed a bug where the 9 and 12 month views of the plans by template chart would sometimes fail to display #2119

API

  • Test-plans are now flagged in the API output of the /api/v0/plans and /api/statistics/plans endpoints #2388
  • Test-plans can now be filtered from the output of the same two endpoints by passing emove_tests=true as a parameter #2388
  • The API now handles empty and invalid dates #2116

Bugfixes

  • Users language no longer defaults to the first language returned by the database upon editing their profile for the first time #2362
  • TinyMCE labels now display properly for screenreaders #1449
  • Users must now accept the Terms and Conditions when signing up to the tool #2341

Security

Gem dependency updates: rack, excon
Yarn dependency updates: tinymce, js-yaml

Assets 2
  • v2.1.4
  • f807b5f
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.1.4
  • f807b5f
  • Compare
    Choose a tag to compare
    Search for a tag

@briri briri released this Dec 5, 2019 · 889 commits to master since this release

General

  • All of the text area fields will now provide spellcheck (browser dependent) #2169
  • We moved the 'Request Feedback' button to its own tab #2234
  • Fixed a bug with the progress bars on the write plan page for plans with multiple phases (e.g. Horizon2020) #2095
  • Updated Português (Brasil) translations #2303
  • Template published date now shows the date the template was published #2199
  • Fixed a bug that was preventing some users from updating their profile #2208
  • Clicking your institution's logo no longer brings you to your institution's website #2173
  • You can now create a plan for a specific public template by clicking on the icon in the public templates page instead of going through the create plan page (you can also copy the link to do this) #2284

Accessibility

  • Links, buttons, table cells and fields now show a visible cue when they have focus #2206, #2230
  • A new 'Opens in a new window' tooltip appears when selecting or hovering over a link that goes to a different site #2211
  • Now providing alternate text as well as tooltips for assistive technologies like screen readers #2222
  • Addressed some issues encountered when using zoomText or Windows Magnifier #2223
  • Fixed some accessibility issues with tables #2253
  • Fixed an issue where radio button labels were not correctly associated with their radio buttons #2273
  • The Guidance and Comments tabs when editing a plan are now accessible by keyboard #2283

PDF Downloads

  • Fixed an issue with long plan title's #2251
  • Fixed an issue with non-latin characters #2249
  • Fixed an issue with the display of some bullet points #2147

Org Admins

  • You can now define departments for your Organization (e.g. 'School of Engineering')
  • Added user's 'department' and their 'number of plans' to the Users table #2266
  • You can now export your own templates #2091
  • Fixed some issues with searching on table #2236
  • Fixed a bug that was causing errors when sorting guidance #2207
  • Fixed a bug when changing a template's visibility (only effected organizations that are both a funder and an organization) #2264

Super Admins

  • You can now merge user accounts on the Admin -> Users page #2245, #2224
  • You can now archive a user account. The account is anonymized so that all personal information for the user is no longer available. Their plans and comments remain. #2224
  • Fixed an issue with updating an organization's shibboleth entityID (only applicable to installations that filter the list of organizations that can use institutional login) #2289

API

  • The full text API is now filterable by user ids, template ids or plan ids #2293

Developers

  • Updated gem and JS dependencies
  • Cleaned up deprecated methods in the Rspec tests #2258
  • Fixed an issue where annotations were being added to removed questions #2216
  • Updated cookie serialization from hybrid to JSON #2256 Note this may invalidate any very old user cookies
  • New branding.yml attribute for the suffix to use when 'anonymizing' a user account. Make sure you update your copy of the branding.yml file (e.g. archived_accounts_email_suffix: '@removed_accounts-dmptool.org')
  • There is a new JS variable called OPENS_IN_A_NEW_WINDOW_TEXT that you should ensure is part of your views/layouts/application.html.erb file (if you have replaced the default with your own)
Assets 2
  • v2.1.3
  • f647e26
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.1.3
  • f647e26
  • Compare
    Choose a tag to compare
    Search for a tag

@xsrust xsrust released this Jul 29, 2019 · 988 commits to master since this release

v2.1.3

Upgrade Process:

  • add the api_max_page_size key to your config/branding.yml, see config/branding.yml.sample
  • run rake upgrade v2_1_3 to:
    • fill blank plan_identifier fields with the ID for the plan
    • add the Reviewer permission to the database
    • Make all org-admins into reviewers
    • Remove the old reviewer Roles
  • Make sure you bundle install and yarn install to get all dependancies up-to-date
  • Run rake db:migrate to add the new table and fields for the departments

Changes:

Researchers

  • Updated date-format in footer of PDF Export to be unambigious
  • Pre-fill the plan's Identifier with it's ID
  • Horison 2020 plan now lets you select your grant-id via a typeahead, pre-filled with active projects
  • Edit-times on comments are now in 'time-ago' instead of displaying in UCT
  • You can now add a school or department to your profile

Org-Admins

  • Reviewer is now an admin permission, you should now have this permission
  • You can now add schools or departments (and set a label for your organisation's sub-divisions) for your users to select & add to their profile
  • To publish, Templates now must have phases; phases, a section; sections a question
  • 'Share Plan' page now viewable for your org's plans

Super-admins

  • 'Share Plan' page now visible
  • Reviewer now a permission, you will see the organisation you are associated with's plans, changing when you change organisation.

Bugfixes

  • RDA Metadata Standards question now working
  • Users with capital letters in their emails can be invited to plans
  • Template export shows error messaging for bad IDs
  • blank answer.text no longer causes csv and text export to throw an error

Security

  • Updated versions for gems and JS dependancies to patch security issues
  • Added gem to patch Omniauth vunlerability CVE-2015-9284
Assets 2
  • v2.1.2
  • a08d751
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.1.2
  • a08d751
  • Compare
    Choose a tag to compare
    Search for a tag

@xsrust xsrust released this Apr 23, 2019 · 1072 commits to master since this release

Upgrade Process

  • Update the text of config/branding.yml to set the following (see #2059):
preferences:
      email:
          users:
              new_comment: false
  • Run rake upgrade:v2_1_2 to add the Date question type
  • Run rake stat:build to update your generated statistics

Changes

Researchers

  • Long links in Guidances now wrap in all browsers #1876
  • Clarified error messaging when updating user profile #1749
  • Improved formatting of Question/Answer in plan downloads #1893
  • Updated Request feedback text to show user/plan name, instead of placeholders #2047
  • Only show Guidance selections on Project Details page when the Plan has applicable Guidance #2020
  • Updated CSV download formatting to include comments and strip text formatting instead of representing line-breaks as semicolons #2058
  • Expand/collapse all links only show on the guidance tab when there are multiple guidances #2049
  • Updated preferences to not notify of new comments by default #2059
  • Comment notification text updated to link-out to plan tab, and list question and section #1872
  • Improved Table Formatting in Example Answers, Questions, Default Answers, Guidance, Answers, and Comments #2071
  • Searches over tables are now case-insensitive #2080

Org-Admins

  • Org-admins cannot become reviewers of their own plans #2009
  • When reviewing a plan, Answers are rendered in HTML, so always display in full #1683
  • Template names in tables are now a link to the template details page #1182
  • Themed guidance displays on all template previews #1209
  • Added missing Date question type #1158
  • Usage Dashboard report now shows the number of plans, grouped by template used (also available via the API) #1679

Accessibility

  • Request feedback confirmation now accessible to screen-readers #1447

Bugfixes

  • UTF no longer breaking PDF footer, solution contributed by @benjaminfaure #73
  • Tables Default sorting is no longer removed by clicking 'View All' or 'View Less' #2027
  • Javascript now compiles to work in IE
Assets 2
You can’t perform that action at this time.