/
2021-05-19 ERM Weekly Delivery Update

2021-05-19 ERM Weekly Delivery Update

May 19, 2021

Meeting Details

Date

May 19, 2021    

Time

9:15am ET, 2:15pm UK, 3:15pm Germany

Location

Video Call in

Previously

2021-05-12 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Gill Osguthorpe

  • @Ethan Freestone

  • @Peter Böhm

  • @Aditya matukumalli

  • @Monireh Rasouli

  • @Owen Stephens

  • @Claudia Malzer

Apologies

Discussion items

Time

Item

Notes

Action Items

Time

Item

Notes

Action Items

<5 mins

Introductions

 

 

Previous Actions

NA

 

 

WIP Update 

Release Candidates

Code Review: 

  • https://folio-org.atlassian.net/browse/ERM-1617

    • requested changes have been made

    • should also add isEmpty and isNotempty

    • returned to In Progress to make change

    • to dev test:

      • functionally the same as isNull

      • not available in definition to test yet, which will be dealt with in  

QA / UAT 

  • NA

For Release

  • NA

Items at Risk / Spillover

In Progress

  • https://folio-org.atlassian.net/browse/ERM-1540

    • first version of mod-agreements changes made

      • available to review

      • not ready for merging as validation not tested until frontend is

    • frontend is more problematic; not sure where to start

      • not clear about what should and shouldn't be validated

      • is additional component needed to add different roles?

    • Transferring issue to Adi to pick up the frontend

      • Will need to set up local vagrant, bumping up cores and RAM

    • Owen to share validation scripts 

    • Claudia to post new shape for Adi

  • https://folio-org.atlassian.net/browse/ERM-1643

    • mod-agreements and mod-licenses can now use the same interface

    • mod-service-interactions no longer stores widget definitions, but will poll implementing modules that manage definition versions

      • some alight shape changes

      • existing domain classes will remain for external access / compatibility

    • non-app based definitions (such as RSS)

      • can use the same interface

      • can be handled directly by mod-service-interaction

    • some local grails access issues causing problems

    • main concern will be handling of typedowns within MSI ... a soon problem

    • terms display is tricky

      • would need some kind of wildcard in the definition (for an unknown property)

      • though is a lower priority

      • one use case requires search by term

  • https://folio-org.atlassian.net/browse/ERM-1632

    • pushing to branch for further

Sprint Backlog

Needs Elaboration

Bugfix Cycle

  • NA

Accepted

Closed

 

<10 mins

AOB

New Issues

Added to sprint

Not added to sprint

  • NA