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 Oct 4th 2023

Convener: Martina T.

Notetaker: Martina S.

Housekeeping

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

• Next ERM meeting:  Oct 18, 2023

• All questions and ERM implementers' topics can be posted on: ERM implementers.

• PC meeting Sep 14th

• PC meeting Sep 21st

• PC meeting Sep 28th

Agenda items

1. Development progress - ERM sprint 175

2. Discuss what other knowledge bases could or should be integrated with Agreements local knowledge base

   • previous discussion: WOLFcon Session "ERM-connecting KBs as metadata sources" recording and slides:

     1. Recording: https://prod-zoom-recordings-openlibraryfoundation-org.s3.amazonaws.com/b071fbe6-0543-44aa-9a96-13ec1ee175ef[…]ared_screen_with_speaker_view(CC).mp4
        Martina S. / GOKb -> 0:16:00
        Owen / Connecting metadata sources -> 1:09:53

     2. Slides can be downloaded from https://wolfcon2023.sched.com/event/1OleV/erm-connecting-kbs-as-metadata-sources

   • questions to look at in advance https://docs.google.com/document/d/1zC4YwX6IBLLq2wjlmLU47adZFg6TstsAYjQn-FEm-0I/edit?usp=sharing

Minutes

Development progress update

• moving to paginated search results in contrast to "load more" (brings us in line with common FOLIO UI)

  • for Agreements and AGLs in Poppy; Licenses will be done for Quesnelia

• work is in progress for options to filter gareements by document → is in code review

• in code review: new filter for looking for agreements with specific information missing

• changes to how data from GOKb is snchronized → not automatically switch, but there is the option to switch

  • will be tested on testsystems e.g. at VZG/GBV after release

  • changes will be applied to any data source, not only GOKb (ERM-3018 and UXPROD-3886)

  • both changes are switched off by default | can be activated via the code

  • external app will not be part of Poppy | is not tied to a release 

Discuss what other knowledge bases could or should be integrated with Agreements local knowledge base

• there are different ways to link resources with agreements

  • local KB imports

  • GOKb as external source

  • eHoldings | EBSCO KB

• e.g. Sara uses suppl. docs: an entry with a link to inventory

  • possibility: use suppl. documents to store title lists

  • Sara in chat: But then I cannot look them up by title in AGREEMENTS at least … a drawback

  • Scott in chat: That’s correct

• Bremen: use detached AGLs - linking to Inventory via POLs

• Inventory records can be linked via POLs to any AGL

• Sara: would be good to directly link to Inventory

  • package example: link one AGL to many Inventory records (use 0359 as a container code - as demoed in App Interaction: https://recordings.openlibraryfoundation.org/folio/app-interaction-group-mondays/2023-09-25T12:00/)

• are there resources people would like to see integrated with Agreements

  • SFX

    • we would need institutions willing to help (customers | Jessica would be willing to help)

  • Kanopy

    • we would need institutions willing to help (customers | Jessica would be willing to help)

  • LibGuides A-Z list

  • LibAnswers

  • OCLC WMS

• using different options to linking resources is possible: configuration in Agreements settings

  • Robert Heaton in chat: Having a local KB alongside HLM would expose the local-kb settings in agreements, in some cases where they wouldn’t apply or might interfere with the connection to eHoldings.

• Peter: KBART automation in addition to existing KBs such as HLM would be good | good metadata is needed

• Robert in chat: Yes, I agree that KBART Automation would work with the knowledgebase directly rather than FOLIO

  • Owen thinks it could work directly

• Jessica in chat: For institutions that don't have a KB integrated with FOLIO though, KBART automation would be helpful. We go title-by-title with Elsevier and it's a lot of manual work to add all those agreement lines.

  • Robert answers in chat: If the content provider is able to provide the automation files, at least in theory they could send them to the library instead of the KB supplier. But the automation part would benefit from something like FOLIO’s APIs re: a place for the data to go.

We will come back to this discussion in a future meeting.

Chat

14:02:07 From Martina Tumulla To Everyone:
    Today's Agenda: https://folio-org.atlassian.net/wiki/display/ERMSIG//2023-10-04+-+ERM+meeting
14:30:23 From scolglaz To Everyone:
    Or I was also using Supp Doc
14:36:01 From scolglaz To Everyone:
    But then I cannot look them up by title in AGREEMENTS at least … a drawback
14:37:10 From Scott Perry To Everyone:
    That’s correct
14:38:34 From scolglaz To Everyone:
    I would love if I could add a link in the AGL
14:40:22 From Catherine Tuohy To Everyone:
    So sorry I have to leave early, thanks Owen and all, will review notes.
14:41:36 From Owen Stephens To Everyone:
    Replying to "So sorry I have to l..."
    
    Thanks Catherine
14:41:51 From Felix Hemme To Everyone:
    Search performance has improved since we were upgraded to Orchid, so that is something at least :-)
14:43:12 From Martina Schildt | VZG To Everyone:
    Recording of last container discussion in App Interaction: https://recordings.openlibraryfoundation.org/folio/app-interaction-group-mondays/2023-09-25T12:00/
14:43:32 From Robert Heaton To Everyone:
    Reacted to "Recording of last co..." with 👏
14:45:19 From Robert Heaton To Everyone:
    I am on the KBART standing committee and am happy to bring any questions or suggestions back.
14:47:36 From Jessica (she/her/hers) To Everyone:
    I'd be happy to help!
14:50:29 From scolglaz To Everyone:
    Raising my hand
14:51:00 From Jessica (she/her/hers) To Everyone:
    Interesting - raised hand is missing from my Zoom controls too!
14:51:22 From Jessica (she/her/hers) To Everyone:
    Nm - they pulled it out. It's now next to the reactions
14:51:29 From Felix Hemme To Everyone:
    Reacted to "Nm - they pulled it ..." with 👍
14:53:50 From Robert Heaton To Everyone:
    Having a local KB alongside HLM would expose the local-kb settings in agreements, in some cases where they wouldn’t apply or might interfere with the connection to eHoldings.
14:55:31 From scolglaz To Everyone:
    Thanks, Jessica: I found it now! Thank you!
14:55:42 From Jessica (she/her/hers) To Everyone:
    Reacted to "Thanks, Jessica: I f..." with 👍
14:57:44 From Robert Heaton To Everyone:
    Yes, I agree that KBART Automation would work with the knowledgebase directly rather than FOLIO.
14:58:00 From Felix Hemme To Everyone:
    Replying to "Yes, I agree that KB..."
    
    Thanks Robert for confirming
14:58:40 From Robert Heaton To Everyone:
    Reacted to "Thanks Robert for co..." with 👍
14:58:51 From Jessica (she/her/hers) To Everyone:
    For institutions that don't have a KB integrated with FOLIO though, KBART automation would be helpful. We go title-by-title with Elsevier and it's a lot of manual work to add all those agreement lines.

Attendees list