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

Inventory. Result list Refined display rules. Display Resource title in MCL and Sort on Index title

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Analysis Estimate:
      Very Small (VS) < 1day
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      Large < 10 days
    • Confidence factor:
      Medium
    • Estimation Notes and Assumptions:
      Will likely required a new derived property for the effective title, in order to do sorting. May involve changes to the keyword searching.
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      131
    • Kiwi Planning Points (DO NOT CHANGE):
      1
    • PO Rank:
      133
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • 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: FLO (MVP Sum 2020):
      R1
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: Grand Valley (Full Sum 2021):
      R1
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: MO State (MVP June 2020):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: Trinity College (Jun 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      Charlotte: Update 6/29/2021:
      New work implementing the title sort by Index title is to be implemented using Elasticsearch - MSEARCH-136 In progress.

      For Inventory then this will be implemented automatically when shifting the current search solution using PostgreSQL, JSONB columns, CQL and RAML Module Builder to be using Elastic Search - UXPROD-3046 NFR: Inventory. Swap from search tool PostgreSQL to Elasticsearch

      • - - - - - - - - - - - - - - - -

      Laura Daniels:
      MM SMEs have expressed a desire, that is, to focus on the longer-term goals rather than interim goals if they can't be built on directly. The lack, for instance, of call number in the search results display of the holdings segment, would not be addressed by the improvements in the JIRA features listed below. So I agree with you, @charlotte, that putting resources toward the hierarchical display instead (UXPROD-491), if at all possible, is in our best interest.
      Charlotte Whitt: See more comments added 2/23/2020 in UXPROD-491.
       

      • - - - - - - - - - - - - - - - -

      This feature had original a wider scope, but is now narrowed to only include the work on use the Index titel, alternatively Resource title, in the display of the Result list - the library ranking is kept from the original feature, which previously included all relevant refinements of the result list for the MVP

      The cap.plan team has asked for getting the different improvements split into their own feature:

      1. UXPROD-1634 (index title/title)
      2. UXPROD-2667 (sort on contributor, when more than one contributor is listed)
      3. UXPROD-2668 (Adding instance HRID)
      4. UXPROD-2669 (Adding resource type)
      5. UXPROD-2670 (Adding format)
      6. UXPROD-2671 (Adding edition)
      7. UXPROD-2703 (Adding publication date)

      Overview: The result list has for the basic alpha implementation been: Resource title, and all listed contributors. With the refined use of elements implemented for beta, we need to configure the results in the Result list based on:

      1) If there is an Index title, the title with no leading article, will display, and not the Resource title
      2) If no Index title, the Resource title displays
      3) After the Index title/Resource title, the primary contributor is displayed.

      Notes:
      This is critical for the results list display to be useful for any searches, displaying the title data of the instance record.

      Usecase:
      As a librarian who is searching in Inventory.
      I want the search results to display the Index title (the title with no leading article), when available, instead of the Resource title.
      So that I when having a large result list can avoid having screens after screens starting with display of titles starting with , A ..., The ..., etc.
      See screen dump from Bugfest-Goldenrod, when searching on Keyword: water

      Here is a default title sort:
      https://bugfest-honeysuckle.folio.ebsco.com/inventory?qindex=querySearch&query=title%3D%3Ddave%20%2A&sort=titleNow change the `sort=title` part of the URL to `sort=indexTitle` and the title Dave moves all the way to the top:
      https://bugfest-honeysuckle.folio.ebsco.com/inventory?qindex=querySearch&query=title%3D%3Ddave%20%2A&sort=indexTitle

       

      Out of scope:

      1. Future need: customizable results lists

      Documentation:

      1. Slide deck reviewed by MM-SIG 10/1/2020 and 10/8/2020 - https://docs.google.com/presentation/d/1kDumWwhNfP7Mq9hZ5q4O1cnbg_BY4ILgKbjBWOO4Xso/edit#slide=id.p
      2. Survey send out on the #metadata-management channel 10/7/2020 - https://docs.google.com/presentation/d/13Dt-Tkr_nzgU2Oxb044J4d3RSxxk4R-0lq-AlKXIItg/edit#slide=id.g9998cb799b_2_0

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                charlotte Charlotte Whitt
                Reporter:
                charlotte Charlotte Whitt
                Analysis Estimator:
                Charlotte Whitt Charlotte Whitt
                Front End Estimator:
                Michal Kuklis Michal Kuklis
                Back End Estimator:
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases