Hi Jessica,
What you're asking for would technically be possible, but I believe it would require some development to implement.
We don't have a way in Elasticsearch (the search index that AtoM uses to manage these queries) to determine if a record's repository relation is direct or inherited from a higher level. We *do* have such a filter for creators, so there would be something for a developer to model such a filter against, but as of right now, you can either use it as is, or you can show all levels of description. This latter option would show you the dispersed records in the hierarchies of other repositories, but it would also make every level of description associated with your repository (included where the repository is inherited) show in the holdings widget.
I will show you how to do that, at least - I know it's not quite what you are hoping for, but perhaps it might be of use.
First, the easy part - you are using the
institutional scoping, I see. When institutional scoping is enabled, then the menus (such as the "Browse our collection" drop-down menu that appears) are customizable.
Go to Admin > Menus, and find the browseInformationObjectsInstitution menu, near the very bottom of the page. Click on it to enter edit mode. To make this link show all levels of description, we can simply add the following parameter to the end of the Path:
Now when you use the institutional browse menu, it will take you to the description browse page without engaging the top-level filter.
The holdings menu itself is trickier - apparently it is hard-coded to only return top-level descriptions at the moment, which is why you are not seeing the description you want currently.
If you wanted to make it show all levels, then a developer or system administrator could simply comment out line #79 in apps/qubit/modules/repository/actions/holdingsAction.class.php
You can comment out the line by simply adding two forward slashes before the beginning of it, like so:
This line is basically saying that one of the parameters is that the parent ID of the descriptions returned should be the root ID of AtoM - i.e. not another description; so a top-level description. If you comment this line out (and don't forget to clear the cache, restart services, and repopulate the search index after as well), then the holdings menu will show all levels of description associated with the current repository.
An easier, long-term solution, would be to update the holdings list so that by default it shows any descriptions directly linked to a repository (rather than inherited), instead of hard-coding in the top-level record requirement. For users who are correctly taking advantage of repository inheritance (i.e. not unecessarily linking the repository at lower levels when the repo name would be inherited anyway), this would make no changes. For those not properly using inheritance, this might help them identify issues - if fixed, they might even see minor performance improvements. Ideally, if we were to make such a change, we would also develop a command-line task that can check for redundant repository associations (i.e. where the direct repository link at a lower level is identical to the repository link in a parent level, where inheritance would have gotten them the same result) and fix them, similar to the creator unlinker task we developed:
To capture this thought for the future, I've created a Wish list ticket for the holdings widget, here:
If your institution might be interested in sponsoring this work, please feel free to contact me off-list and Artefactual can prepare a development estimate.
In the meantime, I hope this helps somewhat!