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 Feb 7th 2024

Convener: Martina S.

Notetaker: Martina T.

Housekeeping

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

• Next ERM meeting:  Feb 21, 2024

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

• PC meetings

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

  • 2024-02-1 Product Council Agenda and Meeting Notes

Agenda items

1. Update on ERM SIG meeting frequency

   1. Change ERM SIG meeting frequency to every 4 weeks

   2. New working group on internal KB topics will meet every 4 weeks

2. Development progress - ERM sprint 184 (link follows)

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

Minutes

• Update on ERM SIG meeting frequency

  • Change ERM SIG meeting frequency to every 4 weeks

  • New working group on internal KB topics will meet every 4 weeks

  • More topics for internal KB e.g. synching mechanism and logging of results of synching mechanism

  • Start in March / calendar invite will follow and information sharing via Slack and on Wiki page

  • Khalilah as PO for eHoldings is informed

  • Sara: similar working group for eHoldings? 

    • No plans, yet but ERM conveners will ask Khalilah and Zorian

  • Sara: How will the results from the subgroup shared with the bigger ERM group?

    • Owen: Anything that might come up and has impact in general ERM will be brought back to the bigger group

  • Martina S.: We will make sure that meetings not collide, so everyone can attend who would like to. Everyone is welcome to attend all meetings.

  • Sara: hope to have mixture of different sources

    • Owen: you can use both, but there is then a mixture of methods, which is not ideal / Aim to decrease the difference between those methods

• Development progress - ERM sprint 184 (link follows)

  • Several tickets in QA
    
    

  • Bug reported: with upgrade to poppy previously set up dashboards no longer displaying, no data is missing or deleted – fix for next poppy service batch

  • External data source display is now displayed in the 4th column in Settings local KB admin to be consistent and easier to navigate

  • Implemented the column selection on the Agreement line accordion in the Agreement view

  • Decide to select field display – valid for a browser session – same design like the POL display in PO in Orders and others

  • Felix (chat): What happens when you uncheck all columns? Other apps have a default column that can't be deselected, in this case this could be "Name"

  • Owen: deselect all – one column cannot be deselected to be a default

  • Felix: name/description or reference should be default

  • Sara: it is a hyperlink to eHoldings you cannot enter your AGL – we need two defaults

  • Owen: old mechanism = click somewhere in the line will open the Agreement line + click on the hyperlink open up the resource / new mechanism = not having the full line click und can have multiple hyperlink e.g. additional AGL number / Pros and cons about both mechanisms

  • Sara: mentioning a number in front of the table – is this possible? Would be helpful - much easier to talk to someone or for remembering

  • Owen: something similar for the serial management – pattern ID is display (number generator) / Each time to add a publication pattern a number from the number generator is allocated – always unique 

  • Sara (chat): No recalculation when one gets deleted

  • Owen: Maybe like the POL – no recalculation

  • To-Do: new implementers' topic for discussion around AGL numbers

  • Felix (chat): We have buttons in MCL's in the Harvester admin app. (Screenshot)

    Open

    

  • Owen: buttons not part of the current UX, but will check

  • Sara (chat): Just an idea: seeing how you had that 4th pane in Settings, could there be something like that with ERM?

  • Martina S.: Audit log in the 4th pane?

  • Owen: not quite the same, we are using the 4th pane for e.g. tags and have ideas about it

  • To-Do: new implementers’ topic around the use of the 4th pane and invite Gill for our discussion

• Avoiding multiple users editing a record at the same time

  • Optimistic locking – mechanism two people trying to update the same record / starting editing simultaneously  – one saves it and to stop the second save overwriting the first one

  • In Inventory Message: “saving instance failed” “cause it has been changed (optimistic locking)”

  • new version number is saved for records

  • Sara: it is different in MARC source record – Edit MARC bibliographic record (quick marc)

  • Message: “This record cannot be saved because it is not the most recent version. View latest version”

  • Sara: Hyperlink view latest version – open in a new pane and retain the not saved changes – two screens possible and coping the not saved changes in the latest version manually

  • Felix (chat): Could it be smarter than what Inventory has implemented? Like compare on a field-by-field basis. So user A+B have the same record in edit view, user A changes field 1, user B changes field 2 and saves first. Why should user A not be able to save the record in this case If the mechanism could check and compare on field basis, it would detect when multiple users try to change the same field. But I don't know if this is technically possible with Folio.

  • Owen: in most applications – when you save the record it always saves the entire record not the updates / different framework is used in ERM, but allows to save partial records - possibility only saving the changes, but in practice it would be tricky to implement, but discussion with the developers

  • Questions: What would be the priority? – Licenses or Agreements or Agreement Lines

  • → Agreements

Chat

scolglaz  an  Alle 14:11
Yes, please incl. Zorian.
Martina Schildt | VZG 14:11
we'll do - thank you
scolglaz 14:12
But it could be an off week from the two.
Martina Schildt | VZG 14:12
we will make sure that the meetings do not collide
scolglaz 14:17
At 8 am I come in early for this meeting in any case. ;-)
FOLIO bee visiting all the flowers! Cross pollination. ;-)
Felix Hemme 14:28
What happens when you uncheck all columns? Other apps have a default column that can't be deselected, in this case this could be "Name"
scolglaz 14:28
Just an idea: seeing how you had that 4th pane in Settings, could there be something like that with ERM?
In think in Bulk Edit there is a default one
Felix Hemme 14:34
Or a button "Show agreement line"?
Felix Hemme 14:36
We have buttons in MCL's in the Havester admin app.
scolglaz 14:39
No recalculation when one gets deleted
Felix Hemme 14:54
Could it be smarter than what Inventory has implemented? Like compare on a field-by-field basis. So user A+B have the same record in edit view, user A changes field 1, user B changes field 2 and saves first. Why should user A not be able to save the record in this case
If the mechanism could check and compare on field basis, it would detect when multiple users try to change the same field. But I don't know if this is technically possible with Folio.
Jessica Harris 15:00
Agreements
Clara Marino 15:00
Agreed

Attendees list