Reporting: LDP-based Reports (UXPROD-1319)

[UXPROD-892] Revision of the inventory per location Created: 12/Jun/18  Updated: 16/Sep/20  Resolved: 04/Sep/19

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

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Sharon Beltaine
Resolution: Duplicate Votes: 0
Labels: inventory, metadatamanagement, reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to REP-189 Shelf List by Location (item level) Open
relates to UXPROD-867 Reporting: In-App Reports Open
Epic Link: Reporting: LDP-based Reports
Analysis Estimate: Large < 10 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: XL < 15 days
Front End Estimator: Charlotte Whitt
Front-End Confidence factor: Low
Back End Estimate: Medium < 5 days
Back End Estimator: Charlotte Whitt
Estimation Notes and Assumptions: We haven't done any canned reports yet so I have no idea what will be involved.
Development Team: Reporting
Report ID (pre-May 2019): ID315
Report Contact(s):
Uschi Klute
Report Functional Area(s):
Metadata Management
PO Rank: 26
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R2

 Description   

This feature will more likely be done as a Dataware house solution. See: REP-189 Open . (Meeting with Sharon Beltaine, Eric Pennington, Charlotte Whitt on 5/16/19)

Purpose: of this report is to check the actual library stock in order to locate missing or damaged material. An ad-hoc report (on demand). Revision of the (book) inventory. This report requires real time data access. (To be described further)

Parameters to the report:
Per location.

Notes from Reporting Master spreadsheet:
Legacy data elements: shelf mark, barcode, title, author, year.
FOLIO data elements: Item Call number, Item barcode, Resource title, Contributor, Publication date (year).

Definition of Inventory In-app reports:
A report which is available from within the Inventory application itself. The in-app report are using the live data being created and stored in the Inventory module.

Document on Wiki: https://folio-org.atlassian.net/wiki/display/RPT/In-App+vs.+Data+Warehouse+Reports



 Comments   
Comment by Erin Nettifee [ 08/Apr/19 ]

Is this a shelf reading report? If so, it needs the item state as an additional field, as well as material type. It's unclear as to what this report would actually be for.

Comment by Charlotte Whitt [ 09/Apr/19 ]

Holly Mistlebauer - would you be able to provide further input? See Erin Nettifee comment above. Thanks much.

Comment by Sharon Beltaine [ 29/Apr/19 ]

Uschi Klute has noted that the purpose of this report is to check the actual library stock in order to to locate missing or damaged material.

Comment by Uschi Klute [ 29/Apr/19 ]

Sharon Beltaine that's right - many libraries take an item list for these purposes. So the best use of this list would be having also loan data.
Otherwise you don't know whether the gap in the shelf is caused by a book loss or whether the book is simply borrowed.

Comment by Charlotte Whitt [ 29/Apr/19 ]

Emma Boettcher - I have added you as watcher on this story, while access to loan data is relevant for this report as well. See Uschi Klute's comment above.

Comment by Kristin Martin [ 30/Apr/19 ]

It sounds like there is functionality involved (updating Inventory from report) as opposed to simply a report.

Comment by lew235 [ 08/Aug/19 ]

Does this really require "live" data or can this be accomplished in LDP? Sharon Beltaine

Comment by Sharon Beltaine [ 04/Sep/19 ]

This report is covered by REP-189 Open for the LDP, so closing this issue as duplicate.

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