Reporting: LDP-based Reports (UXPROD-1319)

[UXPROD-887] Cross app report: Journal Title List Created: 11/Jun/18  Updated: 09/Dec/21

Status: Draft
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: Unresolved Votes: 1
Labels: dwreport, inventory, metadatamanagement, reporting, resourcemanagement
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: 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): ID310
Report Contact(s):
Herkt-Januschek, Claudius
Report Functional Area(s):
Metadata Management
PO Rank: 18
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
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: Leipzig (Full TBD): R4
Rank: Leipzig (ERM Aut 2019): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Purpose: An ad-hoc report. Location changes, preservation actions, Cancellation, Weeding

Parameters to the report:
Instance record: Subject heading and/or Classification
Holdings record: Shelf mark
Item record: Material type

Link to sample (hamburg): https://drive.google.com/file/d/13IYyzPp1p7zXkGMzRT18P-hFk4esYgW2/view?usp=sharing

This could potential be a cross app report: Cataloguing and Circulation (and ERM)

Assignee: Charlotte?, Cate?, Owen?

Notes from Reporting Master spreadsheet:
Legacy System Data Element Sources: Title, internal and external IDs (ISSN, ZDB), link to Journal database ZDB, further information from catalogue (eg link to online/digitized version, preservation notes), holding information (existing volumes, location), circulation data

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 Kristin Martin [ 30/Apr/19 ]

This is a cross-app report and should not be a canned report in Inventory.

Comment by Nassib Nassar [ 04/Sep/19 ]

Please identify an analyst or developer resource to write the SQL report query.

Comment by Charlotte Whitt [ 04/Sep/19 ]

Hi Nassib Nassar - this is a cross-app report and does not belong in Inventory. The rank is very low: Cap plan 18 - so my guess is that this report must be put on hold until after MVP.

Comment by lew235 [ 29/Oct/19 ]

Does anyone know what organization originally contributed this report? I am trying to help create clusters of metadata-related reports. Is this a sort of pick-list that is limited by format? Or a shelf list? Or something different?
(It's not clear to me from the sample data what these data might be used for).

Comment by Herkt-Januschek, Claudius [ 30/Oct/19 ]

Hello Laura, I added this report on behalf of Hamburg (GBV). Journal lists with detailed metadata are needed for several use cases. For example, an overview of subscriptions to identify cancellation cadidates or a shelf list from which candidates for weeding have to be selected.
The task is: for a given set of journals to provide a list of all the relevant information to support well-founded decisions.

Comment by lew235 [ 31/Oct/19 ]

Herkt-Januschek, Claudius Thank you!

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