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 Sub 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 Oct 20th 2021

Convener: Martina S.

Notetaker: Martina T.

Housekeeping

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

• Next ERM meeting:  Oct 27th

  • looking for volunteers to describe how Agreements vs. Agreement Lines are used to handle different use cases

  • looking for volunteers for a FOLIO Forum: in a panel presentation on how FOLIO libraries are managing ERM & acquisitions, specifically:

    • walking through the acquisition of a new e-resource start to finish (ordering, invoicing, activation, and agreement tracking)

    • walking through a renewal from an orders/invoices/agreement perspective

    • maintaining changes in title lists year over year

• 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

Agenda items:

1. Development progress -  ERM Sprint 125

2. Discuss ERM implementers topics:

   1. Internal KB: Enhance package metadata schema (line 44)

   2. Improvements to display of resources that are subscribed through an agreement (line 45)

   3. ERM comparisons: Make Comparison points hyperlinks (line 46)

   4. Agreements/agreement lines: Adjust placement of 'Add PO line' button on agreements edit screen (line 47)

   5. ERM comparisons: Freeze table heading (line 48)

   6. ERM comparisons: Sort by (line 49)

Minutes

• Development progress -  ERM Sprint 125

  • Sprint 125 finishes on Friday

  • Starting on work for Lotus

  • Kiwi Bugfest started this Monday – Agreements release with bug fixes - soon in bugfest environment

  • Testing is going well / halfway through the testing for ERM / Thanks to all testers

  • Other development: progress on testing structure, layout of screens, usability of widget configurations in Dashboard

  • Specific work looking at internal KB - Trying to improve logging process

• Discuss ERM implementers topics:

  • Internal KB: Enhance package metadata schema (line 44)

    • Felix: GOKb as KB is used and adding more and more packages to KB linking them as Agreement lines / Difficult to identify the package in the internal KB, because of the rudimentary metadata “name” and “provider” / Once the package name is harvested into FOLIO from GOKb is never changed. / We cannot see Identifiers or URLs back to the GOKb / Would like to see: Is it a current packages or was it deleted, is it retired, when was it last updated / Don’t need all of the 12 entries listed in the implementers topic page, but ID, status and alternative names are very important 

    • Owen: some will also be using the internal KB with GOKb or without GOKb and some will use eHoldings / what will be displayed in agreements / What are the useful fields to be displayed? Regardless of the source of the package 

    • Sara (chat): If info like that would be available to get from HLM via eHoldings, then to surface it would be wonderful too for me!!

    • eHoldings display: Provider + content type + package type

    • Felix: You have the option in eHoldings to view this information. For users of GOKb the information is not displayed in FOLIO at all – we don’t see it in the e-resources tab 

    • Owen: source agnostic solution would be great, we can only report on information we have

    • eHoldings: Provider + content type + package type

    • e-resources: provider + source + reference (kind of ID)

    • Felix (chat): https://gokb.org/gokb-ui/#/package/9355221

    • GOKb: name + status + content type (slightly different: Books, Journals, Data bases, Mix)

    • Does HLM has concept of status?  No it is deleted – all are active

    • HLM content type: E-Book, E-Journal, Print, Online Reference, Aggregated Full Text, Abstract and Index, Unknown  

    • HLM Type of the package: complete, variable

    • Sara: complete is indicator – package complete in itself, more likely to turn the package on as a complete package / Variable: all the titles, but more pick and choose

    • Sara (chat): For Package Type: I am seeing: Custom, Variable, Selectable, Complete, & 7 Conent Types

    • GOKb check-boxes: content is consistent – content may be split – content is fixed

    • Also Scope: back file,

    • Different KB with FOLIO? – are there different fields? Or views?

    • Kristin: SFX / have to think about the data model - is not the same / SFX “target” – I am not seeing things are not covered

    • Owen: Two aspects: What is available from KBs and what are the key things to be displayed?

    • Is there is something we haven’t yet considered?

    • Sara: ID for a HLM package as an alternative name, because it may be deleted

    • HLM: 3 part identifier: supplier-package-title

    • Owen: ID is stored but not displayed. Question about displaying and then searching. specific use case

    • Owen to come up with a proposal - a list for the display in FOLIO

    • Owen: taking the GOKb ones and not be to specific / What are the commons things? 

    • HLM, GOKb, 360, SFX / maybe coral?

    • Abby (chat) Database in 360 KB

    • Jack (chat): We never actually upgraded to the newer versions of CORAL which integrate with outside KBs

    • Bob (chat): TDNet? Anyone using that KB? We don’t just wondered

  • Agreements/agreement lines: Adjust placement of 'Add PO line' button on agreements edit screen (line 47)

    • Michigan State University: Linking multiple POLs to a single agreement line because agreement line represents a package and a POL for each book in the package

    • Molly: add more POLs – button to add POL – need to scroll down a long way – suggestion to add it to the top of the accordion

    • general navigation - referring to the topic last week - usability of screens 

    • Molly: dozens of POLs –agreements line to represent the eBook package and link to ACQ via the POL

    • Felix (chat): We're having a similar use case where we have one AGRLine for the Ebook Central purchases where we link all individual POLs to this one AGRLine.

    • Jack (chat): I assume we would do the same with the major eBook providers where we're doing one time purchases - I would select the individual titles in the knowledgebase but only attach the package and link the AGL to the POL

    • Maybe the scenario we are not dealing with well: multiple order lines for content in a single package within a single agreement

    • Worried about reporting and grouping costs

    • Felix: hoping match and merge via DOI and ISBN / They are linked via the POL 

    • Sara (chat) re: scrolling away: the accordion heading bar where the Add agreement line button is, but if I am scrolling through my AGLs in Browse/View and load and load and load ....

    • Gill and Owen will investigate about the add POL button

Chat

Von Sara Colglazier (MHC/5C) an alle:  02:15 PM
If info like that would be available to get from HLM via eHoldings, then to surface it would be wonderful too for me!!
Just saying: source agnostic solution would be great .... ;-)
Von Felix Hemme (ZBW) an alle:  02:22 PM
https://gokb.org/gokb-ui/#/package/9355221
Von Sara Colglazier (MHC/5C) an alle:  02:28 PM
For Package Type: I am seeing: Custom, Variable, Selectable, Complete, & 7 Conent Types
Von Owen Stephens an alle:  02:28 PM
Thanks Sara
Von Sara Colglazier (MHC/5C) an alle:  02:32 PM
SFX Target = Package HLM
Von Abby Wickes (she/her/hers) an alle:  02:32 PM
= Database in 360 KB
Von Sara Colglazier (MHC/5C) an alle:  02:33 PM
in HLM Packages have an ID too
I have even started recording them in my Agreements
Von Felix Hemme (ZBW) an alle:  02:34 PM
eHoldings package id: {   "data" : {     "id" : "7048",
Von Peter McCracken an alle:  02:35 PM
I’ve seen 3 digit IDs in HLM, not long ones like the FOLIO ID
Von Jack Mulvaney an alle:  02:42 PM
We never actually upgraded to the newer versions of CORAL which integrate with outside KBs
We waited for FOLIO :)
Von Bob Scheier (Holy Cross) an alle:  02:43 PM
TDNet? Anyone using that KB?
We don’t just wondered
Von Peter McCracken an alle:  02:43 PM
not for many many years
Von Jack Mulvaney an alle:  02:46 PM
This seems directly related to last weeks SIG
Von Felix Hemme (ZBW) an alle:  02:49 PM
We're having a similar use case where we have one AGRLine for the Ebook Central purchases where we like all individual POLs to this one AGRLine.
*link
Von Jack Mulvaney an alle:  02:50 PM
I assume we would do the same with the major eBook providers where we're doing one time purchases - I would select the individual titles in the knowledgebase but only attach the package and link the AGL to the POL
Von Sara Colglazier (MHC/5C) an alle:  02:54 PM
ebooks and coming streaming video
re: scrolling away: the accordion heading bar where the Add agreement line button is, but if I am scrolling through my AGLs in Browse/View and load and load and load ....

Attendees list