Reporting: In-App Reports (UXPROD-867)

[UXPROD-1060] Inventory in-app report: Permanent and/or temporary location Created: 29/Aug/18  Updated: 04/Jul/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Reporting: In-App Reports

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: appreport, inventory, metadatamanagement, reporting, resourceaccess, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-867 Reporting: In-App Reports Open
Epic Link: Reporting: In-App Reports
Analysis Estimate: Medium < 5 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: Large < 10 days
Front End Estimator: Niels Erik Nielsen
Front-End Confidence factor: Low
Back End Estimate: XL < 15 days
Back End Estimator: Niels Erik Nielsen
Estimation Notes and Assumptions: This is VERY low confidence.
We haven't done any canned reports yet so it's difficult to do any estimate. The assumption here will be that the output will be both in the user interface (to do the clickable list) and as a CVS file.
Requirements to be discussed further with RA-SIG, MM-SIG and Reporting SIG.
These reports might reach the limit of number of records the system can return.
Development Team: Prokopovych
PO Rank: 38
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R5
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R4
Rank: Leipzig (ERM Aut 2019): R5
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R5

 Description   

Purpose: An ad-hoc report. It has been considered having filter on permanent and temporary location. And this might be solved like that when implementing Advanced Search ( UIIN-1920 Closed ).

As an interim solution then an in-app report could be the way to solve how to do a list of items on a given Permanent and/or temporary location, when doing collection management, and possible need to do location deletion. Locations that are in use in a holding or item can't be deleted. With the generated list, then you can click a link to view all holdings or items that use that given location, and then you can reassign them to another location.

Requirements and solution as Inventory in-app report to be discussed further with the RA-SIG)

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 Theodor Tolstoy (One-Group.se) [ 19/Sep/18 ]

Chalmers prefers a proper Seach solution over in-app reports

Comment by Cate Boerema (Inactive) [ 05/Dec/18 ]

Removing Q1 2019 fix version due to limited capacity in Q1 2019.

Comment by lew235 [ 02/Aug/19 ]

This info can be gleaned from the Collections Use LDP report:
See: https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=4493713

Comment by Lisa Sjögren [ 28/Mar/22 ]

Have the conditions/limitations/possibilities for this changed with the implementation of Elastic Search – and/or the implementation of filter & export in some other apps? Charlotte Whitt Magda Zacharska

It would be great if this could be covered by something that resembles the very flexible and intuitive "filter and export select fields from result" feature that exists in, for example, the Orders app. That would provide librarians with a simple way of designing and exporting lists (for e.g. stock-taking or weeding) using the familiar Inventory search/filter/facets.

Comment by Charlotte Whitt [ 29/Mar/22 ]

Lisa Sjögren - this is probably something you should raise with the Reporting SIG.

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