About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
configuration:blender

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
configuration:blender [2022/04/22 15:12] – [Basic Configuration] emaijalaconfiguration:blender [2022/04/24 12:11] – [Mappings Configuration] demiankatz
Line 36: Line 36:
 The actual configuration is done with two files: [[.files:Blender.ini]] and [[.files:BlenderMappings.yaml]]. Blender.ini contains settings for configuring the search similarly to other backends. BlenderMappings contains all the mappings from backends to common values for facets, search type mappings and sort options. The actual configuration is done with two files: [[.files:Blender.ini]] and [[.files:BlenderMappings.yaml]]. Blender.ini contains settings for configuring the search similarly to other backends. BlenderMappings contains all the mappings from backends to common values for facets, search type mappings and sort options.
  
-It is recommended to choose one backend as the "primary" one and use its facet values etc. as the target to which all the other backends are mapped to. This makes configuration easier. However, there's nothing preventing from using a Blender-specific set of facets that all backends map to, if desired.+It is recommended to choose one backend as the "primary" one and use its facet values etc. as the target to which all the other backends are mapped to. This makes configuration easier. However, there's nothing preventing the use of a Blender-specific set of facets that all backends map to, if desired.
  
 ==== Basic Configuration ==== ==== Basic Configuration ====
Line 57: Line 57:
 There are several noteworthy features particularly with facet mappings: There are several noteworthy features particularly with facet mappings:
  
-  * Facet mappings also work the other and define how active filters are mapped to each backend. You can also define fields that are only used e.g. with checkbox filters.+  * Facet mappings also work the other direction and define how active filters are mapped to each backend. You can also define fields that are only used e.g. with checkbox filters.
   * If a backend does not support a filter value, that backend gets automatically disabled. If you wish to keep the backend active and just ignore such values, list the values under the ''Ignore'' setting.   * If a backend does not support a filter value, that backend gets automatically disabled. If you wish to keep the backend active and just ignore such values, list the values under the ''Ignore'' setting.
   * If you're mapping a value to a hierarchical facet (those can be used with Solr), you can set ''Hierarchical: true'' to indicate that. In such case Blender will automatically populate any upper levels as well. Example:   * If you're mapping a value to a hierarchical facet (those can be used with Solr), you can set ''Hierarchical: true'' to indicate that. In such case Blender will automatically populate any upper levels as well. Example:
configuration/blender.txt · Last modified: 2023/11/01 10:55 by demiankatz