Reporting: LDP-based Reports (UXPROD-1319)

[UXPROD-2215] MM-LDP-MARC-Table Cluster Created: 20/Dec/19  Updated: 13/Jun/23  Resolved: 13/Jun/23

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

Type: New Feature Priority: TBD
Reporter: Vandana Shah Assignee: Kevin Walker
Resolution: Won't Do Votes: 0
Labels: po-mvp, report-cluster, reporting, team-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to REP-247 Syntactical correctness report Closed
relates to REP-248 Missing fields report Closed
relates to REP-249 Dependencies report Closed
relates to REP-250 Relationship designator (Quality Cont... Closed
Epic Link: Reporting: LDP-based Reports
Development Team: None
Report Functional Area(s):
Metadata Management
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R5
Rank: FLO (MVP Sum 2020): R2
Rank: GBV (MVP Sum 2020): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

MARC report; This is a category of reports with the ability to interrogate the data at a granular, element-level.If we can interrogate the data in a way that satisfies this requirement, REP-247 Closed , REP-249 Closed , REP-248 Closed , and REP-250 Closed will be met. They are all MARC-date specific, and sample queries will be built once the MARC data are available for testing in the LDP.



 Comments   
Comment by Marie Widigson [ 16/Dec/20 ]

Can these reports be used with Inventory data also when no FOLIO MARC-cataloging tools are used? If so, this would be interesting for us.

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