ERM Sprint 78

ERM Sprint 78

Sprint Goal / Focus

  •  Bug fixes for Edelweiss

Sprint Schedule

  • Sprint: 78

  • Release: Edelweiss

  • Quarter: 2019 Q4

  • Start Monday 2 Dec, 2pm UK

  • Finish Friday 13 Dec, 12pm UK

 

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

Lead Roles:

  • Front End Code Review: 

  • Back End Code Review:  

  • QA: 

QA Environment: folio-testing

Navigation

  1. Sprint Goal / Focus

  2. Sprint Capacity

  3. Review sprint candidates 

  4. Agree technical approach / define key implementation tasks

  5. Finalise estimates / costings

  6. Confirm sprint scope

  7. Confirm first actions

 

 

Sprint Planning  

 - not in sprint

 or @ - in sprint 

 

Priorities for Edelweiss

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/UXPROD-1943

https://folio-org.atlassian.net/browse/ERM-621

@Aditya matukumalli

Missing functionality in https://folio-org.atlassian.net/browse/ERM-376.

Cannot use /export/ endpoint on its own, as current resources are missing. 

TODO:

  • confirm that license terms (esp controlling license) is presented

  • is the recent extension to the GSON template causing an issue or conflict?

  • Is something like the _SubscriptionAgreement.gson expand linked license section needed in the export (see conditions in lines 38 and 52)?

 

 https://folio-org.atlassian.net/browse/ERM-623

@Ethan Freestone

Blocking QA on export agreement, such as https://folio-org.atlassian.net/browse/ERM-418.

TODO:

  • Identify last known point it was working (EOD 21 Nov: snapshot)

  • Identify breaking changes to mod-agreements since then

  • Starting point may be around PR 210, 211 (relevant to the export), 212

Expecting that front-end is working as expected. 

 

https://folio-org.atlassian.net/browse/ERM-614

Relates to https://folio-org.atlassian.net/browse/ERM-561

Cursor tracks where in the harvest the process got to, so it can pick up from where it should be. 

  • What would the performance impact be on a production environment? Should be fixed as a moderate priority. 

  • Can this be done without executing an HQL query

TODO:

  • Set a from  offset (date/time) at the end of the harvest, to indicate where harvesting has reached

  • Set resumption point of cursor based on the from offset, when restarting

    • could last_check be used instead of cursor resumption? that could be problematic if the runsync erred. 

There's nested transaction mysteries.

@Ian Ibbotson (Use this one) to review code and comment on issue.

 

https://folio-org.atlassian.net/browse/ERM-558

@Claudia Malzer

TODO:

  • Add disabled attribute 

  • Fix console issue:

    • error on disabled resource filter

    • error thrown on first attempt

 

https://folio-org.atlassian.net/browse/ERM-567

@Peter Böhm

Comment left on Jira issue for @steve.osguthorpe

Additional

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions