In-house use

Description

When an item is checked in without an existing loan, the system should record an in-house use of an item. Like checking in a loaned item, this would record the date and time of the check-in, operator and service point, and the item's status would change to recently returned.

As of March 2019, checking in an unloaned item will show the item in check in history, but not record the time or date of use (either in check in history or elsewhere). In addition to adding that to the data being recorded & thus the check in screen, in-house use check ins should be visually distinct from loaned items.

Priority

Fix versions

Development Team

Prokopovych

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Cate Boerema March 16, 2020 at 10:04 AM

Hi . If UICHKIN-162 passes test, please mark this feature closed. Thanks!

Cate Boerema February 3, 2020 at 11:29 AM

Just marking this blocked since we can't finish it until we decide on how we are storing this data (CIRCSTORE-182)

Anya March 29, 2019 at 10:54 PM

Comment from March Meeting : Would not use as defined - Please contact and for UA and FC contact - as well as who was at the table

Cate Boerema April 4, 2018 at 11:56 AM

, would it make sense to assign this to you as part of loans? Would you mind finding out what is meant by this, at least, so we can determine who to assign it to? See attached epic for more details on where this came from.

Done

Details

Reporter

Potential Workaround

If moving forward with status history (UXPROD-283), query that database to see how many times an Available item was checked in, though the count may not be as precise.

PO Rank

101

Estimation Notes and Assumptions

* Organisation is using recently returned status, and so an in-house loan is determined by a transition from "Available" -> "Recently returned" * 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) * Item status history already in place * Dedicated Check In API is in place (rather than just updating a loan, as currently is now) * Performed within a normal check in request (as user does not want to have to check item or loan information prior to taking action) * A check in action is not refused when there is no existing open loan

Front End Estimate

Medium < 5 days

Front End Estimator

Front-End Confidence factor

Low

Back End Estimate

Medium < 5 days

Back End Estimator

Rank: FLO (MVP Sum 2020)

R1

Rank: 5Colleges (Full Jul 2021)

R1

Rank: Cornell (Full Sum 2021)

R1

Rank: Chalmers (Impl Aut 2019)

R4

Rank: GBV (MVP Sum 2020)

R2

Rank: hbz (TBD)

R2

Rank: Hungary (MVP End 2020)

R1

Rank: TAMU (MVP Jan 2021)

R1

Rank: Chicago (MVP Sum 2020)

R1

Rank: MO State (MVP June 2020)

R1

Rank: U of AL (MVP Oct 2020)

R1

Rank: Leipzig (Full TBD)

R1

Rank: Lehigh (MVP Summer 2020)

R1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created January 18, 2018 at 9:45 PM
Updated September 16, 2020 at 9:17 PM
Resolved March 16, 2020 at 1:45 PM
TestRail: Cases
TestRail: Runs