Loans (UXPROD-788)

[UXPROD-946] Loans in-app report: Items that are claim returned Created: 13/Jun/18  Updated: 07/Mar/22

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Loans

Type: New Feature Priority: P3
Reporter: Emma Boettcher Assignee: Cheryl Malmborg
Resolution: Unresolved Votes: 0
Labels: appreport, cap-mvp, cf_candidate, loans, po-mvp, q4-2019-at-risk, q4-2019-spillover, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-944 Loans in-app report: Items that are i... Closed
Defines
is defined by CIRC-784 Backend: Claimed returned in-app repo... Open
is defined by CIRC-785 Backend: Claimed returned in-app repo... Open
is defined by CIRC-786 Backend: Claimed returned in-app repo... Open
is defined by UIU-1226 Claimed returned in-app report: Exist... Closed
is defined by UIU-1884 Claimed returned in-app report: permi... Closed
is defined by UIU-1227 Claimed returned in-app report: Call ... Blocked
is defined by UIU-1228 Claimed returned in-app report: Item ... Blocked
is defined by UIU-1229 Claimed returned in-app report: Physi... Blocked
Duplicate
is duplicated by UXPROD-2919 On Claim Returned Report in Users App... Closed
Relates
relates to UXPROD-867 Reporting: In-App Reports Open
relates to UXPROD-532 Claim returned: track searches Analysis Complete
Potential Workaround: Querying LDP for list of items that are claim returned. May lead to redundant work (searching for items that have already been found) if data in LDP is old.
Epic Link: Loans
Front End Estimate: Medium < 5 days
Front End Estimator: Emma Boettcher
Back End Estimate: Large < 10 days
Back End Estimator: Emma Boettcher
Development Team: Vega
PO Rank: 101
PO Ranking Note: Likely ranked low because UXPROD-532 has a list of claim returned items and additional functionality, but UXPROD-946 is more feasible and covers one of the most necessary parts of UXPROD-532.
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R2
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R2
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R5

 Description   

Current situation or problem:

  • Export of claimed returned items contains minimal information. Including more information about call number, item status date (i.e., when something became claimed returned), and physical description would make searching for these items more thorough.
  • UIIN-1226 Closed created a bare-bones version of this report, available in honeysuckle release

In scope
Add the following information to the claimed returned CSV export:

  • call number fields
  • item status date
  • physical description

Out of scope

  • UXPROD-532: viewing the list of claimed returned items in FOLIO and being able to take action on those items from that screen, as opposed to a CSV export
    • moving the CSV export of claimed items to that screen so that the user can search & filter the claimed returned items they'd like to search for, then export a list of only those items

Use case(s)

  • Patron claims they've returned an item. The library isn't sure whether to believe them, so they search for the item in the stacks to see if it was shelved without having checked it in.

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Erin Nettifee [ 27/Mar/19 ]

This seems duplicative of https://folio-org.atlassian.net/browse/UXPROD-532 in terms of in-app / circ staff functionality. Duke could see the usefulness of this as a general report, but if 532 is proceeding, then this report does not need to be an in-app report for us.

Comment by Cate Boerema (Inactive) [ 19/Sep/19 ]

Emma Boettcher are any of these stories dev-ready for Core Functional?

Comment by Cate Boerema (Inactive) [ 19/Sep/19 ]

Oh, I see this is blocked on UXPROD-88 Closed

Comment by Emma Boettcher [ 15/Jun/20 ]

Marc Johnson Cate and I were discussing this and wondering if the backend estimate was a little high - and looking at the history, I see that I added that estimate and it was almost 2 years ago, before any other in-app reports were done (like the overdue loans report, which has a lot of the same data as this). Do you think this is an XL or should I knock it down to L or M?

Comment by Marc Johnson [ 16/Jun/20 ]

Emma Boettcher

Do you think this is an XL or should I knock it down to L or M?

We still don't really have a consistent way to do in-app reports. I don't mind lowering the estimate, however this might be offset by changes in policy around performance testing.

Comment by patty.wanninger [ 08/Nov/21 ]

Cheryl Malmborg I have a use case to be able to see items by status, in addition to claims returned , such as missing, withdrawn, etc. These are the statuses that a user can assign manually to the items. The user wants a list of, e.g. missing items by location. Does that need to be a new feature?

Comment by Cheryl Malmborg [ 08/Nov/21 ]

patty.wanninger I don't think I understand the use case. Claims returned is an item status. A claim can be resolved, but the claims returned status cannot be edited in Inventory.

Comment by patty.wanninger [ 08/Nov/21 ]

Cheryl Malmborg I'll ask Charlotte, as these are statuses in inventory, and not related to circ. Thanks.

Generated at Fri Feb 09 00:11:41 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.