A single installation of LucidWorks Search may be used to index multiple types of content, serve multiple user constituencies, or accommodate multiple overlapping security rules. It does this by supporting the creation and use of multiple "collections". A collection is a set of documents that are grouped together with the same indexing and query rules. Each collection in LucidWorks has its own index and configuration files and is logically separate from all other collections.
For those familiar with Solr, the concept of collections in LucidWorks is very similar to the concept of cores in Solr.
By default, each LucidWorks Search installation includes two collections out of the box: "collection1" and "LucidWorksLogs".
Collection1 is the primary collection used by LucidWorks Search to store indexes and define query settings. It can be used as-is immediately after installation to start indexing documents and using the default Search UI. However, a collection cannot be renamed once created (nor can content be moved from one collection to another without indexing it all from scratch). So, if you think you'll use multiple collections and want to name each one based on what it contains or what it will be used for, you would probably create a new collection and start from there.
The LucidWorksLogs collection is a special collection, used to index logs for easier troubleshooting. It is discussed in more detail in the section on the LucidWorksLogs collection. It can be deleted at any time and recreated later, if desired.
If you want to delete collection1, you can do so after you've created at least one other standard collection, as there must always be at least one collection (not including the LucidWorksLogs collection).
A collection that has been customized can also be used as the basis for future collections; see the section on Collection Templates for more information.
You can configure the following items for each collection individually:
- Data sources
- Query settings
- Search UI
- Search Filters
- Solr Admin
After you have created additional collections, you should pay special attention to the collection name you are working with so you edit the proper configuration files or make the correct API calls. This is particularly true when using the REST API or several of the advanced configuration options discussed later in this Guide, but it also applies to the various screens of the Admin UI. Modifying the wrong collection out of context may have unexpected consequences including poorly indexed content or an inconsistent search experience for users.
The following items are system-wide and can only be configured for the entire LucidWorks Search installation or instance:
- Collection definition
- Access to user interfaces
- Alerts (although these take the collection as a parameter to limit the query)