4 results found

1. Support for Trash Status Filtering via exposing _deleted property in query filters to improve duplicate result handling

   We have use cases where we need to search content to determine if an item is in the Trash. Currently, we use the cg-include-deleted: true header as described in the documentation. However, we have observed that duplicate results are returned from the Graph for Content() items.

   One result represents the original location (tombstone marker) with the property _deleted: null, while the most recent version in the index has _deleted: true.

   Although we can filter out duplicates on the client side, this approach is not ideal.
   We would like the _deleted property to be available as part of ContentWhereInput so that a filter could be applied, for example:

   query SearchContent(
   $limit: Int
   $skip: Int
   $contentTypes: [String!]
   $searchText: String!
   ) {
   Content(
   limit: $limit
   skip: $skip
   orderBy: { _ranking: RELEVANCE, _modified: DESC, }
   where: {
   _and: [
   { _deleted: { eq: true }}
   { ContentType: { in: $contentTypes } }
   { _fulltext: { match: $searchText } }
   ]
   }
   ) {
   total
   items {
   Status
   _deleted
   ContentLink {
   Id
   }
   }
   }
   }

   We have use cases where we need to search content to determine if an item is in the Trash. Currently, we use the cg-include-deleted: true header as described in the documentation. However, we have observed that duplicate results are returned from the Graph for Content() items.

   One result represents the original location (tombstone marker) with the property _deleted: null, while the most recent version in the index has _deleted: true.

   Although we can filter out duplicates on the client side, this approach is not ideal.
   We would like the _deleted property to be available as part of ContentWhereInput so that… more

   4 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

   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
   Research & Design  ·  AdminCiara Bergin (Principal Product Manager, Optimizely) responded

   Good news - this idea is now being explored by our product and design teams. We’re researching potential solutions and scoping out what an implementation might look like. We’ll share updates here as our thinking evolves.

2. Syncing folder types/names to GraphQL index

   We have a need to query content under certain folder from GraphQL API. At the moment we can query the parent GUIDs from a block, but it only returns a list of GUIDs. It returns them in a certain order, so it is possible to find out from there which is which folder, but it would be easier if we could query also the name of the folder. At the moment GraphQL API does not index the folder information, so we would like the folder information also to be synced to the index.

   4 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

   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
   Research & Design  ·  AdminCiara Bergin (Principal Product Manager, Optimizely) responded

   Good news - this idea is now being explored by our product and design teams. We’re researching potential solutions and scoping out what an implementation might look like. We’ll share updates here as our thinking evolves. Please do update with any further ideas or comments

3. Allow ancestor/children links in Content Areas in Content Graph

   I am looking to get the parent/children of a content item that is used within a Content Area to support a hierarchical relationship. Currently, it is not possible to use the _link property on Content Areas within Content Graph.

   In this query:

   query MyQuery {
     MyPage(where:{ContentLink:{Id:{eq: 1119}}}) {
       item {
         ContentLink {
           Id
         }
         _link(type: ANCESTORS) {
           MyParentPage {
             items {
               Url
             }
           }
         }
       }
     }
     MyBlock(where:{ContentLink:{Id: {eq:1127}}}) {
       items {
         Cards {
           ContentLink {
             Id
             Expanded {
               _link(type: ANCESTORS) {
                 MyParentPage {
                   items {
                     Url
                   }
                 }
               }
             }
           }
         }
       }
     }
   }
   

   In the first query, we get back the parent items as expected, but in the second query we do not get any data for the _link. We should get back the same data in both.

   I am looking to get the parent/children of a content item that is used within a Content Area to support a hierarchical relationship. Currently, it is not possible to use the _link property on Content Areas within Content Graph.

   In this query:

   query MyQuery {
     MyPage(where:{ContentLink:{Id:{eq: 1119}}}) {
       item {
         ContentLink {
           Id
         }
         _link(type: ANCESTORS) {
           MyParentPage {
             items {
               Url
             }
           }
         }
       }
     }
     MyBlock(where:{ContentLink:{Id: {eq:1127}}}) {
       items {
         Cards {
           ContentLink {
             Id
             Expanded {
               _link(type: ANCESTORS) {
                 MyParentPage {
                   items {
                     Url
                   }
                 }
               }
             }
           }
         }
       }
     }
   }
   

   In the first query,… more

   3 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

   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
   Research & Design  ·  AdminCiara Bergin (Principal Product Manager, Optimizely) responded

   Thanks for sharing this idea. Our product and design teams are looking into it now. We’re exploring possible solutions and figuring out what implementation could involve. We’ll keep you posted here as things progress.

4. 'Stop words' feature in Optimizely Graph

   We need to stop few words from search or indexing. For example, in case of search term 'having a baby' also brings results with 'a' which does not make sense. We are looking for a similar feature like 'synonyms'. We have been advised in the ticket reference 1748761 (https://support.optimizely.com/hc/en-us/requests/1748761) to raise a feature request to bring this feature back as its currently deprecated. We are from Publicis Sapient and working for St Luke's digital transformation project.

   The below document does not have enough details in the API call with PUT method. Also it says the feature is deprecated.

   https://docs.developers.optimizely.com/platform-optimizely/docs/stopwords#:~:text=Stop%20words%20with%20full%2Dtext%20search&text=a%2C%20an%2C%20and%2C%20are,a%20token%20from%20being%20indexed.

   We need to stop few words from search or indexing. For example, in case of search term 'having a baby' also brings results with 'a' which does not make sense. We are looking for a similar feature like 'synonyms'. We have been advised in the ticket reference 1748761 (https://support.optimizely.com/hc/en-us/requests/1748761) to raise a feature request to bring this feature back as its currently deprecated. We are from Publicis Sapient and working for St Luke's digital transformation project.

   The below document does not have enough details in the API call with PUT method. Also it says the feature is deprecated.

   … 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

   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
   Research & Design  ·  AdminCiara Bergin (Principal Product Manager, Optimizely) responded

   Good news - this idea is now being explored by our product and design teams. We’re researching potential solutions and scoping out what an implementation might look like. We’ll share updates here as our thinking evolves.