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

Call Number browse - Back-end

    XMLWordPrintable

Details

    • Lotus R1 2022
    • Falcon
    • 0
    • R2

    Description

      Current situation or problem:
      Users are able to search the inventory by call number (eye readable and normalized) but the results list contain only records with matching call numbers and do not provide information on which call number comes before or after .

      In scope

      • Browse by call number
      • Browse all cataloged material that have been assigned a call number
      • The browse list should display preceding, matching and succeeding call numbers
      • Call numbers should be sorted by shelving order but call number should be a base for search/browse
      • The user should be able to navigate forward and backward

      Out of scope

      • Browse by other elements
      • Navigating from the detail screen

      Use case(s)
      https://wiki.folio.org/display/MM/Call+Number+and+Subject+Browse+Use+Cases

      Mockups:
      https://drive.google.com/drive/folders/1duaMQ4jjzQ6I_Ei7c_rSbsGrWdgZZ7wl

       

      Proposed solution/stories

      Links to additional info
      Here are some examples of the Call Number Browse:

      Questions

      • How many preceding and following call numbers should be displayed - it will be made configurable through the properties for the request
      • Should the browse list display records that match each call number - this will be implemented
      • Should there be a count of items for each call number as in the Michigan State and University of Chicago examples - the count of instances matching searched call number
      • Should the results be sortable by other properties than call number - not in scope for Lotus

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                magdaz Magda Zacharska
                magdaz Magda Zacharska
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases