We'd like a visibility feature added to collections that allows some to be hidden from catalog search when the feature is selected. Basically, we want to use parent-child relationships between collections, where all the collection pages are publicly visible, but only the parent collection is returned in the catalog search. This would function like how parent works show after the UV splits child works (which are hidden). We want the visibility feature to be optional, NOT applied to ALL subcollections, because we have some use cases where parent collections are an organizing container for a set of thematically related subcollections that do stand on their own.
This is a ticket for future development work.
We'd like a visibility feature added to collections that allows some to be hidden from catalog search when the feature is selected. Basically, we want to use parent-child relationships between collections, where all the collection pages are publicly visible, but only the parent collection is returned in the catalog search. This would function like how parent works show after the UV splits child works (which are hidden). We want the visibility feature to be optional, NOT applied to ALL subcollections, because we have some use cases where parent collections are an organizing container for a set of thematically related subcollections that do stand on their own.
Example of a catalog search where subcollections are showing after a search for a term that didn't bring the parent collection to the top: https://adl.b2.adventistdigitallibrary.org/catalog?utf8=%E2%9C%93&search_field=all_fields&q=dykes+collection
Parent collection shows as result 8 in the catalog search: https://adl.b2.adventistdigitallibrary.org/collections/0ed83a24-3553-48bf-8216-eca875cbc48b