/
2020-01-29 ERM Weekly Delivery Update

2020-01-29 ERM Weekly Delivery Update

Jan 29, 2020

Meeting Details

Date
 
Time

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

LocationVideo Call in FOLIO Slack: #erm-developers

Participants

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions


30 minsWIP Updates

QA / UAT: tets data now set up, so able to make good progress in testing

  • ERM-507 - Getting issue details... STATUS

  • ERM-571 - Getting issue details... STATUS
  • ERM-619 - Getting issue details... STATUS
  • ERM-647 - Getting issue details... STATUS

Code Review

  • ERM-434 - Getting issue details... STATUS  /  ERM-644 - Getting issue details... STATUS
  • ERM-671 - Getting issue details... STATUS  
    • final BigTest integration to complete 
    • currently going well
  • ERM-680 - Getting issue details... STATUS

In Progress 

  • ERM-633 - Getting issue details... STATUS  - de-scoped from active development
  • ERM-682 - Getting issue details... STATUS
  • ERM-683 - Getting issue details... STATUS  
    • Using license properties approach because of the vertex(?) constraints on mod-customfields library
    • Owen to follow up with Leipzig that ERM are doing the front end changes
  • UXPROD-2081 - Getting issue details... STATUS  - QA
  • ERM-569 - Getting issue details... STATUS

Sprint Backlog

  • ERM-655 - Getting issue details... STATUS  /  ERM-427 - Getting issue details... STATUS
  • ERM-685 - Getting issue details... STATUS
    • Mapping and UI to follow current QA
      • expect to be dropdown to define type of import and additional fields to capture new details
      • makes sense to have new route, as going to new endpoint. 
    • Clear to proceed with TSV controller

Needs Elaboration

  • ERM-668 - Getting issue details... STATUS  
    • active discussion between FE/BE/PO/UX
    • backend constrains ideal - but within requirement parameters
  •  

15 mins

New Issues

Raised / brought into sprint: 

Also:


<10 minsAOB

CHAL-208.  Entitlement endpoints are slow (~30s) in eHoldings, as single rows being added. Performance issues. This may be faced again by other EKB users (such as Cornell). 

  • Stripes-connect re-fetches on offset (but fixing this wouldn't fix the issue: may reduce the performance, but would involve significant work. 
  • ERM fetches per title. 

Some potential resolutions: 

  • ERM imports the data (commercially unlikely)
  • Attach order lines via eHoldings (rather than agreement resources): though can't do this if needing different order lines per resource.
  • Use a batch endpoint.