Table of Contents | ||||
---|---|---|---|---|
|
Starting from 2023.1.0, Starter kit provides a new user interface for managing portal search. It is now possible to edit or create a universe and its associated filters on production environment through this interface. The interface is not yet open to our customer yet, and customers (a developer role is needed).
Installation & Access
Projects starting with Wedia version 2023.1 can use search configuration interface right away, as this is the default setup.
Existing projects that started on previous versions of Starter Kit can migrate to benefit from the feature. ➡️ Follow the documentation to migrate
Existing projects that did not start with Starter kit do not have access to this configuration interface.
Getting started with the search management interface
Basics
The final setup that is presented to the end user is a combination of three configuration layers :
1.Product Layer
configuration delivered by default with Starter kit
2.Developer Layer
configuration coded by the project developer
3.Project Layer
configuration set up by the project manager from the new configuration interface
The project layer has priority to the developer Layer and the developer layer has priority to the product Layer.
Search Configuration capabilities
The interface allow you to configure :
Portal universes
Portal top filter bars (per universe)
Portal advanced search filters (per universe)
Filters management
The settings interface allow to manage filters or group of filters with specific settings, like operators, dynamic search (filterFromAggregates) etc.
Universe management
Universes created from the settings interface can be based on the following criterias :
One or several asset libraries up to your choice,
One or several asset types up to your choice,
One or several custom criterias based on the metadata of your choice : select the metadata, and then the value(s).
For each universe the interface allow to :
Add filters to a universe
Filters used on the universe filters management are filters made from the setting interface or default named filters delivered by default with starter-kit
For each universe the interface allow to :
Configure the advanced search filters
The universe advanced search management is based on a selection of metadatas you want to use in the advanced search feature.
Limits
Three Two main use cases still require a developer intervention :
Custom filter names:
If you need to customize the filters name (by default, filters use the metadata name)Several tabs in advanced search
Complex filter with several tabs
Environment and deliveries
Search setup through the new configuration interface must The configuration can be done on any project environment. The important thing is to have a reference environment. When starting a project, the reference environment can be the integration environment until it is decided to make it the production environment.
The projects can still deliver updates of the “project configuration layer” through NAR archives.
To retrieve a PRODUCTION configuration layer, and apply it to INT or PPROD :
➡️ Follow theses instructions
another environment, follow theses steps : https://crossmedia.atlassian.net/wiki/spaces/WD/pages/2509373509/Server+side+configuration#How-to-retrieve-configuration-done-by-UI-and-deploy-it-to-another-environment
Documentation
More details for developpers : Server side configuration