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 May 4th 2022

Convener: Martina S.

Notetaker: Martina T.

Housekeeping

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

• Next ERM meeting:  May 18, 2022 

• 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 April 7th

• PC minutes April 28th

• Question: Do you need more field based permissions in ERM? Which fields would be needed?

• Question: What ERM sessions would the ERM SIG like to plan for Wolfcon (Aug 31st - Sep 2nd, Hamburg) - https://openlibraryfoundation.org/about/wolfcon/upcoming/

  • please let us know via Slack

  • One submitted session: "Leveraging FOLIO ERM with GOKb data" (Community sharing meeting) 

  • who will be attending? - if you already know, please indicate in attendees list below

Agenda items

1. Development progress -  ERM Sprint 138 / 139

2. Update on latest ERM development

Minutes

• Field based permissions in ERM

  • Topic raised in App Interaction

  • Owen: Users has view and edit permissions in Agreements, but the user should not edit/update one specific field - so they can edit the agreement, but not field "A" - requirement for more granular permissions?

  • Martina S.: example Organizations app – credentials for interface 

  • Owen (chat): Either in agreements or licenses

  • Please let Martina, Martina and Owen know or post it in the ERM team Slack channel

  • Emma (chat): For field based permissions, we (at Cornell) had been thinking it would be nice if our selectors could edit "renewal priority" in Agreements, but nothing else, since they are the ones who decide whether they want to renew an item, but otherwise we don't want them messing around in our agreements :)

  • Owen: good example and interesting one, one way could be to offer a kind of action to change the renewal priority and not have the edit screen with only one field to change  

  • Emma: even better with this action and if they do not have to open the edit screen

• Development progress

  • ERM-2045 Extend Package data model to store additional information

    • continue to work on extending the metadata we record for packages in Agreement local KB

    • adding fields to model and next we will start to populate those fields – aim is for Morning Glory

  • ERM-1986 Move identifiers between title instances

    • Support moving identifiers between title instances - using the local Kb – incorrect Identifier assigned to a title, there is not a real way to fixing this right now

  • Another hotfix for Kiwi and for Lotus

    • Bug in dashboard regarding the links from dashboard into other app

    • Kristin (chat): What does the Kiwi hotfix cover?

      • searching for “Kiwi (R3 2021) Hot Fix #3” in Jira

• Update on latest ERM development

  • in Settings: Supplementary properties in Agreements and Terms in Licenses

    • Is going to QA now – ready for the next release morning glory 

    • Better interface for interacting with the terms and supplementary properties e.g. searching

    • Option to make terms/supplementary properties deprecated à e.g. used to record it, but not any longer

    • Deprecated Terms/Supplementary properties will not show up when you are trying to add new terms to License or supplementary properties to Agreements

    • It cannot be primary term and deprecated at the same time – “A term cannot be both primary and deprecated”

    • If you set a term to deprecated – the term is still displayed in Licenses, but it is marked with DEPRECATED

    • You cannot add it to any licenses, since it is not in the pick list any longer

    • Julie (chat): Excited to see the term deprecation feature!

  • Licenses terms and supplementary properties: Creating a new term – new type “Date” 

    • When filtering by terms choosing a date based one – date based comparators can be chosen

  • Looking at the multiple value issue

    •  e.g. if you would like to record more than one authentication method - no way of having single term where you can chose both IP and SAML

    • You cannot select two options on a list

    • Questions and presenting some options in a future meeting

Chat

Von Owen Stephens an alle 02:05 PM
Either in agreements or licenses
Von Emma Raub an alle 02:10 PM
For field based permissions, we (at Cornell) had been thinking it would be nice if our selectors could edit "renewal priority" in Agreements, but nothing else, since they are the ones who decide whether they want to renew an item, but otherwise we don't want them messing around in our agreements :)
Von Martina Schildt | VZG an alle 02:10 PM
Thanks Emma, is noted :)
Von Jessica Harris (she/her) an alle 02:11 PM
@Emma, I like that idea!
Von Kristin Martin an alle 02:11 PM
What does the Kiwi hotfix cover?
Von Julie Brannon (she/her) an alle 02:18 PM
Excited to see the term deprecation feature!

Attendees list