Differences

This shows you the differences between two versions of the page.

--- indexing:hierarchies_and_collections [2023/03/22 17:57] – demiankatz
+++ indexing:hierarchies_and_collections [2023/11/28 20:13] (current) – [Hierarchies and Collections] demiankatz
@@ Line 1: / Line 1: @@
 ====== Hierarchies and Collections ======
-// The features described on this page are available starting with VuFind® 1.4. //
 ===== Hierarchies =====
@@ Line 27: / Line 25: @@
   * **is_hierarchy_title** - If the current record represents a node within a hierarchy, this field should contain the same value as the regular title field.
   * **title_in_hierarchy** - Optional, introduced in VuFind® 2.3. If a record needs to have a different display title in different collection contexts, this field should contain a number of titles equal to the number of parent collections and in the same order as the hierarchy_parent_id field.
+This optional field is not required, but can be used to enhance some functionality:
+  * **hierarchy_all_parents_str_mv** - This should contain every parent collection ID -- hierarchy_top_id, hierarchy_parent_id, and any "breadcrumb trail" in between. If populated, starting with VuFind® 10.0, this can be used to improve "deep searching" behavior in the collection view by turning on the search_container_id_field setting in HierarchyDefault.ini. Note that any field name can be used in the configuration, so this name is just a suggestion.
 ==== VuFind® Configuration ====