2024-06-5 Agenda and Meeting notes

Owned by Zorian Sasyk
Last updated: Jun 07, 2024
2 min read

Zoom link: eHoldings subgroup | Zoom

 Date

Jun 5, 2024

 Participants

  • @Zorian Sasyk @Owen Stephens @Liisa Mobley @Phil Adams @Sara Colglazier @Clara Marino @Martina Karlsson @Elizabeth Richens

 Agenda

  1. Housekeeping

    1. Updates on previous topics

      1. UIEH-1424: Add hover text to clarify add versus create options for Agreements tab in eHoldings package record viewClosed

  2. Implementers topic #5 - UIEH-1419: eHoldings package-title (resource) view: display Proxied URLClosed

  3. Implementers topic #2 - UIEH-1388: Incorporating cost or price information from FOLIO acquisitions records (Orders and/or Invoices)Draft

  4. Actions

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

10 mins

Agenda #!

Zorian

Provide update on work being done for Ransoms on UIEH-1424

30 mins

Agenda #2

Zorian

Introduced scope of UIEH-1419, adding proxy URL link to eHoldings package or title record display

Discussed pros/cons of two options presented

Settled on Option B (in Resource settings section) with following additions:

  • add copy clipboard icon

  • add open in new tab icon

  • Determine what happens/appears if URL has no proxy (OA/free materials, et)?

20 mins

Agenda #3

Zorian

Introduced UIEH-1388, incorporating FOLIO Acquisitions cost information in eHoldings Usage CPU calculation

Discussed where the best source of this cost info would be in FOLIO; settled on invoice line

Other considerations:

  • how to deal with multiple invoice lines for one usage period (ex. revisions to invoice, monthly or quartely invoicing etc). Add mechanism to sum all invoice lines per usage period?

  • How to tie invoice line fiscal/annual year to usage periods presented in eHoldings Usage.

    • Members of group generally do NOT try to tie usage periods to fiscal years in their current CPU calculations; rather they settle on standardized year periods that are used across all e-resoruces regardless of each resources actual renewal cycle

    • Possible method could involve using invoice lines subscription start/end dates fields for calculating which usage year the cost info applies to

    • Another method could utilize the linking POL’s fund fiscal year

Notes:

Action items:

  1. Zorian will pass along feedback for agenda item #2 to @Khalilah Gambrell /dev team

  2. Zorian will pass long feedback for agenda item #3 to @Khalilah Gambrell /dev team

  3. Zorian and @Owen Stephens will follow up with eUsage app folks to determine how they handled CPU/cost matching