Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2806

Create Elasticsearch indexes for Inventory search

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Front End Estimate:
      XXL < 30 days
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Low
    • Development Team:
      Falcon
    • Calculated Total Rank:
      60
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R2
    • Rank: U of AL (MVP Oct 2020):
      R2
    • Score:
      16
    • Showstopper for Summer 2021 Implementers?:
      No
    • Showstopper Comments from Summer 2021 Implementers:
      Hide
      [Steven from Five Colleges: Five College Showstopper based the complexity of our locations] [Magda responded to Steven: Hi Steven Bischof could you provide some use cases where the current implementation of Inventory search is insufficient for Five Colleges' needs?] [Tod from Chicago: The issue for us is around needed improvements to search and search results in Inventory, many of which have become tied to Elasticsearch implementation. The problem with search in Inventory is that there are many cases where the available identifying text is not enough distinguish between the results. Without those needed improvements, we will be having some difficult conversations about whether we can support our workflows.][Shawn & Kay from MI St U. Need efficient search to enable pre-order work, adding cataloging to complicated sets, such as government documents.]
      Show
      [Steven from Five Colleges: Five College Showstopper based the complexity of our locations] [Magda responded to Steven: Hi Steven Bischof could you provide some use cases where the current implementation of Inventory search is insufficient for Five Colleges' needs?] [Tod from Chicago: The issue for us is around needed improvements to search and search results in Inventory, many of which have become tied to Elasticsearch implementation. The problem with search in Inventory is that there are many cases where the available identifying text is not enough distinguish between the results. Without those needed improvements, we will be having some difficult conversations about whether we can support our workflows.][Shawn & Kay from MI St U. Need efficient search to enable pre-order work, adding cataloging to complicated sets, such as government documents.]
    • Showstopper December 11 Meeting Summary:
      Hide
      UPDATE: This feature was changed to NOT be a showstopper given a thin-thread version of UXPROD-2712 is the actual showstopper.
      The understanding by the implementers is that this feature needs to be completed before they can the improved searching that they need (as described in UXPROD-2712). Right now users cannot tell the difference between an ebook and a regular book. Magda, the PO, pointed out that this feature is to implement Elasticsearch in addition to the existing search-it will not be integrated as part of R1 2021. So, we need to figure out what the Iris summer 2021 implementers REALLY need. Charlotte recommends that we look at the user stories that define UXPROD-2712 and decide which ones are 'showstoppers'. We will move the 'showstoppers' to a separate UXPROD feature and estimate that work. This feature would be re-planned for R2 2021.
      Show
      UPDATE: This feature was changed to NOT be a showstopper given a thin-thread version of UXPROD-2712 is the actual showstopper. The understanding by the implementers is that this feature needs to be completed before they can the improved searching that they need (as described in UXPROD-2712 ). Right now users cannot tell the difference between an ebook and a regular book. Magda, the PO, pointed out that this feature is to implement Elasticsearch in addition to the existing search-it will not be integrated as part of R1 2021. So, we need to figure out what the Iris summer 2021 implementers REALLY need. Charlotte recommends that we look at the user stories that define UXPROD-2712 and decide which ones are 'showstoppers'. We will move the 'showstoppers' to a separate UXPROD feature and estimate that work. This feature would be re-planned for R2 2021.
    • Showstopper Capacity Planning Team Recommendation:
       

      Description

      Current situation or problem:

      The existing inventory search does not provide enough flexibility in building the search criteria, does not perform as expected when searches in large collection takes long to return the data. Also, in searches that have more than 1000 records fulfilling the search, the count of the matching records is incorrect.

      In scope
      Searches against inventory instances, holdings and items:

      Instance Holdings Items
      Keyword search (title, contributor, identifier) Effective location Item Status
      Effective location Holdings permanent location Effective location
      Language Suppress from discovery Holdings permanent location
      Resource type   Material type
      Format   Suppress from discovery
      Mode of issuance    
      Nature of content    
      Staff suppress    
      Suppress from discovery    
      Date created (from, to)    
      Date updated (from, to)    
      Source    

      Out of scope

      1. Other than inventory records searches
      2. Updates to existing inventory search.

      Proposed solution/stories

      1. Define mappings that will determine

      • which fields should be treated as full text search fields
      • which fields contain numbers and dates and their format
      • custom rules for dynamically added fields

      2. Define approach to text analysis (tokenization and normalization)

      Links to additional info

      Questions

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                magdaz Magda Zacharska
                Reporter:
                magdaz Magda Zacharska
                Front End Estimator:
                Magda Zacharska Magda Zacharska
                Back End Estimator:
                Magda Zacharska Magda Zacharska
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases