<5 mins | Introductions | |
| Call Priorities |
|
| WIP In Progress - ISSUE:
- Progress / Impediments:
- TODO:
- New unknowns:
- Help or input needed:
- ETA for review:
- What progress or impediment on previously stated actions?
- What's left to do?
- Any new unknowns?
- What help or input is needed?
- When expected to be ready for review?
| In Progress-
ERM-2289
-
Getting issue details...
STATUS
- Progress / Impediments:
- Issues with POLine filter
- Getting errors with undefined tags
- TODO:
- New unknowns: NA
- Help or input needed:
- Ethan to help with POLine filter
- ETA for review: Fri/Mon
-
ERM-2288
-
Getting issue details...
STATUS
- Progress / Impediments:
- json works
- has test account for gokb
- needed help from Mortiz to resolve setup issues
- gokb package is imported, waiting for it to present to check that updates reflect in OAI feed (built-in delay)
- TODO:
- Complete test for GOkb once appearing in feed
- Review what attributes are testable for kbart
- Test for kbart
- New unknowns: NA
- not sure whether test exists for kbart import?
- no, it is called directly
- Help or input needed:
- what endpoint to use for kbart?
- look at what the frontend consumes on snapshot, including package information
- triggering gokb harvesting (see vagrant setup on wiki)
- change syncStatus to be refData idle
- reset cursor to 0
- ETA for review: Thu
-
ERM-2312
-
Getting issue details...
STATUS
- Progress / Impediments:
- migration to new domain model should be done
- some issues testing that (reviewing with Ian/Steve to support getting new test users)
- outline of API
- update frontend to use new api
- TODO:
- test functionality equivalence
- confirm outline
- write tests
- major version bump
- New unknowns: NA
- Help or input needed: NA
- ETA for review:
-
ERM-2315
-
Getting issue details...
STATUS
- Progress / Impediments: just started
- TODO:
- extend getResourceIdentifier() with a returnAll boolean parameter
- update agreements to apply logic
- tests
- New unknowns:
- Help or input needed:
- how to see changes?
- grab all resources and count them
- ETA for review: Thu
|
| Pending Blocked - ISSUE
- Blocking conditions
- Action needed
- Are the blocking conditions still relevant?
- What action is needed to unblock, and by whom?
Needs Elaboration - ISSUE:
- Who / When:
- ETA Ready for Dev:
- Who needs to be involved in the elaboration process?
- What is the timeframe for getting input?
- When is the issue expected to be ready for development?
- Who is picking up what next?
- When is next issue expected to start / complete?
- Anything needed to start next issue (dependencies or clarifications)?
| BlockedNeeds Elaboration-
ERM-2314
-
Getting issue details...
STATUS
- moved to Sprint 147 for development
Sprint Backlog - Next Up- Claudia: RTL
- Ethan:
- Monireh: NA
- Peter:
-
ERM-2304
-
Getting issue details...
STATUS
- may have been resolved as part of ERM-2288
-
ERM-2311
-
Getting issue details...
STATUS
|
| At Risk - What is now at risk of not being started this sprint?
- Do any of these take priority over other sprint backlog items?
| Sprint Backlog - to followSprint Backlog - At Risk -
ERM-2306
-
Getting issue details...
STATUS
-
ERM-2307
-
Getting issue details...
STATUS
-
ERM-2308
-
Getting issue details...
STATUS
-
ERM-2309
-
Getting issue details...
STATUS
-
ERM-2310
-
Getting issue details...
STATUS
-
ERM-2313
-
Getting issue details...
STATUS
|
| In Review - Any impediments to review or QA?
- Any useful context, implementation choices or limitations for the reviewer/tester to know ?
| Code Review:-
ERM-2133
-
Getting issue details...
STATUS
QA / UAT - Previously
-
ERM-2234
-
Getting issue details...
STATUS
-
ERM-2093
-
Getting issue details...
STATUS
-
ERM-2214
-
Getting issue details...
STATUS
-
ERM-2220
-
Getting issue details...
STATUS
-
ERM-2278
-
Getting issue details...
STATUS
-
ERM-2279
-
Getting issue details...
STATUS
-
ERM-2290
-
Getting issue details...
STATUS
Bugfix Cycle
|
| Release Candidates - What has passed QA since last dev call?
- What has been closed since last dev call?
| Closed: Morning Glory R2022.2Stories / Bugs-
ERM-1979
-
Getting issue details...
STATUS
-
ERM-1986
-
Getting issue details...
STATUS
-
ERM-2043
-
Getting issue details...
STATUS
-
ERM-2044
-
Getting issue details...
STATUS
-
ERM-2157
-
Getting issue details...
STATUS
-
ERM-2076
-
Getting issue details...
STATUS
-
ERM-2120
-
Getting issue details...
STATUS
Closed: Morning Glory Big Fix R2022.2Stories / Bugs-
ERM-2305
-
Getting issue details...
STATUS
Releases-
ERM-2317
-
Getting issue details...
STATUS
Closed: Nolana R2022.3Stories / BugsRTL / TasksClosed (No ERM Release) |
| AOB
| New IssuesAdded to sprint Not added to sprint- ERM–2318 to ERM-2328: stripes-erm-components should be a peer
- will need to add as a dev-dep as well as a peer-dep
Other
ERM-2289
-
Getting issue details...
STATUS
- Button grouping reviewed at SIG 10 Aug: https://folio-project.slack.com/archives/CAYCU07SN/p1660646280421719
- Preference is collapsible tabs (~10d effort)
- New issue to be raised
- Options to do the non-collapsible alternative: routing v state
- Routing: parameterising the tabs in the url (more effort)
- would result in a breaking change for agreements and eresources
- routing would need to change again if we ended up going collapsible again
- State: or add a state, to determine which search the user is directed to. (less effort)
- rouing would stay flat but be presented hierarchically in the UI
- would cause fewer problems, but is ickier
- Overall effort 1d-2d
|