2020-12-11 Resource Management Meeting Notes

Jesse Lambertson

In-app usage reporting capabilities for eUsage and Agreements

• graphs and calculations
• working with Index Data
• Goal to display eUsage in Agreements app
• Annika Schröer will open a spot on the wiki for others who want to help and join (WG)
• Kristen Wilson detailed the goals
• agreement lines
• agreement content provider data will be available
• eUsage app allows for this information to be viewed and organized
• The hope is to match kB resources with metadata based on ISSN or ISBN, or something in that sense
  • non-matched titles would be reviewed
  • The hope is that choices would be remembers in order not to have be done again 
• from that chat (

  Is that the Agreement Usage data provider or the Content provider?)

• Question from the chat: (is that information exportable in any way, like as a csv or the like? )
• Yes, the data is downloadable
• Folks need to be aware of integrations whenever significant integrations are made because of impact on agreements app (
• Also, Owen S makes a distinction between local agreements kB vs the larger kB
• Sara asking about the specific framework being organized in the dashboard, what exactly is being displayed, how granular can this information be?
• also download stats and cost-per-download reporting are not clear yet
• 
• 
• harmonizing the databases will be required, we don't want to pull apart things that don't need to be pulled apart
• Not sure yet what EBSCO's eUsage app will be doing
• One option to work with statistics 
• Suggestion to use the LDP for reporting
• 
• flexibility is important, but wanted to focus on a few common reports
• WG will have work on where to focus and where to integrate
• Virginia comments that EBSCO is also working on a eUsage app and yet is not come to the SIG meetings (ERM or RM)
  • Suggested Khalilah be invited to update on what EBSCO is working on
  • Sara, update, EBSCO is working on a Usage Consolidation app that comes together with some FOLIO efforts
  • concern about big changes that might affect core apps (existing FOLIO apps)
    • especially as the FOLIO community grows
  • making sure the community is open and accessible
  • It seems desirable for this information to display in agreements (but for those who don't use it, don't want to cause an issue)
  • Acknowledging a micro-service challenge
    • How to work within the challenges for large open-source projects