v1.1.0

• Added roles management using hydra-roles-management. This results in three types of logged-in users (in increasing order of privileges within the app):
  • (no role) -- can currently edit items they own. Although users with no role are currently prevented from using the Upload button, the system would allow transferring items to their ownership.
  • content-admin -- can upload and edit items they own
  • admin -- can also edit content blocks; can also access and manage /roles
• Metadata updates
  • The GW Unit value is now clickable in the item browse view, and links to a faceted search on that value
  • GW Unit is no longer mandatory
  • Updates to the GW Unit list of values
• Content blocks
  • Content block content is now managed in the repo in config/locales/content_blocks. Please reflect any changes to these in the repo.
  • Created a new rake task, gwss:populate_content_blocks to bring the copies in the repo into the app database.
• Google Analytics has been configured in production (no code changes - just configuration)
• Several code cleanup/technical debt items (#126, #137, #140, #145, #160, #163)

Upgrading from v1.0.0 to v1.1.0

General

Gemfile has not changed, so bundle install is not necessary to upgrade an existing v1.0.0 instance to v1.1.0. However, README.md has been updated to recommend using the --without development option when running bundle install.

Roles management

Roles management has been added. To upgrade an existing instance:

• Run the rake task that creates user roles called admin and content-admin:

  % rake gwss:create_roles RAILS_ENV=production
  

• At the rails console, add an initial user to the admin role. Make sure that your admin user
  has logged in at least once.

  % rails c
  > r = Role.find_by_name('admin')
  > r.users << User.find_by_user_key('[email protected]')
  > r.save 
  

• Ask each of the content-admin users to log in to the application at least once, if they have not already. Right now they will have read-only rights.

• Log in as an admin user, and navigate to /roles

• Select the content-admin role, and add each of the users to whom you wish to grant content-admin rights. These users should now be able to upload items and edit the items that they have uploaded (plus items transferred or proxied to them). This would also be an appropriate time to add admins to the admin role.

• Note that removing users from roles through the /roles interface is currently broken, and must be accomplished through the rails console.

Content blocks

• Run the rake task that takes the content of the HTML files in config/locales/content_blocks and populates the associated content blocks. Note that for an existing instance, running this rake task will overwrite any changes you've made to the content blocks!

  % rake gwss:populate_content_blocks RAILS_ENV=production
  

Diff of v1.0.0 vs. v1.1.0 code

v1.0.0...v1.1.0