Add a search block on the page of your choice

Search results from the engine are displayed on a full-screen page. The results displayed depend on the indexing choices made by the administrator in the central configuration.

For example, one could choose to index only the resources of a certain type, or only those of the shared library.

In this example, we find users and resources:

To perform a full-text search, enter the searched term in the input area and click the “Search” button to get the number of items found and their list below the engine.

The Lucene engine offers a number of syntaxes to refine searches or the priorities of result output.

General documentation on these syntaxes is available (in English) here: https://lucene.apache.org/core/2_9_4/queryparsersyntax.html

To perform an advanced search, follow the “Advanced search” link, complete the advanced search form, and click the “Search” button to get the number of items found and their list below the engine.

Note: a link is present on the interface to return to the simple search.

Warning: a space will only be taken into account if it is included in an explicit string, as in Test_1 for example. If you search for the occurrence Test and exclude Test 1 from your search, you will get zero results.

Advanced search example:

Site admin/search/manage global search

1. Select a search engine: This first menu indicates the engine used (Solr)
2. Enable search areas: Target areas of the search via checkboxes (assignments, folders, files, courses, urls, etc.)
3. Set up the search engine:
   1. Index data: Yes/No:
   2. Enable global search: If this setting is enabled, data is indexed and synchronised by means of a scheduled task (CRON)

For this last point, the function must first be enabled in the site's advanced features: Your moodle/admin/settings.php?section=optionalsubsystems

Local plugins/search/manage global search

• UTF8 transcoding of local_search results: by default no conversion
• Software locking local_search: by default no
• Switch index file locking to “software” mode: Must be used when continuous indexing of resources is done by several different clusters on a shared NFS mount. Software locking is less rigorous than physical locking, but is the only way to work on a clustered system.
• Indexing of physical files local_search: by default no. If active, the physical files attached to Moodle contents or resources are indexed in full text.
• File types local_search: List of file types (extensions) supported by the full-text conversions. By default PDF,TXT,HTML,PPT,XML,DOC,HTM
• Define paths from the Moodle root local_search: by default yes
• Analysis body limit local_search: by default the value is 0. Limits the size of the text body analysed for indexing. This can improve the indexer's performance, but lose search capabilities.

• PDF support: System path to your pdftotext (xpdf) library. By default lib/xpdf/linux/bin64/pdftotext -enc UTF-8 -eol unix -q

1. Word documents support: System path to the doctotext converter for Word. By default lib/antiword/linux/usr/bin/antiword
2. Environment variable for MSWord conversion: By default ANTIWORDHOME=/var/www/formation-enligne31.com/local/search/lib/antiword/linux/usr/share/antiword

• Show the list of indexed objects:

• Users local_search: by default yes, to search by user

• Uncheck the activity modules not to be indexed. Example: Assignment 2.2 (disabled) local_search: unchecked

• Global activation local_search: Yes/No, by default no. If disabled, no indexing will be done and all the interfaces related to global search are hidden. It must therefore be checked to use indexing.

• Valéry Frémaux (valery@activeprolearn.com) Development and testing
• Florence Labord (florence@activeprolearn.com) Functional documentation and testing

Back to the component index - Back to plugins index - Back to catalogue - Index by functional subsets