Versions Compared

Version Old Version 9 New Version Current
Changes made by

Jesse Lambertson

Jesse Lambertson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Minute taker

Jesse Lambertson


Announcements/Updates

Kristin Martin

PC update:

  • Take a look at the SIG notes in the PC council meeting notes
  • Documentation:
    • Come up with a list of  needed documentation
    • will need volunteers to develop documentation framework
    • suggested some interns to help...
    • 'checkin' may be a good template on which to model documentation
    • Start with general context and quirks that might not be noticed right off (Virginia from Duke)
    • first steps?:
      • collect local documentation
      • ERM does not a lot of libraries already live
      • Missouri state might have acquisitions to contribute
      • Also Lehigh
      • Start a google drive to dump documentation that already exists (KM) Link.
    • How to use the interns?
      • expert trains the person who is a writer
      • writer records and uses the recording to start the documentation
      • Interns synthesize and format

In-app usage reporting capabilities for eUsage and Agreements

Kristen Wilson Annika Schröer
  • 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

Other?




  • Other:
    • can't batch produce invoices in Iris
    • uses embedded data in MARC at Uchicago (to help with this issue)
    • The functionality would like to assign this to Juniper
    • Note: technical services depts have been reduced 'due to automation' so if non-batch efforts are being prioritized, then staff will not be able to keep up with all the tasks
    • ref: Lehigh using the API and the batch loader to produce orders and may consider this could be used with invoices and approvals
    • Come back to this...
    • the Order API is working
    • from the chat:

      (Lehigh demo video can be found at https://drive.google.com/file/d/15MJhiCgoMlOBeH0QBOafc_BOKQGcWE7z/view

      Demo is from 12:10-25:00)

...