Backend - Aged to lost: Check in

SAME SCENARIOS AS WITH DECLARED LOST

1. Scenario
   • Given an item with the status Aged to lost
   • When that item is scanned in the Check In app
   • Then display a confirmation modal
     • Title: Check in Aged to lost item?
     • Body: <title of item> (<material type of item>) (Barcode: <barcode of item>) has the item status Aged to lost.
     • Buttons: Cancel, Confirm (default)
2. Scenario
   • Given the confirm check in modal for an Aged to lost item
   • When the user clicks Cancel
   • Then do not check in the item
3. Scenario
   • Given the confirm check in modal for an Aged to lost item
   • When the user clicks Confirm
   • Then check in the item
     • Display the item on the Check in history screen
     • Close the loan
     • Change the item status from Aged to lost to appropriate status based on service point, item's effective location and presence of requests
4. Scenario
   • Given an item that was aged to lost and was checked in
   • When viewing loan details
   • Then:
     • Lost field should be populated with -
     • corresponding row of action table should have the following values:
       • Action date: <date and time item was checked in>
       • Action: Checked in
       • Due date: <resulting due date from renewal>
       • Item status: <resulting status from check in>
       • Source: <operator who renewed item>
         • format: Last name, firstname middlename
         • link to user profile
       • Comments: <additional information entered at renewal>

Notes
In relation to other check in modals (e.g., multipiece, check in note, item going in transit), the modal described by this story should appear first.