Uploaded image for project: 'mod-search'
  1. mod-search
  2. MSEARCH-323

Browse: Populating of call-numbers by mod-search can be disabled

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P2
    • Resolution: Done
    • None
    • 1.6.2, 1.7.0
    • None
    • Falcon Sprint 136
    • 1
    • Falcon
    • Lotus R1 2022 Bug Fix
    • TBD

    Description

      Purpose/Overview:
      The current implementation of call-number browsing by all schemas allows mod-search to populate new rows from the instance level items if they have shelf keys between the found value by Elasticsearch and the next value.

      Requirements/Scope:

      1. This feature must be configurable by the tenant
      2. It must be disabled by default
      3. Since this feature is controlled by the mod-search, there is no need to run reindex

      Acceptance criteria:

      • Make the population of call-number browsing rows configurable by the tenant
      • Add tests that validates that this feature is disabled by default and can be enabled by tenant

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                pavel_filippov Pavel Filippov
                pavel_filippov Pavel Filippov
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases