Differences

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

--- configuration:blender [2022/04/22 15:11] – created emaijala
+++ configuration: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.
-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 ====
-  - Copy ''config/vufind/Blender.ini'' to ''local/config/vufind/Blender.ini'' for modification.
+  - Copy config/vufind/Blender.ini to local/config/vufind/Blender.ini for modification.
   - Enable desired backends in [Backends] section.
   - Use the [Blending] section, if desired, to configure the selection of initial results. You can also define the block size used for records from each source. Block size can also be relative to the total number of results.
@@ Line 51: / Line 51: @@
 This is expected to be the most laborsome part of the configuration.
-  - Copy ''config/vufind/BlenderMappings.yaml'' to ''local/config/vufind/BlenderMappings.yaml'' for modification.
+  - Copy config/vufind/BlenderMappings.yaml to local/config/vufind/BlenderMappings.yaml for modification.
   - See the beginning of the file for information on the format and available settings.
   - Set up all mappings according to your needs. The sample file contains example mappings for several facets, including mappings to a hierarchical format facet.
@@ Line 57: / Line 57: @@
 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 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: