2020-06-03 ERM Weekly Delivery Update

Meeting Details

Date
 
Time

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

LocationVideo Call in FOLIO Slack: #erm-developers

Goals

Apologies

Discussion items

Previously: 2020-05-27 ERM Weekly Delivery Update

Time

Item

Notes

Action Items

<5 minsIntroductions


30 minsWIP Updates

Code Review: 

  • ERM-681 - Getting issue details... STATUS
  • ERM-919 - Getting issue details... STATUS  /  ERM-920 - Getting issue details... STATUS
    • needs the backend to be merged
  • ERM-933 - Getting issue details... STATUS
    • PCI doesn't have a Note field (unlike AL edit (934))
    • should it go with dates? YES
    • goal is to move to 4-column

In Progress 

  • ERM-924 - Getting issue details... STATUS
  • ERM-934 - Getting issue details... STATUS
  • ERM-775 - Getting issue details... STATUS  /  ERM-774 - Getting issue details... STATUS ERM-776 - Getting issue details... STATUS  
    • 774 ready for review
    • but depends on what to do with identifiers (776) 
    • better perhaps to use siblingTitles
    • impact on KBART to group siblings, rather than trying to group by identifier in frontend
    • options are to: 
      • remove and replace siblingIdentifiers with siblingTitles
      • add siblingTitles and leave siblingIdentifiers also
    • decision: remove and replace
    • Steve to refactor backend to return siblingTitles for 776+774; and 775 to be reworked
  • ERM-510 - Getting issue details... STATUS
    • Steve to find example from Grails docs
    • can have multiple p-value pairs for MDC
    • extend domain class for events as type of map
    • will store text from map (not JSON) and should be saved and retrieved for output without additional effort

Sprint Backlog

  • ERM-843 - Getting issue details... STATUS  /  ERM-850 - Getting issue details... STATUS
    • returned from testing
    • transactional overlap issues
    • Owen to find some new test data
  • ERM-925 - Getting issue details... STATUS
    • not started yet
    • awaiting examples
  • ERM-930 - Getting issue details... STATUS  /  ERM-929 - Getting issue details... STATUS  /  ERM-931 - Getting issue details... STATUS
  • ERM-888 - Getting issue details... STATUS
  • ERM-935 - Getting issue details... STATUS
    • may be fixed as part of Tags branch
    • Move staright to QA for Owen to verify

Needs Elaboration

  • NA

QA / UAT: 

  • ERM-910 - Getting issue details... STATUS  - passed QA
  • ERM-921 - Getting issue details... STATUS
  • ERM-922 - Getting issue details... STATUS
  •  

10 mins

New Issues

Raised / to bring into sprint: 

  • ERM-921 - Getting issue details... STATUS
  • ERM-922 - Getting issue details... STATUS
  • ERM-935 - Getting issue details... STATUS
  • ERM-923 - Getting issue details... STATUS

Raised

  • ERM-928 - Getting issue details... STATUS
    • hard to recreate: resizing the SaS results pane and then browser window
    • can be replicated on snapshot
    • issue relates to pane set not reflowing everything or not calling saved user-preferred pane width
  • ERM-936 - Getting issue details... STATUS

<15 minsAOB

?