Versions Compared

Old Version 1

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


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

  • Jira Legacy
    serverSystem

Jira

  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-507

  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-571
  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-619
  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-647

Code Review

  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-434
     / 
    Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-644
  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-671
     
    • final BigTest integration to complete 
    • currently going well
  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-680

In Progress 

  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-633
     - de-
descoped
  • scoped from active development
  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-682
  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-683
     
    • 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
  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-2081
     - QA
  • Jira Legacy
    serverSystem JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-569

Sprint Backlog

  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-655
     / 
    Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-427
  • Jira Legacy
    serverSystem JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-685
    • 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

  • Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-668
     
    • 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.