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

Item state in three components

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Duplicate
    • None
    • None
    • None
    • XL < 15 days
    • XXL < 30 days
    • Low
    • FE work for other parts of item state is in the XL range, so adding that here for capacity planning.
    • Prokopovych
    • R4
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1

    Description

      Item state will be summarized by three fields: Availability, Needed for, and Process.

      Availability corresponds to how "status" appears now in the system. Examples: Checked Out, Available.

      Process relates to things being in a staff process, which usually corresponds to the physical state of the item (and making the Availability something like In Process), but occasionally does not (e.g., a Search process).

      Needed for indicates what an item is needed for in the future, and includes some sort of ranking (beyond FIFO) to dictate what is addressed first (e.g., Courses before patron requests).

      Slide deck giving better definitions of these & outlining some of the resulting issues: https://docs.google.com/presentation/d/1DRMg3KPnOnZsw0CUqaJr58tYRJRE-EbjlYDTFKKJbaY/edit?usp=sharing

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                ecboettcher Emma Boettcher
                ecboettcher Emma Boettcher
                Emma Boettcher Emma Boettcher
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases