2 results found

1. Order of content fields in Content Graph _fulltext property

   When a text field is indexed by Content Graph in the _fulltext property, the values in the fields are appearing out of order from how they are configured in the CMS, where nested content is appearing before outer container content.

   For example, our page contains an accordion block. The accordion block has a content area which allows topics blocks. The topics blocks contain a rich text field.

   When querying graph the _fulltext property shows the values of the indexed content in this order:

   Topics block content
   Topics block name
   Accordion block name
   Container block name

   We would expect to see the content in reverse order where the outer block names appear above the inner content:

   Container block name
   Accordion Block name
   Topics block name
   Topics block content

   The customer is querying graph content to feed data into their own LLM, and the proper order of block or page contents is essential for the LLM since it affects how the model comprehends the context. For example, these blocks are being used as FAQ content, where the "question" is the name of the block and the "answer" is the content of the rich text field. Maintaining the order of fields here is critical to preserve the context of the content.

   When a text field is indexed by Content Graph in the _fulltext property, the values in the fields are appearing out of order from how they are configured in the CMS, where nested content is appearing before outer container content.

   For example, our page contains an accordion block. The accordion block has a content area which allows topics blocks. The topics blocks contain a rich text field.

   When querying graph the _fulltext property shows the values of the indexed content in this order:

   Topics block content
   Topics block name
   Accordion block name
   Container block name

   We would expect to see… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Graph  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminCiara Bergin (Principal Product Manager, Optimizely) responded

   We’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!

2. Site specific SearchProvider for Content Graph

   The package Optimizely.ContentGraph.Cms 4.1.0 introduced a SearchProvider that enables searching within the page tree.

   We would like this SearchProvider to respect the Query.SearchRoots property so that searches can be limited to the current page. This would be valuable for us, as we manage more than 60 sites with large amounts of content.

   With Find (Search & Navigation), we were able to override the SearchProvider and inject the search root ourselves, for example:

   public override IEnumerable<SearchResult> Search(Query query)
   {
   var startPageId = ContentReference.StartPage?.ID;
   var startPage = startPageId > 0 ? startPageId.ToString() : "1";
   query.SearchRoots = new[] { startPage };
   return base.Search(query);
   }

   We would appreciate similar flexibility or support in Content Graph so that search queries can be scoped.

   The package Optimizely.ContentGraph.Cms 4.1.0 introduced a SearchProvider that enables searching within the page tree.

   We would like this SearchProvider to respect the Query.SearchRoots property so that searches can be limited to the current page. This would be valuable for us, as we manage more than 60 sites with large amounts of content.

   With Find (Search & Navigation), we were able to override the SearchProvider and inject the search root ourselves, for example:

   public override IEnumerable<SearchResult> Search(Query query)
   {
   var startPageId = ContentReference.StartPage?.ID;
   var startPage = startPageId > 0 ? startPageId.ToString() : "1";
   query.SearchRoots = new[] { startPage };
   return base.Search(query);… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  0 comments  ·  Graph  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating