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 Jan 24th 2024

Convener: Martina T.

Notetaker: Martina S.

Housekeeping

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

• Next ERM meeting:  Feb 7, 2024

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

• PC and Tri-council meetings

  • 2023-12-14 Product Council Agenda and Meeting Notes

  • 2024-01-11 Product Council Meeting Agenda and Notes

  • 2024-01-18 Tri-Council Meeting

Agenda items

1. Development progress - ERM sprint 183

2. Implementers' topic: When duplicating an agreement/ or a license: additional fields should be duplicated

   1. ERM implementers #3

3. Avoiding multiple users editing a record at the same time

Minutes

Development progress

• Licenses settings: new license term pick list setup > pick lists and their values can be managed in one screen

  • Felix in chat: Nice improvement, especially for libraries starting with ERM and the task to set everything up.

• organisation status has been added to organisation display in agreements and licenses

• Dashboard > Widgets > content type is added as a filter to agreements widgets

  • Felix in chat: Will the filter become a select instead of a free text field eventually?

  • Owen: would be ideal to have it as a pick list, but rhe filter depends on a configurable list > there it is not possible

  • Felix: I understand. That is why agreement status can be a select, because the pick list values are static.

• for Quesnalia the team is aiming to update to Grails 6 as a framework - that is a major piece of work

• working on a new process on getting data into FOLIO's internal KB 

Implementers' topic: When duplicating an agreement/ or a license: additional fields should be duplicated - ERM implementers #3

• agreements can be duplicated in view mode

• there is a modal that opens after hitting "duplicate" with checkboxes to select which information should be duplicated

• as sson as the selected list is saved the record is duplicated

• further fields for duplication are requested:

  • reason for closure

  • alternative names

  • agreement period end date

  • related agreements > should be its own checkbox

  • tags

  • change rule for start date to: the new duplicated agreement should have the day of the original agreement set automatically (instead of the current date) > requested by Felix

    • Sara in chat: If I am duplicating and check off date, then I want that date (the current day). 

  • all data should be duplicated, otherwise users can forget that they need to add it to the new record

•  

  • Owen to come up with a proposal for new duplicating agreements behaviour  Feb 21, 2024 

    • create a Jira ticket 

    • include different options how start dates should behave

    • break down list of checkboxes etc

    • come back to ERM SIG in one month time

  •  this would be short term development

  • there could be more targeted options > we should brainstorm on what is needed in a future ERM SIG meeting - long term development

• Sara in chat: In the modal that you just showed, I noted AGL … will those still be duplicatable, with the new structure? Because it is often to remove than to add. … And if you wanted to break an AG apart into many, from when you were trying first off to have everything combined onto one.

Avoiding multiple users editing a record at the same time

• ERM apps plamn to align with current FOLIO behaviour

• one user opens a record and makes edits

• another user opens the same record and saves edits before the other user user has saved their changes

• new: optimistic locking comes into play: person who saves first takes priority

• needs implementing for each record (one by one)

• Felix in chat: There has been a question from Zorian on Oct 25th, 2023 about multiple users simultaneously trying to edit the same record: https://folio-project.slack.com/archives/C9ER2HCRY/p1698269299867129

• Sara in chat: That is how it works in Inventory in quickMarc for example … getting the block but also the option to open the record again separate and the blocked record remains to be able to copy from

• will come back to this topic in a future meeting

Chat

Attendees list