v4.1.8

• Updated all JS and Gem dependencies
• Allow admins who are providing feedback to view the plan's research outputs #520
• Remove the footer from the plan PDFs generated by the system #517

The footer is configurable now in the config/dmproadmap.yml and config/initializers/_dmpraodmap.rb as include_footer_in_pdfs the default is 'false'

v4.1.7

• Added a new error page for SSO errors #501 This will hopefully reduce Helpdesk inquiries
• Added new editorial board members to the website #503
• Removed the UCOP Helpdesk phone number from the contact page since it is no longer valid #509
• Removed Google Analytics tracker code field for institutions since UC has decided not to continue use of GA #504
• Added new related work type of 'Metadata' to the 'Follow up' tab #505
• Fixed a bug that was causing the project start/end date to display the UTC instead of the time specified by the user #506
• Updated all gem and JS dependencies

v4.1.6

• Added 'href' and 'alt' to the allowed attributes the HTML sanitizer will display when rendering template questions and guidance

v4.1.5

UI Changes

• Added the ability for users to change the font size, font color, text alignment in the TinyMCE editors. See app/javascript/utils/tinymce.js.
• Updated the template edit page so that ALL admins will now see the visibility flags. Originally this would only appear in scenarios when the org was a funder and institution/organization. The logic however seems to have been incorrectly setting the template visibility under certain scenarios so there is a need for the user to be able to change it themselves. #474
• Updated the finalize tab so that co-owners see a red 'X' and a note letting them know that only the creator of the plan can register a DMP ID #485
• Added new controller action for creating a plan from the links on the funder requirements page and consolidated logic shared by the new action and the old 'create' action. Fixes bug #488
• Fixed a bug that was causing the org details page to throw a 500 error when the org is a funder and had nil values set for their 'Create plan via api' email subject and body #363
• Fixed an issue that was causing the wrong plan visibility to be shown when the user's role for the plan was not owner or co-owner #483

Removal of Google Analytics

• Removed Google Analytics from the app/views/branded/layouts/_analytics.html.erb and replaced with logic to support Matomo tracking. This requires an account with Matomo and setting up some configuration settings. #490

API Changes

• Fixed a bug that was getting triggered when an API client had more than one redirect URIs defined #472
• Fixed a bug that was returning the plans associated with the API client's user instead of the OAuth2 resource owner's plans when the user has no plans defined. For example if external system A received authorization to access Jane Doe's plans, but Jane has no plans, the API was returning all of system A's owner/user's plans #475

Maintenance

• Updated gem and JS dependencies

v4.1.4

• Fixes an issue where a failure from the uc3-citation gem was forcing the RelatedIdentifier model into an endless loop. #479.
• Updated JS and gem dependencies
• Added users.ui_token in preparation for v5 work. Added the api/v2/me endpoint to fetch the currently logged in user's info which will be used by future React pages. UI token is generated/regenerated when the user logs in and deleted when they log out.

v4.1.3

• patch bug when updating a research output that has no selected repos or standards

v4.1.2-node16.20

• locked @babel/preset-env JS dependency due to asset compilation issue which may be related to the node version running on our hosts. This does not probably impact other installations

v4.1.2

• Update modal search for repositories to allow researchers to define custom repositories that are not a part of the re3data registry #466
• Update modal search for metadata standards to allow researchers and template admins to define custom standards that are not a part of the rda registry
• Refactor custom repository creation for template administrators. Moved functionality into existing modal search window accessed via new 'My repository is not listed' button
• update to api/v2 json to use the correct URL when constructing the link back to the PDF
• Locked better-errors gem to 2.9.1 due to an issue that prevents Rails from starting up unless sassc is installed
• Updated gem and JS dependencies

v4.1.1

• Patch for scenarios where empty custom repositories were being included on form submission in the Preferences tab which was causing the Template.update to fail

v4.1.0

Overview

Note: This version includes a change to the research_outputs table! We have added a new research_outputs.research_output_type field that stores a string value. It is a replacement for the old research_outputs.output_type integer field.

You will need to run: bin/rails db:migrate && bin/rails v4:upgrade_4_1_0 which will:

• Migrate your existing data from the research_outputs.output_type (Integer) field to the new research_outputs.research_ouput_type (String) field.
• Add a new 'OTHER' license to the licenses table. This new license is meant for scenarios where a user's institution or repository provides restricted access to the data the description is 'Custom Data Use Agreements/Terms of Use'. The option will appear for the user by default within the existing License select box
• The enum that backs the Initial Access level of a research Output has changed from 'open (0)', 'embargoed (1)', 'restricted (2)' and 'closed (3)' to: 'unrestricted (0)', 'restricted (2)', 'other (3)'. The script migrates any research outputs that had an initial research_outputs.access level set to 'embargoed' (1) to 'other' (3). The enum was left intact to accommodate the migrations, it will be updated in the next release.

New Functionality

Template administrators now have the ability to enable/disable the 'Research Outputs' tab. If they disable the tab, a researcher will not see the research outputs tab when editing their plan. The new 'Preferences' tab is visible for admins when they edit their template. It also provides additional options to tailor the research outputs tab for their template.

Screenshot of the Preferences tab and the enable/disable checkbox Screenshot of the Output Types preferences. The admin can use the defaults or specify their own (including removing default options) and also provide a tooltip for researchers to help guide their selection process. Screenshot of the Repository preferences showing a scenario where the admin has selected some repositories from the re3data registry and also defined a custom repository. When the researcher adds a research output, these preferred repositories will be displayed by default (they still have the option to select from the full re3data repository list. The admin can also provide a tooltip for researchers to help guide their selection process. Screenshot of the Metadata Standard preferences showing a scenario where the admin indicates that a specific metadata standard is the preferred standard. When the researcher adds a research output, these preferred standards will be displayed by default (they still have the option to select from the full list. The admin can also provide a tooltip for researchers to help guide their selection process. Screenshot of the license preferences. The admin can use the defaults or specify their own (including removing default options) and also provide a tooltip for researchers to help guide their selection process.

Changes

Updated the Admin Template edit page with a new 'Preferences' tab. This new tab allows admins to specify whether or not the Research Outputs tab will be available to the researcher when filling out their plan. If enabled, the admin can specify preferred/recommended output types, licenses, metadata standards and repositories. They can also provide guidance to the research to help them with their selections of those items.

• Added the following columns to the templates table
  • enable_research_outputs
  • user_guidance_output_types
  • user_guidance_repositories
  • user_guidance_metadata_standards
  • user_guidance_licenses
  • customize_output_types
  • customize_repositories
  • customize_metadata_standards
  • customize_licenses
• Updated the Templates model (and RSpec factory and tests) to use new field
• Created the Template Preferences View
• Removed 'Embargoed' from the list of Research Output Type's initial access level and changed the names of the other options. (Left the enum intact on the model for now so that data can be migrated)
• Added a new 'OTHER' license type (does not appear in JSON output because it has no valid URI)
• Added column research_output_type to the research_outputs table
• Added v4:upgrade_4_1_0 rake task to migrate data from output_type and output_type_description to the new research_output_type field. The task also adds a default 'OTHER' license and migrates resource_output.access from embargoed to closed
• Updated the ResearchOutput model (and RSpec factory and tests) to use new field
• Replaced the old output_types enum on the ResearchOutput model with DEFAULT_OUTPUT_TYPES array
• Updated presenters (and RSpec tests) and controller to work with the new field
• Created table template_licenses
  • Created UI to save preferred Licenses for a Template
• Created table template_output_types
  • Created UI to save preferred Output Types for a Template
• Created table template_repositories
  • Customize modal search to populate this relation
• Created table template_metadata_standards
  • Customize modal search to populate this relation
• Modify repositories table to allow for the definition of customized repositories for a template.
  • UI to create customized repositories
  • UI to select customized, preferred and/or standard repositories for a research output.
• Updated Gem and JS dependencies