Meeting Time:    8 am EST /  2 pm CET / 1 pm UK

Call in Number:     https://zoom.us/j/995679876 

Meeting URL:  https://zoom.us/j/995679876 Password needed: please see link below

https://folio-org.atlassian.net/wiki/display/COMMUNITY/FOLIO+Meetings+with+Zoom

ERM SIG Folio Wiki: https://folio-org.atlassian.net/wiki/display/ERMSIG/

Google Folder: https://drive.google.com/drive/folders/17X3tr6siZH8iS07kGcjAqUNl01zVrJmB

Terms and definitions: https://docs.google.com/document/d/1vue-mbcULpZivWu69a7nAZEdC-H2yXPQqSblbL_0J6U

Slack Channel: # erm-team

Agenda Jan 26th 2022

Convener: Martina T.

Notetaker: Martina S.

Housekeeping

• All: Please edit the attendees list below and indicate when you are there!

• Next ERM meeting:  Feb 2nd

• all questions and topics for the ERM implementers meeting can be posted on this confluence page: https://folio-org.atlassian.net/wiki/x/SABS

• Open discuss posts: right now no new posts regarding erm

• PC minutes Jan 13th

• PC minutes Jan 20th

Agenda items

1. Development progress -  ERM Sprint 132

2. Presentation on eUsage reports functionality (Annika)

Minutes

Development progress

• moving towards feature freeze for Lotus - outstanding functionality will be wrapped up

• main piece of work on local KB and matching processes for PTIs and PCIs

• move IDs between title instances - will at least have an API; hopefully UI as well

  • primary route: corrections in external source

  • would be a supplementary option on a title by title basis

  • possible as bulk edit via API

• Benjamin A. in chat: very excited absolut KB corrections!!! .... I alone have accumulated a couple  of awkward errors

• Peter M. in chat: It needs to be title-by-title, and also at database-by-database level. Because not every database has the same regular mistakes to be fixed. At Serials Solutions we built a Rules Management Module to address this core problem. It was, in my opinion, what people were ACTUALLY paying for, even if they didn’t realize it.  And package-by-package, at times, as Owen points out
  
  

eUsage reports

• extension for eUsage and agreements that combines data from the two and sometimes invoices

• project funded by SLUB Dresden, implemented by Index Data

• released for the Kiwi release

• if libraies have plug-in running in their system there is an eUsage reports accordion on the agreement

• there are statistics

• several reports are implemented

• more reports can be added in the future; the ones that are there were identified as the most important ones

  • use over time

  • use over time, grouped by publication year

  • use over publication year, grouped by time

  • cost per use (including conversion to system currency)

• period of use: start and end month

• different scales possible, different stacks

• can download reports as csv

• there is a documentation of all the different reports; done by the PO Kristen Wilson; including e.g. parameters

• where does the data come from: everything needs to start with the usage data

• need agreement and usage data provider connected to it

• harvesting configuration in eUsage

• plug-in needs counter 5

• best to configure the harvester

• needs data inside local KB; agreement lines need to be configured

• new accordion in eUsage app: Matching summary; for seeing results of matching resources of counter statistic with titles in Local KB

• matches can be viewed, edited or ignored

• when editing: a new title can be selected from the ersources in the internal KB

• for cost per use: cost data is needed; taken from POL that is linked from the agreement line; linked to the POL is the invoice line

• users can choose whether Open Access should be included or not in reports

• Analyse agreement button to manually reload the report:

• because most data is quite unstatic; titles can change, invoices can be paid it made no sense to set a specific timeframe to reload

• Felix in chat: For Annika: From your experiences, what is the spread between matches and non-matches?

  • Annika: can't really answer this; did not test with real data; it is a Kiwi feature and in Leipzig Kiwi is not used yet

  • only working with test system so far

  • seems to match quite well

• feedback from Eric: really impressive functionality

• will this work with eholdings as well? 

  • Annika can't asnwer that because that would need technical input from eholdings side

• Annika loves to hear about feedback when people start testing

• technical work as done by Index Data and KristenWilson as PO can give answers as well

• Here's the eUsage Reports documentation page I showed briefly, if anybody is interested in the details: eUsage Reports Documentation
  The functionality is available since Kiwi.

Chat

Von Benjamin Ahlborn an alle 02:08 PM
very excited absolut KB corrections!!!
Von Peter McCracken an alle 02:10 PM
It needs to be title-by-title, and also at database-by-database level. Because not every database has the same regular mistakes to be fixed. At Serials Solutions we built a Rules Management Module to address this core problem. It was, in my opinion, what people were ACTUALLY paying for, even if they didn’t realize it.
And package-by-package, at times, as Owen points out
Von Benjamin Ahlborn an alle 02:11 PM
.... I alone have accumulated a couple  of awkward errors
Von Felix Hemme (ZBW) an alle 02:33 PM
For Annika: From your experiences, what is the spread between matches and non-matches?
Von Jack Mulvaney an alle 02:39 PM
This looks really great, I'm very jealous of the internal KB users right now
Von Martina Schildt an alle 02:39 PM
Great functionality!
Von Julie Brannon (she/her) an alle 02:40 PM
Exciting!
Von Sabrina Bayer an alle 02:40 PM
It looks very great :)

Attendees list