Uploaded image for project: 'Atlassian Intelligence'
  1. Atlassian Intelligence
  2. AI-896

Don't index/display a raw body when "ac:custom-content:search-body" is set

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      Feature request made in developer support: https://ecosystem.atlassian.net/browse/DEVHELP-3321

      In my Mind Map App, I store the mind map data in XML format in the raw body of a custom content type as proposed by the documentation:
      "You can define custom content to support a content body with a type of raw. This is useful when you want to store, for example, stringified JSON to the content." [1]

      While this works well, the raw body still gets indexed and displayed in the confluence search results. And seeing a bunch of XML code in the search results is probably confusing for the user.

      I tried using the "ac:custom-content:search-body" property which states: "The content of this property will also be used in displaying the excerpt text for search result." [1] but the content of that property was only added to the excerpt text and the XML code still remained.

      My proposal is not to index/display a raw body - at least when "ac:custom-content:search-body" is set.

      [1] https://developer.atlassian.com/cloud/confluence/modules/custom-content/

            [AI-896] Don't index/display a raw body when "ac:custom-content:search-body" is set

            pqz made changes -
            Component/s Original: XP - Content Search [ 61005 ]
            Component/s New: XP - Content Search [ 75299 ]
            Key Original: CONFCLOUD-67909 New: AI-896
            QA Demo Status Original: Not Done [ 14330 ]
            QA Kickoff Status Original: Not Done [ 14234 ]
            Project Original: Confluence Cloud [ 18513 ] New: Atlassian Intelligence [ 23110 ]
            nmcginley made changes -
            Component/s Original: Search - Indexing [ 46493 ]
            Component/s New: XPC - Content Search [ 61005 ]
            Peter Obara made changes -
            Component/s New: Search - Indexing [ 46493 ]
            Component/s Original: Ecosystem [ 49196 ]
            Component/s Original: Macros - 3rd Party [ 46352 ]
            Peter Obara made changes -
            Rank New: Ranked lower
            Peter Obara made changes -
            Rank New: Ranked lower
            Shreshth Luthra (Inactive) made changes -
            Rank New: Ranked lower
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3559421 ] New: JAC Suggestion Workflow 3 [ 3630709 ]
            Shreshth Luthra (Inactive) made changes -
            Labels Original: cc-integration cc-integrations devhelp ecosystem New: cc-integration cc-integrations devhelp ecosystem grooming-ready
            Anne Calantog made changes -
            Description Original: h3. Summary

            Feature request made in developer support: https://ecosystem.atlassian.net/browse/DEVHELP-3321

            {quote}
            In my Mind Map App, I store the mind map data in XML format in the raw body of a custom content type as proposed by the documentation:
            "You can define custom content to support a content body with a type of raw. This is useful when you want to store, for example, stringified JSON to the content." [1]

            While this works well, the raw body still gets indexed and displayed in the confluence search results. And seeing a bunch of XML code in the search results is probably confusing for the user.

            I tried using the "ac:custom-content:search-body" property which states: "The content of this property will also be used in displaying the excerpt text for search result." [1] but the content of that property was only added to the excerpt text and the XML code still remained.

             !Screenshot 2019-08-16 at 11.22.54.png, height=300!

            My proposal is not to index/display a raw body - at least when "ac:custom-content:search-body" is set.

            [1] https://developer.atlassian.com/cloud/confluence/modules/custom-content/
            {quote}
            New: h3. Summary

            Feature request made in developer support: [https://ecosystem.atlassian.net/browse/DEVHELP-3321]
            {quote}In my Mind Map App, I store the mind map data in XML format in the raw body of a custom content type as proposed by the documentation:
             "You can define custom content to support a content body with a type of raw. This is useful when you want to store, for example, stringified JSON to the content." [1]

            While this works well, the raw body still gets indexed and displayed in the confluence search results. And seeing a bunch of XML code in the search results is probably confusing for the user.

            I tried using the "ac:custom-content:search-body" property which states: "The content of this property will also be used in displaying the excerpt text for search result." [1] but the content of that property was only added to the excerpt text and the XML code still remained.

            !Screenshot 2019-08-16 at 11.22.54.png|width=745,height=419!

            My proposal is not to index/display a raw body - at least when "ac:custom-content:search-body" is set.

            [1] [https://developer.atlassian.com/cloud/confluence/modules/custom-content/]
            {quote}
            Anne Calantog made changes -
            Description Original: h3. Summary

            Feature request made in developer support: https://ecosystem.atlassian.net/browse/DEVHELP-3321

            {quote}
            In my Mind Map App, I store the mind map data in XML format in the raw body of a custom content type as proposed by the documentation:
            "You can define custom content to support a content body with a type of raw. This is useful when you want to store, for example, stringified JSON to the content." [1]

            While this works well, the raw body still gets indexed and displayed in the confluence search results. And seeing a bunch of XML code in the search results is probably confusing for the user.

            I tried using the "ac:custom-content:search-body" property which states: "The content of this property will also be used in displaying the excerpt text for search result." [1] but the content of that property was only added to the excerpt text and the XML code still remained.

             !Screenshot 2019-08-16 at 11.22.54.png|thumbnail!

            My proposal is not to index/display a raw body - at least when "ac:custom-content:search-body" is set.

            [1] https://developer.atlassian.com/cloud/confluence/modules/custom-content/
            {quote}
            New: h3. Summary

            Feature request made in developer support: https://ecosystem.atlassian.net/browse/DEVHELP-3321

            {quote}
            In my Mind Map App, I store the mind map data in XML format in the raw body of a custom content type as proposed by the documentation:
            "You can define custom content to support a content body with a type of raw. This is useful when you want to store, for example, stringified JSON to the content." [1]

            While this works well, the raw body still gets indexed and displayed in the confluence search results. And seeing a bunch of XML code in the search results is probably confusing for the user.

            I tried using the "ac:custom-content:search-body" property which states: "The content of this property will also be used in displaying the excerpt text for search result." [1] but the content of that property was only added to the excerpt text and the XML code still remained.

             !Screenshot 2019-08-16 at 11.22.54.png, height=300!

            My proposal is not to index/display a raw body - at least when "ac:custom-content:search-body" is set.

            [1] https://developer.atlassian.com/cloud/confluence/modules/custom-content/
            {quote}

              Unassigned Unassigned
              acalantog Anne Calantog
              Votes:
              9 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: