Versions Compared

Old Version 2

changes.mady.by.user Jag Goraya

Saved on

compared with

New Version Current

changes.mady.by.user Jag Goraya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Meeting Details

Date 
Time

09:30am ET, 2:30pm UK, 3:30pm Germany

LocationVideo Call in FOLIO Slack: #erm-developers

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions


30 minsWIP Updates

Code Review: 

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1012
    • Ethan can take a look
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1050
    • needs checking similar to licenses
    • changes applied to datepickers outside of card components sent back to In Progress

In Progress 

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1000
    • mostly working on datepicker fixes and code review, so not far progressed apart from requirements clarifications
    • should be "Suppress from discovery" rather than "Suppress from delivery"
    • Relates to ERM-1004
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1004
    • Relates to ERM-1000
    • fiddly migrating agreements settings page from redux to finalform, and modconfig
    • more complex than importing fields because of save handling
    • decided not to add in a fieldarray
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1032
     / 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1049
     
    • Code refactored to improve performance
    • Load more added, Load All not to be added
      • ERM-1049 closed
      • Parent ERM-1032 ready for release 
    • Investigation tasks to be separated out

Sprint Backlog

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1010
    • making progress on first subtask 
    • looks straightforward 
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1002
    • to be handled as part of ERM-1000
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-904
     = pending return of Steve O
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1053
    • not sure how to reject a single entry in a JSON file 
    • (if that is even the ask)
    • ingest process should split it out and reject the individual line
    • should it be handled in KBART import process or Gokb adaptor?
    • re-assigning to Owen for clarification ... JSON doesn't reject, KBART does. What should happen?

Needs Elaboration

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-999

QA / UAT: 

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-943
     / 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-986
    • If TrustedSource is off, no fields should be updated
    • If TrustedSource is on, simple fields are handed but identifiers are updated through JSON patching
    • refData rather than string, but should be based on enrichment routine 
    • returned to sprint backlog
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1006
    • assigned to Gill for QA
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-994
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1052
     / 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1051
    • PR still pending merge from John Coburn for functionality to work, but the component should now be visible completely
    • JC working on validation which is not firing correctly. 
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1054
  •   

10 mins

New Issues

Raised / to bring into sprint: NA

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1041
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1042
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1054
    • moved to QA
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1053
     = returned to Owen for clarification

Raised: 

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1056
    • potential translation issue - code changes necessary
    • pending snapshot / testing rebuild
    • bumped back to QA 
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1055
    • assigned to Steve for post=JDK11
    • could block release of comparison functionality

<15 minsAOB