Reporting: LDP-based Reports (UXPROD-1319)

[UXPROD-2379] ERM-Agreements Count Cluster Created: 14/Apr/20  Updated: 06/Jun/23  Resolved: 06/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: Sharon Beltaine Assignee: Axel Dörrer
Resolution: Done Votes: 0
Labels: po-mvp, report-cluster, reporting, team-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by REPTOOLS-177 LDP 1.2 features (placeholder) Open
Defines
is defined by LDPQURY-35 Prototype for ERM Count Cluster Open
Relates
relates to REP-58 Digital stocks, altogether (without e... Open
relates to REP-59 Digital stocks, among these: commerci... Open
relates to REP-61 Digital stocks, of those: digital aud... Open
relates to REP-62 Digital stocks, of those: databases a... Open
relates to REP-65 Journals and newspapers in electronic... Open
relates to REP-66 Journals and newspapers in electronic... Open
relates to REP-67 Journals and newspapers in electronic... Open
relates to REP-69 Other costs for journals and newspape... Open
relates to REP-70 Journals and newspapers in electronic... Open
Epic Link: Reporting: LDP-based Reports
Back End Estimate: XXL < 30 days
Development Team: Reporting
Report Functional Area(s):
Resource Management
Cap Plan Fix Version (DO NOT CHANGE): R2 2021
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R3
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R2
Rank: 5Colleges (ERM Jun 2020): R2
Rank: GBV (MVP Sum 2020): R2
Rank: Lehigh (MVP Summer 2020): R3
Rank: Leipzig (ERM Aut 2019): R2
Rank: TAMU (MVP Jan 2021): R3
Rank: U of AL (MVP Oct 2020): R4

 Description   

This is the report cluster for reports used to generate counts in the functional area of ERM (Electronic Resource Management). This will not cover e-usage data.

 

Query done for Metadb and the use of the internal Knowledgebase, see:
https://github.com/folio-org/folio-analytics/tree/main/sql_metadb/report_queries/erm/agreement_count

 



 Comments   
Comment by Axel Dörrer [ 03/Nov/20 ]

Note for eHoldings users:
At the current stage of development, no data from eHoldings can be accessed via the LDP. Currently, the POs and ERM subgroup of the Reporting SIG are working on possible solutions.

Comment by Marie Widigson [ 16/Dec/20 ]

So, as a eHoldingsuser, this feature should be ranked R5?

Comment by Axel Dörrer [ 17/Dec/20 ]

Marie Widigson No, not necessarily. It depends how eHoldingsusers will do their reportings on ERM.
If you are e.g. using a reporting service within the EBSCO portfolio this probably will not affect you. Otherwise if you are going to broadly use the LDP for FOLIO reporting as well as in ERM you might consider to have that ranked higher.

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