ERM Sprint 82

ERM Sprint 82

Sprint Goal / Focus

  •  Migration / Import / Custom Properties

Sprint Schedule

  • Sprint: 82

  • Release: Fameflower

  • Quarter: 2020 Q1

  • Start Monday 27 Jan, 2pm UK

  • Finish Friday 7 Feb, 12pm UK

 

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions: NA

Lead Roles:

  • Front End Code Review: @md331 (Deactivated)

  • Back End Code Review:  @steve.osguthorpe

  • QA: @Owen Stephens

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 

 

Brought Forward

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-2081

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

@Owen Stephens

In QA 

 

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

@Owen Stephens

In QA 

 

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

@Owen Stephens

In QA 

 

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

@Owen Stephens

In QA 

 

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

@Owen Stephens

In QA 

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

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

@md331 (Deactivated)

Waiting on completion of ERM-644

  • Migration script needs to be fixed for new column added (with@Peter Böhm)

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

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

@Peter Böhm

 

 

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

Does need resolving,  but not especially urgent. 

PO decision input from @steve.osguthorpe

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

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

@Owen Stephens

In QA 

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

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

@Owen Stephens

In QA 

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

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

@Owen Stephens

In QA 

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

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

@Owen Stephens

In QA 

 

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

@Ethan Freestone

In Progress Needs BigTest tests to be written

 

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

 

 

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

@steve.osguthorpe

Higher priority than ERM-647 and ERM-633. Should resolve ERM-427.

Workaround: is to manually add JOIN and sort on title of resource. 

 

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

 

Should be resolved by ERM-655.

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

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

@md331 (Deactivated)

See https://folio-org.atlassian.net/browse/ERM-684

Sprint Focus

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-2234

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

 Spike: @steve.osguthorpe

Custom Properties in this context are like Custom Properties ("terms") in Licenses.

Possible conflict of functionality with MOD-CUSTOM-FIELDS (https://github.com/folio-org/mod-custom-fields)

Putting into a separate module inhibits searching.

TODO: 

  1. Steve to review mod-custom-fields

  2. Implement backend

    1. using terms implementation

    2. or using mod-custom fields

  3. Define UI work based on method 

  4. Build out UI for settings

  5. Implement add/edit UI

Front-end implementation with terms is complicated because they are stored as object arrays. 

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

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

 Backend

@Owen Stephens

@Ethan Freestone

@Gill Osguthorpe

TODO

  1. Supply KBART mapping (Owen)

  2. Controller for TSV parsing (Ethan)

  3. Define front end requirements / UI (Gill)

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

https://folio-org.atlassian.net/browse/ERM-668 / https://folio-org.atlassian.net/browse/ERM-684

@Owen Stephens

Draft UIs defined.  Some questions about rules / operations that can be supported. 

Currently being refined: operator precedence (perhaps some kind of expression grouping. 

@Owen Stephens to merge into ERM-668 and close ERM-684

Has potential relationship to ERM-683.

 

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

  

Related to service that occurs prior to migrations. 

Required for live upgrade in second sprint week. 

 

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

@Claudia Malzer

Entitlements package view used to have this problem, but is now fixed. Recent PR related to paging in agreements should help with addressing this.