4 results found
-
Synonyms and "Pinned results" admin UI for custom Graph sources
We are indexing custom entities to a custom source in Graph (that is, to a source named something other than "default").
Since the editor UI for synonyms and "Pinned results" defaults to the "default" source behind the scenes (it does not allow you to specify any other source), it is impossible for our customer to use the synonyms or "Pinned results" features within our custom source.
We want a source-dropdown in the synonyms UI and the "Pinned results" UI. See attached image for an example.
5 votes -
Search Management
Add support to see actual graphlql queries in Search Management/Performance view. Now it shows only names of the queries.
5 votes -
geopoint
I'm a developer trying to solve customer needs for sorting results from graph queries by geolocation. Sorting by geolocation is a vital part of meeting customer expectations and would be greatly appreciated to get solved as we are now performing multiple cursor queries in order to sort by a customers location.
1 vote -
Computed fields in Contracts
Role: Developer working with Optimizely CMS 13 and Optimizely Graph.
Problem:
I am implementing search across multiple content types (pages, media etc.) using Optimizely Graph.
A common requirement is to expose consistent search fields across different content types, for example SearchTitle and SearchDescription, while allowing each content type to derive those values from its own properties and fallback logic.The current limitation is that computed fields cannot be exposed through Contracts. While computed fields can be defined on concrete content types and avoid storing redundant search data, they cannot be used to create a unified schema across multiple content types.
…
2 votes
- Don't see your idea?