Page Comparison

Status of eUsage App

-cost per use is the most important report

-in the eUsage app, usage data being collected about a resource from various providers or services 

-in agreements, the way the resource is being ordered, licensed, invoiced, etc. is set up

-no link between eUsage resource and agreements yet

Questions

-is the work better done in LDP or within a FOLIO app?

-mod agreements could do a query against LDP and provide data back to the agreements UI, evaluates the permissions, and performs the query itself

Frequency

-stats not needed in real time; most users gather data monthly

Nassib

-need to think about queries

-might be easier if distribution of queries arranges over

-if small number of attributes, might be more efficient to develop in FOLIO application

-could push data into LDP as needed (faster than overnight)

-FOLIO db needs to respond to request in real time; LDP is queried by analysts; use of LDP could create a latency in providing the data

Data Storage Concerns

-cache the data to speed up access?

Proof of Concept

-outline representative query

-set up amount of data needed for good test-

Permissions

-no OKAPI interface to LDP; a permissions system would require developing this

-queries could be direct ODBC queries, but we also need to add the LDP loader to load incremental data

-eUsage can proxy to the LDP

Preparation for next meeting

-mod agreements could do a query against LDP and provide data back to the agreements UI, evaluates the permissions, and performs the query itselfdocument what is needed in a schematic way (e.g., typical query, typical dataset with appropriate size)

-describe data needed, query patterns

Small Workgroup Creates

-Richard and Annika have documented a good use case

-Richard, Nassib, Owen, Annika, Kevin, Matt

Timeline Constraints?

-eUsage wants to finish application by December 2019

-ask Annika for specifics on timing

Next Steps