Reporting: LDP-based Reports (UXPROD-1319)

[UXPROD-2027] RA-Missing In Transit Cluster Created: 28/Aug/19  Updated: 11/May/21  Resolved: 22/Jun/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Reporting: LDP-based Reports

Type: New Feature Priority: TBD
Reporter: Angela Zoss Assignee: Angela Zoss
Resolution: Done Votes: 0
Labels: po-mvp, report-cluster, reporting, team-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by LDPQURY-5 SQL query for Missing Items report Closed
Relates
relates to REP-190 Missing in Transit Report Closed
Epic Link: Reporting: LDP-based Reports
Back End Estimate: XXL < 30 days
Development Team: Reporting
Report Functional Area(s):
Resource Access
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R2
Rank: GBV (MVP Sum 2020): R2
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R1

 Description   

Query currently being updated to use LDP derived tables; see:
https://github.com/folio-org/folio-analytics/issues/187



 Comments   
Comment by Angela Zoss [ 24/Jan/20 ]

what is a missing item?

two possible reports:
state is in transit, has been for certain amount of time
for missing items themselves, not a distinction between item state of "missing" and "really missing for a long time", might also want a report of missing for a year to suppress or reorder (include a date range)

this may cross with a collection development report as well, looking for replacement possible

field that might be useful: last check-in for item (will be released soon - will say when and where item was last checked in)

for missing in transit, need: service desk where it was last touched and when, its permanent location, and its destination

where would we find destination - pick-up location, or maybe in requests; primary service desk associated with item's effective location when it was checked in; OR pick-up location for requests

Comment by Simona Tabacaru [ 31/Jan/20 ]

Rank: TAMU (MVP Sum 2020): go-live

Comment by Angela Zoss [ 01/Feb/21 ]

Development completed as part of milestone 1.0 of the LDP.

https://github.com/folio-org/folio-analytics/tree/main/sql/report_queries/items_lost_in_transit

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