Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Inventory in-app report: Permanent and/or temporary location

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).

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

Priority

Labels

Fix versions

None

Development Team

Prokopovych

Assignee

Solution Architect

Parent

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Charlotte Whitt March 29, 2022 at 11:56 AM

- this is probably something you should raise with the Reporting SIG.

Lisa Sjögren March 28, 2022 at 10:27 AM
Edited

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?

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.

Laura E Daniels August 2, 2019 at 3:34 PM
Edited

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

Cate Boerema December 5, 2018 at 2:34 PM

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

Theodor Tolstoy (One-Group.se) September 19, 2018 at 12:08 PM

Chalmers prefers a proper Seach solution over in-app reports

Details

Reporter

PO Rank

38

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.

Analysis Estimate

Medium < 5 days

Analysis Estimator

Front End Estimate

Large < 10 days

Front End Estimator

Front-End Confidence factor

Low

Back End Estimate

XL < 15 days

Back End Estimator

Rank: FLO (MVP Sum 2020)

R4

Rank: 5Colleges (Full Jul 2021)

R4

Rank: Cornell (Full Sum 2021)

R2

Rank: Chalmers (Impl Aut 2019)

R5

Rank: GBV (MVP Sum 2020)

R5

Rank: hbz (TBD)

R4

Rank: Hungary (MVP End 2020)

R1

Rank: TAMU (MVP Jan 2021)

R2

Rank: Chicago (MVP Sum 2020)

R4

Rank: Leipzig (ERM Aut 2019)

R5

Rank: U of AL (MVP Oct 2020)

R5

Rank: Leipzig (Full TBD)

R4

Rank: Lehigh (MVP Summer 2020)

R4

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created August 29, 2018 at 11:33 AM
Updated July 4, 2023 at 6:10 PM
Configure
TestRail: Cases
TestRail: Runs