Skip to end of banner
Go to start of banner

2020-04-08 ERM Delivery Weekly Update

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

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

QA / UAT: NA

Code Review

In Progress 

  • ERM-547 - Getting issue details... STATUS
    • working on filter to work with package ingest
    • where packageStatus prevents add/update
    • OS to double-check whether retired packages are provided
  • ERM-793 - Getting issue details... STATUS  /  ERM-795 - Getting issue details... STATUS
  • ERM-777 - Getting issue details... STATUS  /  ERM-748 - Getting issue details... STATUS
  • ERM-805 - Getting issue details... STATUS
  • ERM-827 - Getting issue details... STATUS
    • agreements backend done
    • working on frontend 

Sprint Backlog

  • ERM-694 - Getting issue details... STATUS
  • ERM-800 - Getting issue details... STATUS
    • model developed and tested
    • needs adding to imports/exports
  • ERM-746 - Getting issue details... STATUS
  • ERM-788 - Getting issue details... STATUS
    • not started: 
  • ERM-794 - Getting issue details... STATUS  to follow ERM-795 
  • ERM-807 - Getting issue details... STATUS
  • ERM-779 - Getting issue details... STATUS
    • currently In Progress
    • nearly done - some line breaks and other qol matters to verify
  • ERM-828 - Getting issue details... STATUS
    • to take valid ui-agreements code into shared component for frontend
  • ERM-834 - Getting issue details... STATUS
    • intended behaviour to be verified
    • PCI collects PTI name first which would need to be traversed first
    • getName method is used rather than name properties
    • getter added for tags etc
    • need to devise solution to keep working when tags behaviour is refactored

Needs Elaboration

  • ERM-829 - Getting issue details... STATUS
    • reviewed with GBV and subgroup
    • working through user feedback to revisit options
  •  

10 mins

New Issues

Raised / brought into sprint: 

  • ERM-834 - Getting issue details... STATUS
    • higher priority than delete / duplicate
  • ERM-832 - Getting issue details... STATUS
  • ERM-831 - Getting issue details... STATUS

<15 minsAOB



  • No labels