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

Create FOLIO internal Elasticsearch APIs

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Development Team:
      Falcon
    • Calculated Total Rank:
      40
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Score:
      17
    • Showstopper for Summer 2021 Implementers?:
      No
    • Showstopper Comments from Summer 2021 Implementers:
      Hide
      [Steven from Five Colleges: Five Colleges Showstopper based on complexity of locations in the consortium] [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.]
      Show
      [Steven from Five Colleges: Five Colleges Showstopper based on complexity of locations in the consortium] [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.]
    • 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.
      Same as UXPROD-2806.
      Show
      UPDATE: This feature was changed to NOT be a showstopper given a thin-thread version of UXPROD-2712 is the actual showstopper. Same as UXPROD-2806 .
    • Showstopper Capacity Planning Team Recommendation:
       

      Description

      Current situation or problem:
      The currently existing inventory search does not perform as expected on large data sets due to the PostgreSQL limitation.
      In scope:

      1. Build Inventory model:

      • Utility classes and Spring components
      • JSON module structure
      • REST Controller for index endpoints

      2. Index mappings and settings:

      • Utility classes and Spring components
      • EsIndexClient EsIndex/Repository

      3. Inventory indexing:

      • Kafka event listener
      • REST Controller for saving resource endpoint

      4.Search:

      • CQL query parser (EsSearchClient, Query builder for ElasticSearch)
      • RESTController - search endpoints

        TestRail: Results

          Attachments

            Issue Links

            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-620 Domain events sending in inventory-storage for instance

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-639 Domain events sending in inventory-storage for item

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Task - A task that needs to be done. MODINVSTOR-647 Refactor ItemStorageAPI and HoldingsStorageAPI before implementing domain events

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-649 Populate instanceId for new/old item when publishing domain event

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MSEARCH-10 Indexing of instances

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MSEARCH-11 Rancher env setup

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            mentioned in

            Page Loading...

              Activity

                People

                Assignee:
                magdaz Magda Zacharska
                Reporter:
                magdaz Magda Zacharska
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases