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

Extend Lucene search engine in Confluence to add support for synonym rings, faceted search, etc

    • 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.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      The search capability of Confluence is starting to fall behind that offered by many commercial knowledge products. In particular there is no ability in Confluence to specify synonym rings (a ring is a set of terms which have equivalent meaning - a term meaning a word or a phrase). This is useful for many reasons in particular knowledge domains (for example a user could enter either an acronym or its equivalent long form or other predefined synonym into the search box and the indexed Content Entity Objects would return documents that contain any of them). Also there is no ability to predetermine that certain Content Entity Objects are always matched to particular search terms in order to guarantee that desired content is returned if someone uses a particular search term. There are no extensions employed by Confluence to allow search to provide faceted search capabilities (for example, see http://drupal.org/project/faceted_search or SOLR )

      These features are important to enhancing the functionality of knowledgebases and providing users with more fine tuned search capability that, if used skillfully, are more likely to produce useful and quick access to content for the average non-technical user without having to be a search query guru.

      These features should be implemented in search in such a way that they can be configured per space or globally and that plugins such as metadata and advanced search can take advantage of the added features, being able to extend or modify their behavior for particular purposes.

      Finally, there should be the option to index rendered wiki pages such that wiki markup is never shown to the user in search results.

      Make custom metadata (ala metadata plugin) capability and metadata reporting/searching an integrated part of the base Confluence product

      Incorporate these features into the Remote SOAP interface.

      The features should be configurable primarily by either site and/or space administrators depending on scope.

      Some of these features have various open source implementations that are demonstrated or have become commercial products. Products such as Sharepoint 2007 and others have implemented some of these features or are rumored to be adding them in the near future.

      Note: I was reminded that this is probably too broad for a feature request. I apologize for that. I just wanted to tie a lot of related aspects of the search improvements I was requesting together (as a wish list).

            [AI-714] Extend Lucene search engine in Confluence to add support for synonym rings, faceted search, etc

            Hi all, sadly due to our multi-tenanted architecture we are not able to fix this ticket

            Owen Wallis added a comment - Hi all, sadly due to our multi-tenanted architecture we are not able to fix this ticket

            Ola added a comment -

            The synonyms management and boosting of some hits would be a great improvement. Space owners would like to have more capability to influence what users find by particular keywords.

            Ola added a comment - The synonyms management and boosting of some hits would be a great improvement. Space owners would like to have more capability to influence what users find by particular keywords.

            Would love to see some sort of logging of search terms...

            Helen Griffith added a comment - Would love to see some sort of logging of search terms...

            Please support Solr.

            Kurt Newcomb added a comment - Please support Solr.

            logging of search term utilization would be helpful just to start.

            A workaround is to enable logging at DEBUG level for com.atlassian.confluence.search.v2.lucene package, but beware that search terms are logged after transformation and other sources in the app use the search engine.

            Sergey Svishchev added a comment - logging of search term utilization would be helpful just to start. A workaround is to enable logging at DEBUG level for com.atlassian.confluence.search.v2.lucene package, but beware that search terms are logged after transformation and other sources in the app use the search engine.

            Better searching capabilities would be very helpful for our organization. We have 10,000+ users who use Confluence for knowledge management of a myriad of our Customer facing and internal support operating procedures and processes for a Fortune 500 company.

            At the very least - logging of search term utilization would be helpful just to start.

            Mark Hursh added a comment - Better searching capabilities would be very helpful for our organization. We have 10,000+ users who use Confluence for knowledge management of a myriad of our Customer facing and internal support operating procedures and processes for a Fortune 500 company. At the very least - logging of search term utilization would be helpful just to start.

            Hi Steve, thanks for the feature request - and no, it is not too broad as an initial request, we like detailed requests more than too short requests since we can always break them down. I just had to remove some of the components you suggested, since that was really too broad. Looking at all the other feature requests we have, please don't expect this request to be implemented in Confluence very soon, though....

            Per Fragemann [Atlassian] added a comment - Hi Steve, thanks for the feature request - and no, it is not too broad as an initial request, we like detailed requests more than too short requests since we can always break them down. I just had to remove some of the components you suggested, since that was really too broad. Looking at all the other feature requests we have, please don't expect this request to be implemented in Confluence very soon, though....

            Steve Koch added a comment -

            Yes, of course, you are correct. There are probably ways around it. Perhaps one could decide what markup tags to avoid rendering or at least mark pages that should not be rendered for these and other unforeseen problems.

            Steve Koch added a comment - Yes, of course, you are correct. There are probably ways around it. Perhaps one could decide what markup tags to avoid rendering or at least mark pages that should not be rendered for these and other unforeseen problems.

            Finally, there should be the option to index rendered wiki pages such that wiki markup is never shown to the user in search results.

            While I agree in principle, I'm not sure how well it would work in practice unless macros were omitted ... imagine what the search results would look like if any of them contained a

            {gmaps}

            or

            {gallery}

            macro!

            Dan Hardiker added a comment - Finally, there should be the option to index rendered wiki pages such that wiki markup is never shown to the user in search results. While I agree in principle, I'm not sure how well it would work in practice unless macros were omitted ... imagine what the search results would look like if any of them contained a {gmaps} or {gallery} macro!

              owallis@atlassian.com Owen Wallis
              81aec81a7c85 Steve Koch
              Votes:
              52 Vote for this issue
              Watchers:
              37 Start watching this issue

                Created:
                Updated: