Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-3529

Extend Faceted Navigation usecases

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • r2.10.00
    • r2.17.00
    • repository-core
    • None

    Attachments

      1.
      		 Phase 1: Move FacetedNavigation to seperate project & seperate namespace Sub-task Closed Ard Schrijvers  
      2.
      		 Add support for ranges Sub-task Closed Ard Schrijvers  
      3.
      		 Add support to limit resultset size to predefined limit Sub-task Closed Ard Schrijvers  
      4.
      		 Add support for faceted navigation on primary node type Sub-task Closed Ard Schrijvers  
      5.
      		 Add possibility for initial query in the faceted navigation node which works as a filter Sub-task Closed Ard Schrijvers  
      6.
      		 Add possibility to return the resultset nodes in some predefined order, like ordered descending on myproj:mydate Sub-task Closed Ard Schrijvers  
      7.
      		 Check if during update all content the ServicingNodeIndexer queryHandlerContext is fine with the queryHandlerContext.getNamespaceRegistry().getPrefix Sub-task Closed Ard Schrijvers  
      8.
      		 Replace the FacetTypeConstants constants like '\uFAFA' or '\uFAFE' with lucene payloads Sub-task Closed Ard Schrijvers  
      9.
      		 remove the property type postfixing in lucene terms with FacetTypeConstants like '\uFAFA' Sub-task Closed Ard Schrijvers  
      10.
      		 remove FixedScoreTermQuery as it is not much faster then normal TermQuery Sub-task Closed Ard Schrijvers  
      11.
      		 Fix the DerivedDateTest again wrt changes in faceted navigation engine Sub-task Closed Junaidh Kadhar Sheriff  
      12.
      		 Add out-of-the-box support for faceted navigation on dates, for example on year/month/day Sub-task Closed Ard Schrijvers  
      13.
      		 Add support for ranges on long & double (for example for prices) Sub-task Closed Ard Schrijvers  
      14.
      		 performance: for getting the hit counts, do not use hit collector of Lucene but the index reader terms directly Sub-task Closed Ard Schrijvers  
      15.
      		 During indexing rounding of dates to day seem to fail for times between 0:00 and 0:59:59, returning the wrong day number Sub-task Closed Ard Schrijvers  
      16.
      		 Add default faceted navigation example to quickstart Sub-task Closed Ard Schrijvers  
      17.
      		 Ranges with resolution week fail for descendant nodes Sub-task Closed Ard Schrijvers  
      18.
      		 Add possibility to limit the number of facetvalues in tree. This limit needs to be configurable *per* facet Sub-task Closed Sylvain Pélissier (Inactive)  
      19.
      		 Add caching to populateFacetValueCountMap in FacetedNavigationEngineThirdImpl Sub-task Closed Sylvain Pélissier (Inactive)  
      20.
      		 Indexing performance and Lucene storage improvement: only index facet for nodes containing at least a hippo:paths property Sub-task Closed Sylvain Pélissier (Inactive)  
      21.
      		 Make the facet value nodes be sorted in a customizable way Sub-task Closed Sylvain Pélissier (Inactive)  
      22.
      		 Make the free drill path faceted navigation customizable wrt which facets are available at which moment Sub-task Closed Sylvain Pélissier (Inactive)  
      23.
      		 Guided drill paths: create possibility to configure that after a facet has been used, it does not show up again Sub-task Closed Sylvain Pélissier (Inactive)  
      24.
      		 Support multiple scopes (docbases) for faceted navigation Sub-task Closed Ard Schrijvers  
      25.
      		 Add free text search support Sub-task Closed Sylvain Pélissier (Inactive)

      0%
      Original Estimate - 2 days
      Remaining Estimate - 2 days
      26.
      		 Add performance logging Sub-task Closed Ard Schrijvers  
      27.
      		 By default add a internal filter skipping draft documents in faceted navigation Sub-task Closed Ard Schrijvers  
      28.
      		 For filters and free text search, use standard Lucene QueryParser instead of Jackrabbit query parser Sub-task Closed Arje Cahn (Inactive)  
      29.
      		 Do not use org.apache.jackrabbit.spi.Name in the FacetedNavigationEngine interface, but replace it with the qName string representation Sub-task Closed Ard Schrijvers  

      Activity

        People

          jsheriff Junaidh Kadhar Sheriff
          aschrijvers Ard Schrijvers
          Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

          Dates

            Created:
            Updated:
            Resolved:

            Time Tracking

              Estimated:
              Original Estimate - 2 days
              2d
              Remaining:
              Remaining Estimate - 2 days
              2d
              Logged:
              Time Spent - Not Specified
              Not Specified