/
ERM Sprint 83

ERM Sprint 83

Feb 10, 2020

Sprint Goal / Focus

  •  

Sprint Schedule

  • Sprint: 83
  • Release: 
  • Quarter: 2020 Q1
  • Start Monday 10 Feb, 2pm UK
  • Finish Friday 21 Feb, 12pm UK


Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

Lead Roles:

  • Front End Code Review: 
  • Back End Code Review:  
  • QA: 

QA Environment: folio-testing

Navigation

 Sprint Planning Agenda
  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  

(error) - not in sprint

(tick) or @ - in sprint 

 

Brought Forward

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-683 - Getting issue details... STATUS

Owen Stephens



ERM-685 - Getting issue details... STATUS

Ethan Freestone

Further ETA 2w 

  • Some backend complications relating to how dates are stored
  • UI setup to follow
  • Dummy UI set up  
  • Assume resources in KBART file are digital
    • though there may be Print Identifiers and Print Publish Date rather than digital equivalents: treat these as digital without the relevant fields)
    • no need to flag lacking publication date (missing identifier should already be reported)

ERM-696 - Getting issue details... STATUS

(tick)

Blocked by  ERM-711 - Getting issue details... STATUS


ERM-434 - Getting issue details... STATUS  /  ERM-644 - Getting issue details... STATUS  

steve.osguthorpe  / Peter Böhm

Further code review changes requested.

Expected to push within the hour. 


ERM-655 - Getting issue details... STATUS

steve.osguthorpe

Sprint Focus

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-700 - Getting issue details... STATUS

steve.osguthorpe
.

ERM-702 - Getting issue details... STATUS

steve.osguthorpe


ERM-711 - Getting issue details... STATUS

steve.osguthorpe

Prioritise above  ERM-655 - Getting issue details... STATUS


ERM-703 - Getting issue details... STATUS

(tick)

May be required by  ERM-711 - Getting issue details... STATUS


ERM-698 - Getting issue details... STATUS  /  ERM-699 - Getting issue details... STATUS

(tick)

Date format should reflect system locale in Edit (as used in View).  Stripes objects pass in the locale. May need separate library (such as moment) to extract the format without affecting value translation. 


ERM-714 - Getting issue details... STATUS

Aditya matukumalli
Pick list explicitly conditionally hidden as part of ERM-683. To be reverted. 

ERM-715 - Getting issue details... STATUS

Aditya matukumalli  / Peter Böhm

Currently no UI validation in place.  Needs proper backend validation also. Some current experiences: 

  • Backend, eg, is currently forcing decimal values to an integer (Grails autoconversion). 
  • Entering more than 255 characters in text type returns null value.

Frontend validation messages to reflect the type permitted for the specific license term or supplementary information.

Backend validation currently happens after binding. Some extra non-trivial functionality would be needed to intercept raw JSON.  Some straightforward validation options to prioritise: 

  • Required
  • is RefData 

ERM-713 - Getting issue details... STATUS

Gill Osguthorpe Owen Stephens

Effectively a batch operation, exporting report to tabular format. Should be facilitated easily enough because of JSON handling / output.  New specific JSON file could be created for batch. License endpoints can be filtered by ID/OR. 

Selecting multiple licenses isn't currently possible.

  • Basket is used for agreement resources. Is this an appropriate model for licenses as well. (May need to disambiguate resource and (potential) agreement basket in Agreements going forward.)
  • Or would line-select checkboxes in search results work instead? Pagination could be a gotcha. 

Expected to come ready for licenses in Sprint 84, and packages etc before too long.