Feature #13555

Feature enhancement: make the behavior of the institutional scoping more consistent and widely supported

Added by Dan Gillean 2 months ago. Updated 2 months ago.

Status:NewStart date:08/12/2021
Priority:MediumDue date:
Assignee:-% Done:


Target version:-
Google Code Legacy ID: Tested version:2.6, 2.7
Sponsored:No Requires documentation:No


In issue #10733, we added a new feature called "Institutional scoping." When enabled via Admin > Settings > Global, It adds a dedicated repository search box and customizable browse menu per repository on the following pages:

  1. Any repository view page
  2. Any description search/browse results page that includes a repository filter/facet
  3. Any description view page if the user arrives there from a repository-scoped search or the repository view page's Holdings menu

There are two areas where this feature could be enhanced to improve the user experience - first in how scoping is applied to description view pages, and also in how it is applied to authority records.

Description view pages and scoping

This third point in the list above (re: description view pages) leads to an inconsistent user experience - it's possible to see the institutional scoping in some cases but not others, depending on how you have navigated.

At first this seems like a regression, but it turns out this is currently how the feature is implemented, as per a note in the related documentation:

Finally, the institution block will also appear on the view page of a related archival description, but only if the description is arrived at via one of the scoped elements - i.e. the holdings list on the repository view page, or from a scoped search or browse page. If a user arrives at the archival description via a global search or browse page, the institution block will not appear.

See: https://www.accesstomemory.org/docs/latest/user-manual/administer/settings/#enable-institutional-scoping

This feature should be enhanced for a more consistent end user experience so that arriving on any description page that is linked to a repository will display the institutional block if scoping is enabled.

Authority record view pages and scoping

In issue #8642, we added the ability to directly associate an authority record with an archival institution as its maintainer. Now that this exists, we should also consider enabling institutional scoping when viewing authority records that have a maintainer link.


#1 Updated by Dan Gillean 2 months ago

  • Tracker changed from Bug to Feature
  • Subject changed from Regression: Institutional scoping no longer displaying on first load as expected to Feature enhancement: make the behavior of the institutional scoping more consistent and widely supported
  • Description updated (diff)
  • Target version deleted (Release 2.7.0)

Originally filed as a regression, it turns out this is how the feature was designed. Consequently, I've renamed the ticket, updated the description as a feature request, and moved it to the Wishlist.

Also available in: Atom PDF