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

View status history on item record (Q4 2019 work)

    XMLWordPrintable

Details

    • Large < 10 days
    • Large < 10 days
    • Large < 10 days
    • Medium
    • Hide
      * Item status updating mechanism is in place (and this does not involve creating a new type of record for state derivation, if that is the approach we choose)
      * All existing processes which update the item status are compatible with the mechanism chosen to capture the transition
      Show
      * Item status updating mechanism is in place (and this does not involve creating a new type of record for state derivation, if that is the approach we choose) * All existing processes which update the item status are compatible with the mechanism chosen to capture the transition
    • Concorde
    • 120
    • R2
    • R1
    • R1
    • R1
    • R1
    • R1
    • R2
    • R2
    • R1
    • R1
    • R1
    • R1
    • R1

    Description

      As an item's status changes, its previous statuses (and the date, place, and operator that applied them) can be recorded in an action table to help staff troubleshoot and to see the history of items. Lives in Inventory. May also include history in various workflows depending on how that information is stored.

      February 2019: Show last time touched on item record, but don't need to have extensive history for this in Inventory so long as the full history can be accessed quickly.

      Item record: most recent check in section (UIIN-749), maintain item status date (UIIN-486)

      Status history/audit app:

      • Create new item for existing holdings record (--> Available)
      • Check in the item (--> Awaiting pickup, In transit, Available)
      • Check out the item (--> Checked out)
      • Mark item as missing (--> Missing)
      • Open purchase order to create item (--> On order)
      • Receive purchase order (--> In process)
      • Paging an available item (--> Paged)
      • Expired request on an item (--> Awaiting pickup)

      Excluded from that timeline: edits to item record, some loan actions (renew, change due date), creating any kind of request on an item besides paging an available item
      Included: actions in the above list, even if they don't change the status (e.g., scanning an Available item in the Check In app --> Available)

      Other anticipated actions that would affect status:

      • Marking a (loaned) item claim returned or lost (through interaction in Users)
      • Time passing (Recently returned items becoming Available, Checked out items becoming lost when they're past their due dates - the latter is imminent, the former is not)
      • All fines/fees closing for a lost item (--> Lost and paid)
      • Marking an item as In process, Withdrawn, or Long missing
      • Renewing an item (if it's lost, will change the status to Checked out)

      For these actions, need to capture: status (at end of action), who is doing the action, when, associated service point (for check in/check out actions), and link back to at least item details, assuming loan details/patron details/request details is going to lead to issues.

      Completed in Q4:

      • Backend work to show last check in on item record
      • Work to maintain item status date when record was edited

      TestRail: Results

        Attachments

          1. At a glance (2).png
            265 kB
            Emma Boettcher
          2. Status history.png
            162 kB
            Emma Boettcher

          Issue Links

            Activity

              People

                ecboettcher Emma Boettcher
                ecboettcher Emma Boettcher
                Emma Boettcher Emma Boettcher
                Aditya matukumalli Aditya matukumalli
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases