ERM Sprint 97

Sprint Goal / Focus

  •  

Sprint Schedule

  • Sprint: 97
  • Release: Honeysuckle
  • Quarter: 2020 Q4
  • Start Tues 8 Sep, 2pm UK
  • Finish Fri 18 Sep, 12pm UK


Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions

Lead Roles:

QA Environment: 

  • folio-testing 
  • (folio-snapshot is on pre-JDK11 ERM)

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-1000 - Getting issue details... STATUS

In QA

ERM-904 - Getting issue details... STATUS

Returned to Dev. 


ERM-1097 - Getting issue details... STATUS

In QA

ERM-1098 - Getting issue details... STATUS

In QA

ERM-1099 - Getting issue details... STATUS

In QA

ERM-943 - Getting issue details... STATUS  /  ERM-986 - Getting issue details... STATUS


ERM-943 Blocked pending ERM-1053

ERM-986 In QA: Failed

JSON should support new field for publicationType, rather than reuse existing Type. Should not be making guesses about what the row type is at this point. 

On ERM-986: TODO

  • Reject JSON import row if Type field is set to something other than serial or monograph
  • Add new field publicationType to JSON to populate titleInstance only when new or trustedSource

Changes need to happen on (a) import and (b) import validation. 


ERM-740 - Getting issue details... STATUS  /  ERM-742 - Getting issue details... STATUS

ERM-740 In Progress

ERM-742 Ready for Dev

Ethan has reached an impasse. The issue is blocked 500 error when posting custom props to mod-agreements (and possibly mod-licenses). Looks like a Grails 4 triggered issue

Steve O to pick up ERM-904.



ERM-999 - Getting issue details... STATUS

In Progress

TODO:

  • Incorporate backend variables into frontend
  • Renaming them

Uses standard MCL as per other messages. 


ERM-780 - Getting issue details... STATUS

Ready for Dev. Backend sorting verified by Claudia in Sprint 95.

Sorting in backend is confirmed. 

SearchAndSort handles MCL sorting.

TODO: 

  • Look at MCL API for parameters and properties being used for sorting
  • Add sort logic for non-SaS contexts. Can use similar SaS logic as a

Example is in SaS, but also in other apps (eg, ui-inventory). 


ERM-1055 - Getting issue details... STATUS

Ready for Dev.

ERM-943 - Getting issue details... STATUS  /  ERM-1071 - Getting issue details... STATUS

For elaboration 

ERM-1053 - Getting issue details... STATUS



ERM-904 - Getting issue details... STATUS

ERM-1093 ERM-1094

Sprint Focus

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-1100 - Getting issue details... STATUS

In QA

ERM-1087 - Getting issue details... STATUS

Should be very quick.


ERM-1093 - Getting issue details... STATUS

(tick)

Potentially resolved by fixing  ERM-908 - Getting issue details... STATUS


ERM-1094 - Getting issue details... STATUS

(tick)

Potentially resolved by fixing  ERM-908 - Getting issue details... STATUS


ERM-1095 - Getting issue details... STATUS

TODO: Form level validation needed

Error message to be used rather than warning, as that is needed for blocking progress  


ERM-1096 - Getting issue details... STATUS

TODO: Form level validation needed

Error message to be used rather than warning, as that is needed for blocking. 


ERM-883 - Getting issue details... STATUS


Spike to identify what the proposed solution does or does not afford for more efficient or speedy bulk fetching. 

On the face of it, the microservice as presented is being asked to do work it shouldn't be expected to. 

UXPROD-2621 - Getting issue details... STATUS

ERM-1073 - Getting issue details... STATUS

Accessibility issue that has come in externally. 

UXPROD-1759 - Getting issue details... STATUS

ERM-1102 - Getting issue details... STATUS


Stored v dynamic? Trade-off between performance cost of fetch.

  • More info needed ... technical options discussion to follow
  • PO to provide use cases to understand the kinds of operations required ERM-1102 - Getting issue details... STATUS



ERM-1103 - Getting issue details... STATUS

folio_eholdings, folio_erm-comparisons, folio_plugin-find-eresource, folio_plugin-find-agreement, and folio_local-kb-admin



Brought In

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-1114 - Getting issue details... STATUS

Reported as  SUP-19 - Getting issue details... STATUS .

Potential roadblock with GORM/migrations. Hopefully ready for QA Wednesday 16 Sep. 


ERM-1118 - Getting issue details... STATUS

Frontend code is setting type for inward but not outward relationship. 

TODO: 

  • Discuss with Mark D and Steve O the implementation decision behind this. 

ERM-1119 - Getting issue details... STATUS

(tick)

book keeping work, specifically bumping react-intl versions across all our repos


ERM-1111 - Getting issue details... STATUS  /  ERM-1112 - Getting issue details... STATUS



ERM-1106 - Getting issue details... STATUS

(tick)Simple change. 

ERM-1117 - Getting issue details... STATUS