Zoom link: https://folio-org.atlassian.net/wiki/spaces/ERMSIG/pages/47776470/eHoldings+subgroup#Zoom
\uD83D\uDDD3 Date
05 Jun
\uD83D\uDC65 Participants
Zorian Sasyk Owen Stephens Clara Marino Becca Banach Elizabeth Richens Please add yourself if you attended!
\uD83E\uDD45 Agenda
Housekeeping
Updates on previous topics
: UIEH-1419 complete and on track for Ransoms!
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIEH-1419
Implementers topic #2 - #7 - Searching in eHoldings: issues and possible improvements?
Misc (if time)
Actions
\uD83D\uDDE3 Discussion topics
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:
| ||||||||
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 #1: Proxied URL display in eHoldings title records | Zorian | Zorian demoed to group Proxied URL display in eHoldings title-level records using Snapshot. At this time, Proxied URLs will only be displayed at the title level; package-level display will need to be a different User Story. A seperature User Story is being worked on for adding the Proxied URL to the eHoldings package-title export report. | ||||||
40 mins | Agenda #2: eHoldings search issues (Clara Marino) | Zorian | Clara discussed and demonstrated issues with eHoldings search: -stemming is occuring inconsistently across searches (ex. mobilization returns titles with mobilizing, mobile, etc, while quantification returns quantification) -uncertain how asterisk functions as wildcard Group discussed need for search documentation for eHoldings, as well as fix for stemming issue Question: should eHoldings search follow how FOLIO inventory and users search works, or follow how the ERM apps search works? ERM apps do NOT use elastic/opensearch at this time, but there are long terms plans to switch
| ||||||||
20 mins | Agenda #3 | Zorian | Did not discuss, meeting ended early |
Notes:
Action items:
Zorian will
...
Zorian will pass long feedback for agenda item #3 to Khalilah Gambrell /dev team
...
followup regarding search issues discussed in meeting; if necessary, make bug case for eHoldings search stemming.
Followup on wiki documentation for eHoldings search: eHoldings title search is based on Advanced search of HoldingsIQ API, documentation here: https://developer.ebsco.com/knowledge-services/docs/holdingsiq-using-search-types