2021-05-07 RM SIG Meeting notes

Announcements/Updates

• Product Council Meeting, 2021-05-06

Kelly Drake is leaving the project. Khalilah G. is taking over.

WolfCon - Jesse K. is working on the schedule. It will be a pared down schedule. There will not be working groups. Will be covering all products under the OLF umbrella.

Bugfest results: Fairly similar to previous tests. More cases that had to be taken up by POs than by people in the community. Solution may be more automated testing.

Link to slides: https://docs.google.com/presentation/d/1NpbCGeWZVOteVO2C3K6PmXifaqryDteLSz8isID9-xg/edit#slide=id.gd83ed12f96_0_85

Project commissioned to provide visualizations of downloads and usage reports from eUsage app in conjunction with the internal knowledgebase. Matching process: Look at titles and try to match them to titles in the knowledgebase. 1) When a new report is loaded, a harvest summary is generated. 2)The status will be "pending review" if there are any unmatched records. If all matched, then "reviewed". 3)You can view the appropriate tab in the report by selecting the linked number (matched, unmatched, etc.).

If a title is matched, app will link to the title in the kb. You can manually edit the match by searching the kb. Once titles are matched, the process should be more efficient moving forward.

Reports and Visualizations: Cost per use report (by agreement line, so you can see the package level and journal level, and includes columns such as order type from PO [ongoing/one-time], link to POL from agreement line, fiscal year start/end, subscription start/end, start/end of COUNTER report [which should match the subscription period], various cost figures down to amount paid divided by the number of unique requests). If there's no subscription year, it defaults to the fiscal year. For databases, it will be the cost per search. Tabs for the different formats (journals, books, databases, etc.).

You'll be able to enter report parameters.

Use over time report: lists all titles from agreement lines even if no COUNTER data present, Controlled and OA_Gold are separated. One visualization is titles by number of uses.

Use by publication year: Requests by date of use; Requests by publication year (the user can enter in a period of use interval, e.g. 5 years. This report is similar to the use over time report.

Reports in context: New accordion →Usage Statistics Preview in Agreements app. This dependency will be optional so if you're not using eUsage, it will no display.

The working group meetings are on Tuesdays at 10am Eastern and are open to anyone who is interested.

The group is planning to have a testing environment.

Invoice/POL matching for migrated orders

Harrassowitz/EBSCO subscription meetings

POL-Invoice line matching presentation is here

As of Iris, can do EDIFACT invoicing. The goal is MARC 9xx will be in Kiwi (not Juniper). The invoice line should match the POL. This matters for one-time orders but is more important for ongoing orders. It's very important to have a usable matchpoint. Matchpoint may vary depending on the type of order (monographic firm order vs. approval plan purchase vs. standing order/subscription).

What can be used for POL-invoice line matching in FOLIO?

• FOLIO POL number 
• Any vendor reference number (type does not matter)
• Upper/lowercase

Cannot be used:

• FOLIO PO number
• FOLIO POL with punctuation