Infocenter Views¶
Overview¶
Infocenter Views allow partners to define preconfigured search queries in the partner portal. These views serve as custom navigation elements (e.g., categories) that can be:
- Attached to Infocenter data
- Utilized through the Infocenter Search API
The goal is to provide greater flexibility in tailoring the search and data experience per project or partner.
Info
If you want to get started quickly, you can use the View Quickstart
Infocenter View Management¶
To manage Infocenter Views, we are introducing new CRUD operations in the Infocenter API.
Info
These endpoints are accessible only to authorized consumers of the Infocenter View service, using the partner's definition context.
| Endpoint | Second Header | Request | Response |
|---|---|---|---|
| GET search/views | Get all search views | - | SearchViewResponse[] |
| GET search/views/{id} | Get search view by Id | - | SearchViewResponse |
| POST search/views | Create search view | SearchViewRequest | SearchViewResponse |
| PUT search/views/{id} | Update search view | SearchViewRequest | SearchViewResponse |
| DELETE search/views/{id} | Delete search view by Id | - | - |
Infocenter Views in Search Requests¶
- A
viewIdparameter is added to the SearchRequest. - The corresponding view definition is loaded and used as a base configuration.
- The active search request is merged into the base view definition dynamically.
Infocenter Views in API Responses¶
- A new property
viewis added to each object. - This property lists the view IDs related to the object.
- Views for the current project or partner are merged into the response, if requested.
View Creator UI¶
A user interface component is provided to assist partners in creating and managing views within the context of a selected project.
Features include:
- Add filters and scopes to a view definition.
- Live preview of:
- Search results based on current filters.
- Facet definitions and UI representation.
- Use facets to define filters.
- Save or update view metadata.
Landing Page Integration¶
The existing Landing-Page component is extended to accept a viewId parameter and load the corresponding configuration.
Please check back for updates as we continue to evolve this functionality.