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

Item state in three components

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Epic Link:
    • Front End Estimate:
      XL < 15 days
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      FE work for other parts of item state is in the XL range, so adding that here for capacity planning.
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      121
    • 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):
      R1
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      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

            is duplicated by

            New Feature - New feature requests UXPROD-1530 Items needed for staff workflow needs

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

            New Feature - New feature requests UXPROD-1590 Items fulfilling staff workflow needs

            • TBD - To be determined
            • Open
            relates to

            New Feature - New feature requests UXPROD-283 View status history on item record (Q4 2019 work)

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

            New Feature - New feature requests UXPROD-2181 View last check in on item record

            • 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. UIREQ-101 Requests - capture action information during edit

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

            New Feature - New feature requests UXPROD-92 Check-in: Implications to item status

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

            New Feature - New feature requests UXPROD-1731 Ability to change Item status from Inventory (without switching to another app)

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

              Activity

                People

                Assignee:
                ecboettcher Emma Boettcher
                Reporter:
                ecboettcher Emma Boettcher
                Front End Estimator:
                Emma Boettcher Emma Boettcher
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases