ERM Sprint 81

ERM Sprint 81

Sprint Goal / Focus

  • Support for non-serial resources

Sprint Schedule

  • Sprint: 81

  • Release: Fameflower

  • Quarter: 2020 Q1

  • Start Monday 13 Jan, 2pm UK

  • Finish Friday 24 Jan, 12pm UK

 

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • WolfCon w/c 20 Jan. @Owen Stephens NA.

Lead Roles:

  • Front End Code Review: @md331 (Deactivated)

  • Back End Code Review:  @steve.osguthorpe

  • QA: @Owen Stephens@Gill Osguthorpe

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

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

@md331 (Deactivated)

 

 

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

@Peter Böhm

Almost code complete. Query about updating the database to reflect code changes. Potentially look at examples in migrations folder in mod-agreements. 

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

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

@steve.osguthorpe

Functionality complete - cannot be tested yet, as there is an issue with tests suite. 

 

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

@Owen Stephens

 

 

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

@Claudia Malzer

STCON-92 is now resolved, so this is unblocked.

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

 

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

@Ethan Freestone

Add to e-resource preview panel in the first instance.

 @Owen Stephens to define rules for these and subsequent items, eg

Review UI changes needed with Gill

 

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

@steve.osguthorpe

.

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

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

Q: how to identify a record?

See notes on ERM Sprint 79-80. Owen to followup with Steve.

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

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

Needs further definition. May be dependent on ERM-485. 

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

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

@Jag Goraya to followup with @steve.osguthorpe re streaming dependency.

 

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

@Peter Böhm

 

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

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

@md331 (Deactivated)

@Owen Stephens

Novelty: 

  • repeatable filters

  • filter by both type and value (different to Org / Roles)

Needs wireframe, and may be dependent on ERM-591.

Investigation goals for Sprint 81: 

  • What support / refactoring is needed from custom properties / backend to facilitate repeatable and nested filters possible? (BE)

    • How to manage functionality in UI? (UX/PO/FE)

 

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

@Aditya matukumalli

 

 

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

 

No longer effectively blocked by STCON-57