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 Dec 15th 2021

Convener: Martina T.

Notetaker: Martina S.

Housekeeping

• All: Please edit the attendees list below and indicate when you are there!
• Next ERM meeting:  Jan 12
  
• 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
• PC minutes Dec 2nd
• PC minutes Dec 9th
• The FOLIO Documentation Working Group is seeking a volunteer to write documentation for the Local KB Admin app and the ERM Comparisons app

Agenda items:

1. Development progress -  ERM Sprint 129
2. Copying agreement line information
   1. Homework to complete before meeting: Please read and and the questions in this document (https://docs.google.com/document/d/1HnB3OuPCkfMZuwRTDhGd4l5OgVSyWPWbjg5hVYv5alo/edit?usp=sharing)

Minutes

Development progress

• for libraries using the Local KB Admin and external source: harvest process can get stuck in a suspended state - trying to track the reasons down
• currently implementing options to reset
• work on where documents are stored that are added to agreements and licenses
• in cases where libraries are running multi tenants in a single installation → documents are not uploaded to a tenant specific area in database → S3 is the option for cloudbased storage that the ERM team is looking at
• Benjamin in chat: @Owen: Do you know where the other apps (e.g. invoices) are storing file uploads?
  
  • in some apps files are stored on S3 or a compatible service
  • there is no established rule for a most appropriate solution
• security issues with log4j → focus has been put on fixing related issues
• improved sorting of agreement lines → they are now sorted in a consistent manner; they are sorted by FOLIO ID
• reaction by Sara in chat: YEAH!!!!
• counts for individual resources as well as packages; displaying the "selected / available" (e.g. 0/1)
• non-attached lines (empty lines) show a dash; the non-attached sort first; resources from the same package will sort together

Copying agreement line information

• resource is being linked into an Agreement line
• for some reason the resource is removed from e.g. the eholdings KB; a new one is added in
• Agreement line now points at nothing; the information on the agreement line is relevant for the new resource; but the Agreement Line cannot just be updated to point at the new resource → restriction is deliberate due to data integrity reasons
• related: sync from external systems into FOLIO ERM like for LAS:eR
• now we are looking for a compromise
• the proposed approach is to have a copy mechanism
• scenarios where copying agreement lines would be useful
  • Jack (UMass) in the homework document: Sometimes the EBSCO KB breaks content into chunks sort of arbitrarily (ScienceDirect eBooks versus eJournals) and our notes/PO/etc. are just for “ScienceDirect” so I will assign the notes helper app note to both AGLs since it isn’t specific just to the eJournals. With 1 note its easy to use the notes helper app functionality but with more than 1 and a POL it might be nice to duplicate all at once and apply to the 2nd AGL. It wouldn’t really be the actual AGL that I want to copy though.
  • recorded information would be specific to Science direct and the platform, not the actual resources (books or journals)
  • this is relevant especially for a set of information; rather than just one note
• does the "replace resource" example cover all use cases or are there other?
• the former resource is no longer needed in this scenario 
  • it covers all; 
• Sara: eholdings can unlink from an agreement line; it does not work the other way round → that is not ideal
• Owen: Agreements has no way to preserve the information; we cannot change the behaviour
• Sara would prefer "copy and close" and delete the former resource in a separate step - if necessary
• Owen: "copy and delete" would be closer to replace a resource than "copy and close"
• the other scenario that has been proposed is "copy and close" → preferred by Owen
• Bob in chat: Thats more like we do with serials title changes I think; they use a "continued by" note
• Jack in chat: Can I delete an AGL if it is linked to a POL/has notes helper app notes?
  
  • Owen: yes, that is possible; there are currently no restrictions
• Kristin: there may be use cases for both approaches
• Owen: the deletion of agreement lines is allowed; so offering "copy and delete" is consistent with that
• Sara: there are use cases where I want to copy without deleting
• the copying of data between 2 existing agreement lines is also taken into consideration
• do we need to record relationships between agreement lines
  • yes, e.g. for "continues / is continued by"
• eholdings relations need review
• Jack in chat: That would also be helpful when the EBSCO APIs go down which is happening more frequently lately
  

Chat

14:08:43 Von  Benjamin Ahlborn  an  Alle:
    @Owen: Do you know where the other apps (e.g. invoices) are storing file uploads?
14:13:17 Von  Sara Colglazier (MHC/5C)  an  Alle:
    YEAH!!!!
14:50:58 Von  Bob Scheier (Holy Cross)  an  Alle:
    Thats more like we do with serials title changes I think
14:51:03 Von  Jack Mulvaney  an  Alle:
    Can I delete an AGL if it is linked to a POL/has notes helper app notes?
15:01:41 Von  Jack Mulvaney  an  Alle:
    That would also be helpful when the EBSCO APIs go down which is happening more frequently lately
15:02:20 Von  Bob Scheier (Holy Cross)  an  Alle:
    Happy Holidays to you all!
15:02:38 Von  Owen Stephens  an  Alle:
    Thanks Martina and Martina 🙂
15:02:42 Von  Owen Stephens  an  Alle:
    See you next year

Attendees list