Reporting: LDP-based Reports (UXPROD-1319)

[UXPROD-1875] Draft a data dictionary for LDP-based reporting Created: 07/Jun/18  Updated: 07/Dec/21

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

Type: New Feature Priority: P2
Reporter: Holly Mistlebauer Assignee: Nassib Nassar
Resolution: Unresolved Votes: 0
Labels: ldp-platform, mandatory, reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-864 Create a reference data warehouse Closed
Epic Link: Reporting: LDP-based Reports
Back End Estimate: XXL < 30 days
Back End Estimator: Nassib Nassar
Development Team: Reporting
PO Rank: 119.5
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R2

 Description   

Documentation of attributes in the Library Data Platform (LDP) database.



 Comments   
Comment by Sharon Beltaine [ 25/Jul/18 ]

The label "mandatory" was just removed from this issue. Data analysts will need a data dictionary to build reports. This is work the data analysts on the Reporting SIG will do. Would someone please explain why the label was removed?

Comment by Holly Mistlebauer [ 25/Jul/18 ]

Sharon Beltaine, there were several reporting issues incorrectly labeled as "mandatory" because they were linked to the wrong epic. Cate was just doing some housekeeping. The data warehouse was part of the gap analysis and this issue probably should have been as well. Given this is needed to use the data warehouse it will be completed as part of that effort. In other words, it will have the same priority as the data warehouse. Sorry for the confusion.

Comment by Holly Mistlebauer [ 25/Jul/18 ]

I just noticed that the development team is listed as EBSCO. This isn't true.

Comment by Sharon Beltaine [ 25/Jul/18 ]

Okay. Thank you. Should we list the development team as the Reporting SIG?

Comment by Holly Mistlebauer [ 26/Jul/18 ]

Reporting SIG isn't one of the options, so I just set it to NONE for now...I will add an issue for the Reporting SIG in the Reporting project right now...

Comment by Sharon Beltaine [ 26/Jul/18 ]

Sounds good. Thanks!

Comment by Cate Boerema (Inactive) [ 24/Aug/18 ]

Hi guys. The reason this was given the wrong dev team is that is was associated with the wrong epic. I will move it from  "Reporting: Analytics and Audit Data Logging for External Reporting" to "Reporting: Reporting SIG Data Warehouse Reference Implementation"

Comment by Cate Boerema (Inactive) [ 03/Sep/18 ]

Holly Mistlebauer and Sharon Beltaine, is this still targeted for completion for the Q3 2018 release? If not, can you please modify the Fix version on this issue? Also, would it make sense to assign this feature to Sharon (as was done with UXPROD-863 Closed ) or, perhaps, to Nassib Nassar? Thanks!

Comment by Holly Mistlebauer [ 19/Sep/18 ]

Theodor Tolstoy (One-Group.se), it will be difficult to use the data warehouse without a proper data dictionary.

Comment by Theodor Tolstoy (One-Group.se) [ 10/Oct/18 ]

I think the reasoning was that most of the reports will not get used until the end of the year, and hence the need for the dictionary at this time. I will raise this one again with Chalmers.

Comment by Cate Boerema (Inactive) [ 10/Oct/18 ]

Depending upon what you mean by "data warehouse", Holly Mistlebauer, Chalmers may not be using it. As far as I know, EBSCO still plans to develop a hosted reporting solution for its customers.

Comment by Sharon Beltaine [ 15/Jul/19 ]

Ranking reviewed at Reporting SIG Meeting 7/15/19. Nassib noted that this is a mandatory issue, so it will be removed from the Ranking process.

Comment by Nassib Nassar [ 12/Aug/19 ]

Moved to LDP 1.2. We will use the FOLIO documentation for 1.0.

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