refs #22384 [finc] updated config files with vufind stock configuration files

local/config/vufind/DAIA.ini

@@ -14,6 +14,12 @@
 ; daiaResponseFormat = json
 ;
 
+; This section contains settings applying to DAIA and its deriving classes such as
+; PAIA.
+;[General]
+; Set the time to live (ttl) for cached data (default is 30 seconds).
+;cacheLifetime = 90
+
 [DAIA]
 ; The base URL for the DAIA webservice.
 ;baseUrl            = http://localhost/daialibero/daia/
@@ -50,3 +56,18 @@ daiaContentTypes['xml'] = "application/xml"
 ; (separate multiple values by commas, for example:
 ; daiaContentTypes['json'] = "application/json, application/javascript"
 daiaContentTypes['json'] = "application/json"
+
+; Enable caching for DAIA items (default is false).
+;daiaCache = false
+
+; DAIA does not support placing holds (this functionality is covered by PAIA) but is
+; able to provide a link to the OPAC to perform such an action. Regarding placing
+; holds/recalls such link is usually given as href for an unavailable service.
+; Uncomment the below section Holds with the setting 'function' to show a link to
+; the OPAC (if it was provided in the DAIA response) instead of a VuFind
+; Holds-Button.
+; If PAIA is used in combination with the DAIA driver, handling holds etc. should be
+; left to the logic in the PAIA driver - thus keep this section commented out if you
+; are using PAIA as well.
+; [Holds]
+; function = getHoldLink

local/config/vufind/RecordTabs.ini

-;####################################################################
-;##################### DO NOT DELETE THIS HEADER ####################
-;################### Leipzig University Library © 2022 ##############
-;
-; This is the ISIL-instance-specific default INI-file and inherits
-; all the settings from the INI-file defined in [Parent_Config] which
-; points to the default INI-file located in the folder vufind2/local
-;
-
-[Parent_Config]
-relative_path = ../../../config/vufind/RecordTabs.ini
-
 ; This file controls the display of tabs on the Record page for various types of
 ; records. Each section name matches a record driver class name, and those settings
 ; will be used when displaying that type of record. If no settings are found for a

local/config/vufind/export.ini

@@ -25,11 +25,19 @@
 ;             {config...} setting above, except result will be URL-encoded.
 ; requiredMethods[] - a repeatable field indicating methods which must be available
 ;     on the record driver object in order to allow export in this format.
-; bulkExportType - [ "link" | "download" ] - link renders a download link in the UI,
-;     download offers to save the export-file directly; overrides the defaultType
-;     setting found in the [BulkExport] section of config.ini. This distinction
-;     currently only affects users with Javascript enabled; the 'download' option
-;     cannot be implemented in a user-friendly way when Javascript is disabled.
+; bulkExportType - [ "link" | "download" | "post" ] - link renders a download link in
+;     the UI, download offers to save the export-file directly, post sends the
+;     metadata using the POST method in a form field named by the postField
+;     parameter; overrides the defaultType setting found in the [BulkExport] section
+;     of config.ini. This distinction currently only affects users with Javascript
+;     enabled; the 'download' option cannot be implemented in a user-friendly way
+;     when Javascript is disabled.
+; postField
+;     Name of the POST field to use when sending records with the POST method.
+; targetWindow
+;     Name of the window where the export is opened in the browser. Default is
+;     "{format}Main" (e.g. "RefWorksMain"), but could be set to e.g. "_blank" to
+;     make the export always open a new window.
 
 [EndNote]
 label = "EndNote"
@@ -61,8 +69,9 @@ headers[] = "Content-type: application/x-research-info-systems; charset=utf-8"
 
 ;[RefWorks]
 ;requiredMethods[] = getTitle
-;redirectUrl = "{config|RefWorks|url|http://www.refworks.com}/express/expressimport.asp?vendor={encodedConfig|RefWorks|vendor|VuFind}&filter=RefWorks%20Tagged%20Format&url={encodedCallback}"
-;headers[] = "Content-type: text/plain; charset=utf-8"
+;redirectUrl = "{config|RefWorks|url|https://www.refworks.com}/express/expressimport.asp?vendor={encodedConfig|RefWorks|vendor|VuFind}&filter=RefWorks%20Tagged%20Format&encoding=65001"
+;bulkExportType = post
+;postField = ImportData
 
 ;[EndNoteWeb]
 ;requiredMethods[] = getTitle

local/config/vufind/facets.ini

@@ -30,7 +30,34 @@ publishDateSort    = "adv_search_year"
 ; recommendations module is used.  See the [TopRecommendations] section of
 ; searches.ini for more details.
 [ResultsTop]
-; topic_facet        = "Suggested Topics"
+;topic_facet        = "Suggested Topics"
+
+; This section controls where facet labels are retrieved from when facets are not
+; explicitly configured.
+[FacetLabels]
+; This setting lists configuration sections containing facet field => label
+; mappings. Later values will override earlier values. These mappings will be used
+; only when a label is not explicitly configured (i.e. through SideFacets settings).
+; If you customize your facet display, be sure to add any new facet configuration
+; sections to this list to ensure proper display in search history, etc.
+labelSections[] = Advanced
+labelSections[] = HomePage
+labelSections[] = ResultsTop
+labelSections[] = Results
+labelSections[] = ExtraFacetLabels
+
+; This setting lists configuration settings defining checkbox facets. If you use
+; a custom section to configure additional facets, be sure to add it to this list
+; so labels display correctly in history, the advanced search editor, etc. If you
+; are using the reverse label => filter format rather than filter => label, you
+; should prefix the section name with a ~ character to ensure proper loading.
+checkboxSections[] = CheckboxFacets
+
+; This section is used to specify labels for facets that may be applied by parts
+; of VuFind other than the facet lists defined in this file (for example, the
+; hierarchical browse of the BrowseController, or the Geographic Search).
+[ExtraFacetLabels]
+long_lat = "Geographic Search"
 
 ; This section is used to identify facets for special treatment by the SideFacets
 ; recommendations module.
@@ -50,14 +77,29 @@ dateRange[] = publishDateSort
 ; (see https://wiki.apache.org/solr/HierarchicalFaceting but note that we always
 ; use a trailing slash to avoid ambiguities)
 ;hierarchical[] = building
-; Sort options for hierarchical facets:
-; How hierarchical facets are sorted. Default is result count, but alternative ways
-; can be specified:
+
+; General sort options for hierarchical facets (Home page, Advanced Search and
+; SideFacets).
+;
+; You can set a general default setting with * and set field-specific overrides
+; using field names (see example below).
+;
+; Available options:
 ; top = Sort the top level list alphabetically, others by result count (useful e.g.
 ;       for a large number of building facets where top level is organization and
 ;       second level the library branch)
 ; all = Sort all levels alphabetically
+; count = Sort all levels by count
+;
+; Note: this section may be overridden for HomePage and Advanced search facets (see
+; hierarchicalFacetSortOptions in HomePage_Settings and Advanced_Settings below).
+;
+; By default, if no settings are configured in this file, the default sort will be
+; 'count' for SideFacets values, 'all' for HomePage values, and 'top' for Advanced
+; values.
+;hierarchicalFacetSortOptions[*] = all
 ;hierarchicalFacetSortOptions[building] = top
+
 ; How hierarchical facet values are displayed in the records:
 ; single = Display only the deepest level (default)
 ; full   = Display full hierarchy for each entry
@@ -75,8 +117,22 @@ dateRange[] = publishDateSort
 ; Leave the section empty if you do not need checkbox facets.
 [CheckboxFacets]
 ;edition:1st* = "First Edition"     ; Contrived hypothetical example
-;access_facet:Local Holdings = "Local Holdings"
-;access_facet:Electronic Resources = "Electronic Resources"
+
+; Available sort options when listing all facets from Sidefacets.
+;
+; Each configuration option targets a search class and a facet field.
+; All facet fields for a search class can be targeted using the wildcard '*'.
+; Sort options are given as a comma-separated list of "<sort-field>=<label>" entries,
+; where <sort-field> is either 'count' or 'index' and <label> the translation
+; key for the option.
+[AvailableFacetSortOptions]
+; By default all Solr facets can be sorted by count and alphabetically.
+
+; Example: sort Solr author_facet by count only.
+; Solr[author_facet] = "count=sort_count"
+
+; Example: sort Solr author_facet only alphabetically
+; Solr[author_facet] = "index=sort_alphabetic"
 
 ; These settings affect the way the [Results] facets are displayed
 ; If using facets at the top of search results you have more room for text.
@@ -85,18 +141,21 @@ dateRange[] = publishDateSort
 facet_limit = 30
 ; Override facet_limit on a per-field basis using this array:
 ;facet_limit_by_field[format] = 50
+
 ; By default, the side facets will only show 6 facets and then the "show more"
 ; button. This can get configured with the showMore settings.
 ; You can use the * to set a new default setting.
 showMore[*] = 6
 ; Or you can set a facet specific value by using the facet name as index.
 ;showMore['format'] = 10
+
 ; Show more facets in a lightbox (paginated, no limit)
 ; If false, facets expand in side bar to show facets up to the above limit
 ; If "more", facets expand and offer an option at the bottom to open the lightbox
 ; If true, facets immediately open in the lightbox
 showMoreInLightbox[*] = false
 ;lightboxLimit = 50 ; page size for the lightbox
+
 ; Rows and columns for table used by top facets
 ;top_rows = 2
 ;top_cols = 3
@@ -170,8 +229,8 @@ special_facets   = "daterange"
 ; translated facets, be sure that all of the necessary strings are included in the
 ; language files found in the languages directory. You may add a colon and the
 ; name of a text domain after the field name to specify translations in a specific
-; text domain (subdirectory of the languages folder). By default, no facets are
-; translated -- uncomment or add lines below to turn on this feature.
+; text domain (subdirectory of the languages folder). If you comment out the lines
+; below, no facets will be translated.
 ;translated_facets[] = institution
 ;translated_facets[] = building
 translated_facets[] = format
@@ -192,15 +251,21 @@ translated_facets[] = mega_collection
 ;delimited_facets[] = author_id_str
 ;delimited_facets[] = "author_id_str|:::"
 
-; These facets will be displayed on the Home Page.  If this section is omitted,
-; the [Advanced] section will be used instead.
+; Sort overrides for Advanced search hierarchical facets. See the comments
+; above the SpecialFacets > hierarchicalFacetSortOptions setting for details.
+;hierarchicalFacetSortOptions[*] = all
+;hierarchicalFacetSortOptions[building] = top
+
+; These facets will be displayed on the Home Page when FacetList is turned on in
+; the content setting of the [HomePage] section of searches.ini. If this section
+; is omitted, the [Advanced] section will be used instead.
 [HomePage]
 ;callnumber-first = "Call Number"
 language         = Language
 format           = Format
 ;hierarchy_top_title   = Collections
 
-; These settings affect the way the [HomePage] facets are displayed
+; These settings affect the way the [HomePage] facets are displayed.
 ; NOTE: To make changes take effect immediately, you may need to clear VuFind's
 ; cache after changing this section.
 [HomePage_Settings]
@@ -208,6 +273,11 @@ format           = Format
 ; of the homepage facet lists, we may not display all loaded values for every facet
 facet_limit      = 20
 
+; Sort overrides for HomePage search hierarchical facets. See the comments
+; above the SpecialFacets > hierarchicalFacetSortOptions setting for details.
+;hierarchicalFacetSortOptions[*] = all
+;hierarchicalFacetSortOptions[building] = top
+
 [Visual_Settings]
 ; Which two facetable fields should be used for creating the visual results?
 ; See VisualFacets recommendation module in searches.ini for more details.

local/config/vufind/permissionBehavior.ini

-;####################################################################
-;##################### DO NOT DELETE THIS HEADER ####################
-;################### Leipzig University Library © 2019 ##############
+; This file controls how denied permissions are treated within VuFind.
 ;
-; This is the ISIL-instance-specific default INI-file and inherits
-; all the settings from the INI-file defined in [Parent_Config] which
-; points to the default INI-file located in the folder vufind2/local
+; The permissions need to be set in permissions.ini.
+; In this file you can configure what should happen if a permission is denied.
+; Please use the permission names from permissions.ini as section names here.
 ;
-
-[Parent_Config]
-relative_path = ../../../config/vufind/permissionBehavior.ini
-
-; A comma-separated list of config sections from the parent which should be
-; completely overwritten by the equivalent sections in this configuration;
-; any sections not listed here will be merged on a section-by-section basis.
-;override_full_sections = ""
-
+; Example:
+;
+; This role from permissions.ini:
+;
+; [default.EITModule]
+; role = loggedin
+; permission = access.EITModule
+;
+; should be configured here in section:
+;
+; [access.EITModule]
+;
+; See permissions.ini for more permissions that you may also wish to configure here.
+;
+; Within each section, there are two options which can be configured:
 ;
-;       Add instance-specific customization after this header.
+; deniedTemplateBehavior: The behavior to apply when a permission is denied
+; dynamically within a template; i.e. the user has access to a page but is blocked
+; from a particular feature of that page. If undefined, the default behavior is
+; to hide the affected functionality and display no special message.
 ;
-;##################### DO NOT DELETE THIS HEADER ####################
-;####################################################################
+; deniedControllerBehavior: The behavior to apply when a permission is denied at the
+; controller level; i.e. the user is totally blocked from accessing something. If
+; undefined, the default behavior defined by the controller (usually promptLogin)
+; will be applied.
+;
+; Each of these options may be set to one of the following options; most options
+; also receive a colon-delimited list of parameters.
+;
+; exception - Throw the specified exception class (param 1) with the specified
+;     exception message (param 2).
+;     This option is ONLY supported by deniedControllerBehavior.
+;     example: deniedControllerBehavior = exception:MyExceptionClass:Access Denied.
+;
+; promptLogin - Redirect the user to the login page. You can optionally set the
+;     first parameter to a message to display on the login page (omit for default).
+;     This option is ONLY supported by deniedControllerBehavior.
+;     example: deniedControllerBehavior = promptLogin
+;
+; showMessage - Display the message (the first parameter) to the user; this text
+;     will be run through the translator. When used as the deniedControllerBehavior,
+;     the message will be displayed in the form of a flash message on the
+;     "permission denied" screen. When used as the deniedTemplateBehavior, the text
+;     will be displayed in place of the blocked markup.
+;     example: deniedControllerBehavior = showMessage:Blocked!
+;
+; showTemplate - Render a specific template, specified as the first parameter.
+;     This option is ONLY supported by deniedTemplateBehavior.
+;     example: deniedTemplateBehavior = showTemplate:error/denied
 
+; Section for global parameters
 [global]
-defaultDeniedTemplateBehavior = true
\ No newline at end of file
+; The default behavior will get used if a permission is denied, but the controller
+; in question defines no default behavior and no permission denied behavior has been
+; configured in this file for the relevant permission.
+defaultDeniedControllerBehavior = "promptLogin"
+
+; The default behavior will get used if a permission is denied, but no permission
+; denied behavior has been configured in this file for the relevant permission.
+; (False means "use the default behavior defined by the template").
+defaultDeniedTemplateBehavior = true
+
+; This setting can be used to override access permissions for controllers. You can
+; set a controller class name inside the brackets to explicitly override that
+; controller's access permission (and that of any of its children, unless more
+; specific permissions are set for those subclasses), whether or not it has a
+; default defined in the class. You can use * inside the brackets to set a default
+; access permission that is applied to all controllers that do not have an
+; internally-defined default (the MyResearchController is also excluded from
+; this setting to avoid infinite login redirects). This can be useful if you
+; wish to password-protect your entire site.
+;controllerAccess[*] = access.VuFindInterface
+;controllerAccess[VuFind\Controller\SearchController] = access.SearchResults
+
+; Example configuration for non-standard favorites permission behavior:
+;[feature.Favorites]
+;deniedTemplateBehavior = "showMessage:Login for Favorites"
+; Note that VuFind loads the MyResearch/Favorites action by default, so be
+; careful about blocking this at the controller level. If you conditionally
+; block this for some users, you should change the defaultAccountPage in
+; config.ini to avoid causing login problems.
+;deniedControllerBehavior = "exception::You are not logged in!"

local/config/vufind/permissions.ini

@@ -45,6 +45,9 @@
 ;               rule that checks an attribute.
 ; username    - Grant the permission to logged-in users whose usernames match the
 ;               specified value(s). Accepts a string or an array.
+; user        - Grant the permissions to logged in users whose user attribute match
+;               the given regular expression pattern. For valid pattern syntax see
+;               http://php.net/manual/de/reference.pcre.pattern.syntax.php.
 ;
 ; Example configuration (grants the "sample.permission" permission to users named
 ; admin1 or admin2, or anyone coming from the IP addresses 1.2.3.4 or 1.2.3.5):
@@ -57,15 +60,22 @@
 ; ipRange[] = "1.2.3.4"
 ; ipRange[] = "1.2.3.7-1.2.5.254"
 ; permission = sample.permission
-;
+
+; Example configuration (grants the "sample.permission" permission to users
+; who are from myCollege or who is a studentmajor (.*studentmajor.*):
+; user[] = "college myCollege"
+; user[] = "major .*studentmajor.*"
+
 ; List of permissions that you may wish to configure:
 ;
 ; access.AdminModule - Controls access to the admin panel (if enabled in config.ini)
 ; access.DebugMode - Allows ?debug=true GET parameter to turn on debug mode
 ; access.EDSExtendedResults - Controls visibility of protected EDS results
 ; access.EITModule - Controls access to the EBSCO EIT module (if active)
+; access.PrimoModule - Controls access to ALL Primo content
 ; access.StaffViewTab - Controls access to the staff view tab in record mode
 ; access.SummonExtendedResults - Controls visibility of protected Summon results
+; feature.Favorites - Controls access to the "save favorites" feature
 
 ; Configuration for permitting EBL/Schweitzer link resolving
 ;[default.EBL]
@@ -97,6 +107,11 @@ role[] = guest
 role[] = loggedin
 permission = access.StaffViewTab
 
+[feature.Favorites]
+role[] = loggedin
+role[] = guest
+permission = feature.Favorites
+
 ; Example for dynamic debug mode
 ;[default.DebugMode]
 ;username[] = admin
@@ -143,7 +158,31 @@ permission = access.StaffViewTab
 ;role = loggedin ; if you want to allow authenticated users to use Primo module
 ;permission = primoOnCampus.MYINSTITUTION
 
-[feature.Favorites]
-role[] = loggedin
-role[] = guest
-permission = feature.Favorites
\ No newline at end of file
+; Example Shibboleth logout API access permission.
+; See https://vufind.org/wiki/configuration:shibboleth for more information.
+;[api.ShibbolethLogoutNotification]
+;permission = access.api.ShibbolethLogoutNotification
+;require = ANY
+;ipRange[] = '127.0.0.1'
+;ipRange[] = '::1'
+
+; Example EZproxy authorization permission.
+; See https://vufind.org/wiki/configuration:ezproxy for more information.
+[ezproxy.authorized]
+permission = ezproxy.authorized
+role = loggedin
+
+; Search and Record API permissions.
+;[api.SearchAndRecord]
+;permission[] = access.api.Search
+;permission[] = access.api.Record
+;require = ANY
+;ipRange[] = '127.0.0.1'
+;ipRange[] = '::1'
+
+; Example permission for Alma webbooks
+;[alma.Webhooks]
+;permission[] = "access.alma.webhook.user"
+;permission[] = "access.alma.webhook.challenge"
+;require = ALL
+;ipRange[] = "127.0.0.1"

local/config/vufind/searches.ini

@@ -21,8 +21,10 @@ default_view         = list
 ; sets the default number of results per page. limit_options is a comma-separated
 ; list of numbers to be presented to the end-user. If only one limit is required,
 ; set default_limit and leave limit_options commented out.
-; WARNING: using large limits may require you to raise your PHP memory limits to
-; avoid errors.
+; WARNING: using large limits may cause problems due to a variety of limitations,
+; especially if you support bulk operations (which can cause large URLs/requests).
+; If you must support large page sizes, you may need to raise the PHP memory_limit
+; and max_input_vars settings and/or adjust the Apache LimitRequestLine setting.
 default_limit        = 20
 limit_options        = 10,20,40,60
 
@@ -51,10 +53,15 @@ case_sensitive_ranges = true
 ; [NoResultsRecommendations] sections below.
 ; See the comments above those sections for details on legal settings.  You may
 ; repeat these lines to load multiple recommendations.
+;default_top_recommend[] = MapSelection ; see [MapSelection] in geofeatures.ini.
 default_top_recommend[] = TopFacets:ResultsTop
 ;default_top_recommend[] = SpellingSuggestions
 ;default_top_recommend[] = VisualFacets:Visual_Settings
 default_side_recommend[] = SideFacets:Results:CheckboxFacets
+; SideFacetsDeferred is an alternative to SideFacets. Using it will defer loading of
+; any facet until it's actually displayed. This can improve search performance and
+; decrease server load especially with larger indexes.
+;default_side_recommend[] = SideFacetsDeferred:Results:CheckboxFacets
 ;default_side_recommend[] = EbscoResults:[namespace]:[url]
 ;default_noresults_recommend[] = SwitchTab
 default_noresults_recommend[] = SwitchType
@@ -81,9 +88,9 @@ highlighting = false
 ; For control over snippet captions, see the [Snippet_Captions] section below.
 snippets = true
 
-; When you filter a search using facets, VuFind will present a checkbox that can
-; be used to apply those filters to the next search you perform.  This setting
-; controls its default state: on (true) or off (false).
+; When you filter a search using facets, should VuFind retain your current filters
+; on the next search and provide a reset button to clear them (true), or should it
+; always perform new searches unfiltered (false)?
 retain_filters_by_default = true
 
 ; The filters listed below will be applied to all new searches by default. Omit
@@ -153,6 +160,8 @@ ISN                 = adv_search_isn
 Signatur            = "Call Number"
 Barcode             = Barcode
 toc                 = adv_search_toc
+;Coordinate        = Coordinates
+
 
 ; This section defines the sort options available on standard search results.
 ; Values on the left of the equal sign are either the reserved term "relevance"
@@ -337,35 +346,36 @@ CallNumber = callnumber-sort
 ;       Displays see and see also results to user based on search of Authority Index.
 ;       Any number of filter queries may be specified as parameters to limit which
 ;       set of authority records is used for recommendations; for example:
-;           AuthorityRecommend:record_type:Heading* OR Topical*:source:LCNAF
+;           AuthorityRecommend:record_type:Heading* OR Topical*:source:FAST
 ;       limits record_type to strings starting with "Heading" or "Topical" and
-;       limits source to LCNAF.  A special field name of "__resultlimit__" may be
+;       limits source to FAST. A special field name of "__resultlimit__" may be
 ;       used to suppress authority results when the result set contains more items
 ;       than the number specified as the corresponding value (e.g. if you configure
 ;       AuthorityRecommend:__resultlimit__:50 then authority recommendations will
 ;       only display on result screens displaying fewer than 50 hits; by default,
-;       recommendations will always display). Filtering is optional.
-; MapSelection:[ini section]:[ini name]
-;       Enable geographic searching capability via OpenLayers3 API by activating
-;       this module. Records must be indexed using the geographic search and display
-;       fields. See the marc_local.properties file for more information on indexing.
-;       Default settings and more comments may be found in the  [MapSelection]
-;       section in this file. The section name and ini file name loaded by the
-;       module may be overridden through the [ini section]/[ini name] parameters.
+;       recommendations will always display). A special field name of "__mode__"
+;       may be used to control what type of suggestions are presented (default is
+;       both seealso and usefor results, but you can turn on just one of these
+;       options if desired; for example "__mode__:seealso" would only show "see
+;       also" results from records whose main headings match the current search
+;       terms while "__mode__:usefor" would show only main headings from records
+;       whose "use for" headings match the current search. You can use "__mode__:*"
+;       to turn on all options (but this is default behavior if no __mode__ is
+;       set). Filtering is optional. A special field name of "__header__" may be
+;       used to customize the header text above the results (default = "See also").
+; Channels
+;       Display a link to the Channeled Browse functionality leading to channels of
+;       records related to the current search.
+; MapSelection
+;       Enable geographic searching capability by activating this module.
+;       Records must be indexed using the geographic search and display fields.
+;       See the marc_local.properties file for more information on indexing.
+;       See the [MapSelection] section of the geofeatures.ini file for more information.
 ; PubDateVisAjax:[zooming]:[facet field 1]:[facet field 2]:...:[facet field n]
 ;       Display a visualization of publication dates for each of the specified facet
 ;       fields.  This is designed for a field containing four-digit years.  Zooming
 ;       is set to either true or false and controls whether or not selecting part of
 ;       the graph zooms in to greater detail.
-; ResultGoogleMapAjax:[facets]
-;       Show a Google Map with markers for all result items which have long/latitude
-;       data (be sure to turn on location indexing in import/marc_local.properties).
-;       Each marker will show the number of items which are in the long_lat
-;       facet. A separate call is made when a marker is clicked to retrieve the
-;       first 5 records on that location facet. The map uses clustering to
-;       combine markers where there are more than one marker close together into
-;       clusters. The facets parameter is the name of the extra config file which
-;       holds the facet information(default "facets.ini").
 ; TopFacets:[ini section]:[ini name]
 ;       Display facets listed in the specified section of the specified ini file;
 ;       if [ini name] is left out, it defaults to "facets."
@@ -383,10 +393,26 @@ CallNumber = callnumber-sort
 ;
 ; AlphaBrowseLink:index
 ;       Use the query to generate a link to the specified alphabrowse index
+; DOI:[prefix]
+;       Detect DOIs in the user search query. If a DOI makes up part of the search,
+;       display a link to resolve it. If it makes up the entire query, redirect to
+;       the resolver automatically. [prefix] is the URL of the resolver to which
+;       the DOI itself will be appended.
+; ExternalSearch:[link label]:[url template]
+;       Display a link to an external search system. The contents of the <a> tag
+;       will be [link label] (which will be run through the translator -- use a
+;       translation string if you need to display a string containing a colon).
+;       The href will be [url template] with %%lookfor%% replaced with the current
+;       search's lookfor parameter. If you omit the %%lookfor%% placeholder, the
+;       search terms will simply be appended to the end of the URL template.
 ; Libraryh3lp:[type]:[id]:[skin]
 ;       Display a chat box for the Libraryh3lp service. [type] indicats the type
 ;       of chat being used (either "queue" or "user"). [id] is the name of the
 ;       queue or user. [skin] is optional and specifies a skin number to use.
+; RecommendLinks:[ini section]:[ini name]
+;       Display a list of recommended links, taken from [ini section] in
+;       [ini name], where the section is a mapping of label => URL. [ini name]
+;       defaults to searches.ini, and [ini section] defaults to RecommendLinks.
 ; RemoveFilters
 ;       Suggests removing facet filters to retrieve more results.
 ; SwitchQuery:[backend]:[opt-out checks to skip]:[opt-in checks to add]
@@ -447,6 +473,11 @@ Author[]            = AuthorFacets
 top[] = AuthorInfo
 side[] = "ExpandFacets:Author"
 
+; This is the default section used for setting up links for the RecommendLinks
+; recommendation module (see above for details).
+;[RecommendLinks]
+;Library of Congress Online Catalog = http://catalog.loc.gov/
+
 ; This section controls the "New Items" search.
 [NewItem]
 ; New item information can be retrieved from Solr or from the ILS; this setting
@@ -493,6 +524,11 @@ sort = "last_indexed desc"
 ;
 ; The available autocomplete handlers are:
 ;
+; Eds:[Mode]
+;       Use the EBSCO Discovery Service autocomplete handler (only intended to be
+;       used in the context of the EDS backend). [Mode] can be either "holdings" for
+;       title completion in PubFinder or "rawqueries" for completion of basic textual
+;       queries.
 ; None
 ;       Do not provide any suggestions.  You should use this handler if you want to
 ;       disable suggestions for one search type while still providing suggestions
@@ -526,6 +562,8 @@ sort = "last_indexed desc"
 enabled = false
 ; This handler will be used for all search types not covered by [Autocomplete_Types]
 default_handler = Solr
+; Auto-submit autocomplete on click or enter
+auto_submit = true
 
 ; In this section, set the key equal to a search handler from searchspecs.yaml and
 ; the value equal to an autocomplete handler in order to customize autocompletion
@@ -537,6 +575,7 @@ Author           = "Solr:Author:author,author2"
 Subject          = "Solr:Subject:topic,genre,geographic,era"
 CallNumber       = "SolrCN"
 ISN              = "Solr:ISN:isbn,issn"
+Coordinate = "None"
 tag              = "Tag"
 
 ; When snippets are enabled, this section can be used to display captions based on
@@ -663,21 +702,10 @@ view=full
 ; functionality found in the MapSelection recommendation module.
 ; To enable this feature, uncomment the default_top_recommend[] = MapSelection
 ; in the default recommendations section. To set the configuration settings
-; for this feature, adjust the parameters below.
+; for this feature, adjust the parameters in the geofeatures.ini file.
 [MapSelection]
-; This defines the coordinates of a search region that will be highlighted when
-; the user clicks the "Geographic Search" link next to the VuFind search box.
-; This should ideally cover a large area of the map where most/all of your
-; geographic points are located. If your dataset is not concentrated in one
-; geographic area, it is advised that you pick a default area, and do not use
-; the entire extent of the map for searching (otherwise the search may be slow).
-; The default coordinates specified below are in decimal degrees, and are
-; ordered as WENS (west, east, north, south). Ranges of valid values are:
-; -180 to 180 (longitude) and -85 to 85 (latitude). Note, to search from and to
-; the international date line, use west = -179 and east = -180.
-default_coordinates = "-95, 30, 72, 15"
-; height: Height in pixels of the map selection interface.
-height = 320
+; These configuration settings have been superseded by the geofeatures.ini file.
+; See the [MapSelection] section of the geofeatures.ini file for more information.
 
 ; This section defines settings used to fetch similar records.
 [MoreLikeThis]
@@ -694,6 +722,23 @@ height = 320
 ; This setting can be used to limit the maximum number of suggestions. Default is 5.
 ;count = 5
 
+; This section controls the behavior of the Search/Home screen.
+[HomePage]
+; Content blocks can be selected from the list below:
+;
+; Channels:[source] - Display the homepage channels for the specified [source].
+; [source] defaults to Solr.
+;
+; FacetList:[source]:[column size] - Display a list of facet values
+; drawn from the [source] backend, with a maximum of [column size] values per
+; column. [source] defaults to Solr and [column size] defaults to 10.
+;
+; IlsStatusMonitor:[target] - Performs an AJAX health check of the ILS and
+; prepends a warning message to the HTML element identified by the jQuery selector
+; provided in [target] (which defaults to .searchHomeContent.
+content[] = IlsStatusMonitor
+content[] = FacetList
+
 ; PreMunge is used by a listener on the search-pre event
 ; registered by the MungerInjectionDelegatorFactory. This listener applies
 ; the regex patterns as configured for the search handlers