Feature #13570

Add ability to apply copyright pop-up globally without accompanying Rights statement

Added by Dan Gillean 8 months ago. Updated 7 months ago.

Status:VerifiedStart date:09/29/2021
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Rights
Target version:Release 2.7.0
Google Code Legacy ID: Tested version:
Sponsored:Yes Requires documentation:

Description

In Feature #8771, we added the ability for administrators to configure a customizable copyright pop-up warning that would appear before users are granted access to master digital objects.

This feature requires a number of pre-conditions to work as expected:

  • Global permissions for anonymous users must be set to Grant access to the Master digital object
  • The Permissions settings for copyright must all be set to Grant in Admin > Settings > Permissions
  • A Rights statement must be added to any description where the copyright pop-up should appear, which has a basis of copyright and a Conditional restriction.

These requirements introduce some limitations to the utility of the feature. Namely:

  • It is difficult for existing users with a lot of content to decide later to use the copyright pop-up, as they would need to manually add, at minimum (if using Rights inheritance), dozens if not hundreds of Rights statements
  • Since it relies on the presence of a Rights records with particular conditions and settings, it's easy for human error to introduce exceptions where some digital objects are not covered - either because the permissions are not correct, the Rights statement is forgotten, or the Rights statement is not correct, etc.

This feature enhancement will add a way for an administrator to configure the copyright pop-up to be applied globally to all digital objects associated with an archival description, without requiring an accompanying Rights statement.

Feature description

A new setting will be added to Copyright pop-up section of the Permissions settings, below the existing settings to enable and configure the copyright pop-up, labelled "Apply to all digital objects" (or similar). We'll also add an accompanying tooltip, explaining that "When enabled, the copyright pop-up will be applied to all digital objects, regardless of whether there is an accompanying Rights statement."

History

#1 Updated by Douglas Cerna 8 months ago

  • Status changed from New to QA/Review
  • Assignee changed from Douglas Cerna to Dan Gillean

#2 Updated by Dan Gillean 8 months ago

  • Status changed from QA/Review to Verified
  • Assignee deleted (Dan Gillean)

Works well!

Testing notes, some of which may be added to the documentation:

- The user interface label for "digital object" is being used in the settings labels, so the setting and tooltip text has been changed to singular, so it matches the user interface label setting - e.g. "every digital object" instead of "all digital objects," etc.
- There is no in-browser validation on the settings. However, on save, if the "Enable Copyright pop-up" setting is set to No, but the "Apply to every digital object" is set to yes, then on reload following a save, the second setting ("Apply to every digital object") will default back to No.
- For public users to see the pop-up and be able to continue to the Master, an administrator will still need to change the anonymous group's default permissions so that "View master" is set to Grant
- There are some known issues adding per-description or per-repository permission restrictions that are not a result of this feature - see for example #13345
- Like the previous copyright pop-up functionality, this new setting does NOT cover remote digital objects linked via URI. Only locally uploaded digital objects will trigger the copyright pop-up
- Similarly, this functionality doesn't cover public access to digital objects associated with authority records. See #13419
- When enabled, any user (including administrators) who have access to the master digital object will be redirected to the copyright pop up before being able to access the master

#4 Updated by Dan Gillean 7 months ago

  • Requires documentation deleted (Yes)

Also available in: Atom PDF