connect Rovo to our confluence Glossary

[Tami Dubi]

Hi,

We are using the Smart Terms for Confluence add-on.
We have now received the Rovo search in our Confluence standard site. Can we predefine Rovo search to prioritize results so that if someone searches for a term that already has a definition, it will show first in the results?

Thanks,
Tami

[Nikola Perisic · Accepted solution]

Hello @Tami Dubi 

Not directly. You need to prompt Rovo for the definition and then add it as bookmark for your team. Everyone in your organization will see this result when they search for the terms.

You need to define the search result title, URL, Description and also the Search terms that could be used in order to find the definition.

[Tami Dubi]

Thanks @Nikola Perisic ,
a follow-up question. Is there a difference between bookmarks and definitions in Rovo, in the way they are created and viewed by the users?

[Nikola Perisic]

Both are powered by Rovo. This article shows how you can create definitions: https://support.atlassian.com/rovo/docs/add-or-edit-a-definition/

[Dr Valeri Colon _Connect Centric_]

Yup, I agree @Nikola Perisic  for best results, use definitions to show term meanings inline across Rovo and bookmarks to pin key glossary entries at the top of search results.

[Tami Dubi]

Hi @Dr Valeri Colon _Connect Centric_ ,
I read the definitions documentation, and it isn't clear who can set definitions on a site level and product level, assuming we want one source of truth across the org. 

Thanks,
Tami

[Khawla Issaoui Creativas]

Hello @Tami Dubi 

This is Khawla from Smart Terms for Confluence Team!

At this stage, based on our testing and available information, Rovo (Atlassian Intelligence) does not index or prioritize content from Marketplace apps, including Smart Terms for Confluence. This means that glossary terms or definitions created using Smart Terms are currently not surfaced or prioritized in Rovo search results, even if a definition for the searched term exists in your glossary.

This behavior appears to be consistent with how Rovo handles app data in general, including term content or other structured data from third-party apps. Atlassian has not announced any change in this behavior so far.

That said, we’d be happy to run specific tests or collaborate further if you’d like to explore this in more depth, or if you notice anything different in your environment.

You can reach out to our support team for further details: https://creativas.atlassian.net/servicedesk/customer/portals