@vyruss vyruss released this Mar 13, 2018 · 736 commits to master since this release

Assets 2

We’re delighted to announce that the DMPTool and DMPonline sites are both now running from the new joint DMPRoadmap codebase. We pushed the MVP out to test last month and have now migrated our production services. There are lots of exciting new features, including:

  • A usage dashboard lets organisational administrators generate statistics for the number of users and plans for given date ranges. Admins can also download a csv to manipulate raw usage data for their organisation further.
  • Organisational administrators can see all the plans for their institution and download metadata on these.
  • Users can request feedback on DMPs if affiliated with an organisation that opts to enable this feature.
  • Administrators are alerted to requests and can make comments alongside each question.
  • Users can turn guidance on/off at any stage, and display guidance from multiple institutions at once.
  • Users can set language preferences, configure email notification settings and link their account with their ORCID ID on their profile.
  • UK users benefit from plan visibility settings, public DMPs and public templates as features from the DMPTool.
  • US users benefit from the ability to customise funder templates (add sections and guidance or example answers) and themed guidance to map one set of institutional guidance across all templates.

Developer notes:

  • Moved asset management from the Rails' asset pipeline over to NPM and WebPack. All assets are stored in lib/assets and you will need to run Webpack to compile and package these resources (See the installation guide for more details). The Rails asset pipeline is disabled in the config/environments/[environment].rb so be sure to update any local environment files for your installation!
  • Upgraded all JS files to ES6 and introduced a linter to help ensure code consistency and quality
  • Upgrade to Bootstrap 3.3 and a complete rewrite of all stylesheets
  • Started using Rails concerns where appropriate (e.g. Paginable, ExportablePlan, etc.)
  • Made the following database changes:
    • templates.visibility allows Orgs that are both funder and organisation/institution to specify whether their template is an external funder template or for internal use (drives the template selection on the create plan page)
    • plans.visibility allows a user to share their plan with other members of their organization, with the public, identify the plan as a test or keep it private (default - configurable in application.rb)
    • orgs.links and template.links a configurable number of links that admins can supply for Orgs and Templates (funders only). Org links appear in the institutional branding header and template links appear as sample plans or funder links on the new public facing funder requirements page
    • plans.complete a new flag that gets set to true when at least 50% (configurable in application.rb) of the plans questions have been answered. This drives whether or not the plan's visibility can be changed and is also factored into usage statistics
    • users.prefs and the prefs table were added to allow for users to set their email notification preferences
    • A new :reviewer role type and the following fields were added to allow for the new 'request feedback' feature: orgs.feedback_enabled, orgs.feedback_email_subject, orgs.feedback_email_msg and plans.feedback_requested
    • org_identifiers table was added to allow for you to manage a customized list of orgs that have shibboleth enabled (table is used to store the Org's shib entity_id)
    • roles.active added to allow users to 'remove' a plan from their list but not actually delete the plan
    • New columns added to the plans table: principal_investigator_email, principal_investigator_phone, data_contact_email and plans.data_contact_phone
    • orgs.contact_name added and displays in the UI instead of the contact email
    • Numerous indexes were created to help improve query efficiency