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

Remember location filter state as you move between campus / library / location

    XMLWordPrintable

Details

    • XL < 15 days
    • Firebird
    • 0
    • R5
    • TBD

    Description

      Current situation or problem: When creating locations, or looking up information about locations, libraries have to frequently move between the four areas of locations (institution, campus, library, location).

      If you need to move among campus, library, and location, the dropdowns reset each time, and you have to reselect desired values.

      It would be a great help to usability if the values could be "remembered" and the drop-downs not reset.

      In scope

      • Changes to the view pane for Settings > Tenant > Campuses, Settings > Tenant > Libraries, Settings > Tenant > Locations

      Out of scope

      • Changes to the location schema

      Use case(s)

      • A library is configuring ten new locations for use with remote storage, with two locations at one library, three locations at another library, and five locations at a third library associated with a different campus. Each time they move to the library view pane, and each time they move to the campus view pane, FOLIO should remember the previous selection, so that they only have to change the selection if the desired value has changed.

      Proposed solution/stories

      Links to additional info

      Questions

      • Do we want different behavior if we go from, say, Settings > Tenant > Location setup > Campuses to an app, versus if we stay within the Settings > Tenant > Location setup tree?
        Or perhaps to have the state persist only if you are within Settings?

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                enettifee Erin Nettifee
                enettifee Erin Nettifee
                Vadym Shchekotilin Vadym Shchekotilin
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases