Page Comparison

Date

17 Jun 2019

Attendees

• Sharon Markus

• E Pennington
• Former user (Deleted)
• Kevin Walker
• Angela Zoss (Old)
• Matthew Harrington
• Roman Ruiz-Esparza
• Nassib Nassar
• lm15@cornell.edu
• Vandana Shah
• Michael Patrick

...

Resource Access has additional report requirements

App Interaction: ERM + eUsage + Reporting

The eUsage app would like to include a statistics summary that would require joining data between ERM and eUsage modules. Rather than having the app know how to join its data to another app, should they try to leverage the joins that the LDP is already doing? How might that work?

• maybe app would connect to LDP through ODBC and submit query? or maybe we would offer an LDP API?
• problem: they would have to be okay with day-old data, wouldn't be able to harvest COUNTER data and immediately see cost/use
  • this does seem like a concern, people might want pretty fast responses, especially if they're using this stats summary to perform QA on the data they just uploaded
    • (Q: could they do QA on the COUNTER data separate in the app, before it gets joined to cost data?)
  • don't forget, day-old is just for go-live, may eventually be faster
• this should really be a conversation across apps:
  • other apps might (will) need to join data, too
  • if other apps are joining data directly and don't need the LDP, maybe we shouldn't do something special for ERM; but maybe everyone will want to run from the LDP

Note: this meeting also included a tangential but important discussion about non-COUNTER data in the eUsage app. There are many difficulties getting non-COUNTER data to be usable in the app - it could be uploaded, but any calculations are hard to do unless you have the known structure of something like COUNTER. Talked about possibly adding a special uploader to match non-COUNTER data to important fields, but even that might be out of scope. Is there a chance the LDP would be a better option? If the LDP allows for custom data (could be a separate, local data table), then they could at least query against COUNTER and non-COUNTER data using the same database. That might not be perfect for the analysts, though, who would prefer to be able to quickly upload data in whatever format they have (JSON?) and be able to calculate cost/use easily.

Action items

•   add a user story to the JIRA issue about storing effective location in loan (UXPROD-1432)
•   

...