Skip to end of metadata
Go to start of metadata
Meeting Details
Date | |
---|
Time | 09:30am ET, 2:30pm UK, 3:30pm Germany |
---|
Location | Video Call in FOLIO Slack: #erm-developers |
---|
Goals
Discussion items
Time | Item | Notes | Action Items |
---|
<5 mins | Introductions | |
|
30 mins | WIP Updates | Code Review: -
ERM-1012
-
Getting issue details...
STATUS
-
ERM-1050
-
Getting issue details...
STATUS
- needs checking similar to licenses
- changes applied to datepickers outside of card components sent back to In Progress
In Progress -
ERM-1000
-
Getting issue details...
STATUS
- mostly working on datepicker fixes and code review, so not far progressed apart from requirements clarifications
- should be "Suppress from discovery" rather than "Suppress from delivery"
- Relates to ERM-1004
-
ERM-1004
-
Getting issue details...
STATUS
- Relates to ERM-1000
- fiddly migrating agreements settings page from redux to finalform, and modconfig
- more complex than importing fields because of save handling
- decided not to add in a fieldarray
-
ERM-1032
-
Getting issue details...
STATUS
/
ERM-1049
-
Getting issue details...
STATUS
- Code refactored to improve performance
- Load more added, Load All not to be added
- ERM-1049 closed
- Parent ERM-1032 ready for release
- Investigation tasks to be separated out
Sprint Backlog -
ERM-1010
-
Getting issue details...
STATUS
- making progress on first subtask
- looks straightforward
-
ERM-1002
-
Getting issue details...
STATUS
- to be handled as part of ERM-1000
-
ERM-904
-
Getting issue details...
STATUS
= pending return of Steve O
-
ERM-1053
-
Getting issue details...
STATUS
- not sure how to reject a single entry in a JSON file
- (if that is even the ask)
- ingest process should split it out and reject the individual line
- should it be handled in KBART import process or Gokb adaptor?
- re-assigning to Owen for clarification ... JSON doesn't reject, KBART does. What should happen?
Needs Elaboration -
ERM-999
-
Getting issue details...
STATUS
QA / UAT: -
ERM-943
-
Getting issue details...
STATUS
/
ERM-986
-
Getting issue details...
STATUS
- If TrustedSource is off, no fields should be updated
- If TrustedSource is on, simple fields are handed but identifiers are updated through JSON patching
- refData rather than string, but should be based on enrichment routine
- returned to sprint backlog
-
ERM-1006
-
Getting issue details...
STATUS
-
ERM-994
-
Getting issue details...
STATUS
-
ERM-1052
-
Getting issue details...
STATUS
/
ERM-1051
-
Getting issue details...
STATUS
- PR still pending merge from John Coburn for functionality to work, but the component should now be visible completely
- JC working on validation which is not firing correctly.
-
ERM-1054
-
Getting issue details...
STATUS
| |
10 mins | New Issues | Raised / to bring into sprint: NA -
ERM-1041
-
Getting issue details...
STATUS
-
ERM-1042
-
Getting issue details...
STATUS
-
ERM-1054
-
Getting issue details...
STATUS
-
ERM-1053
-
Getting issue details...
STATUS
= returned to Owen for clarification
Raised: -
ERM-1056
-
Getting issue details...
STATUS
- potential translation issue - code changes necessary
- pending snapshot / testing rebuild
- bumped back to QA
-
ERM-1055
-
Getting issue details...
STATUS
- assigned to Steve for post=JDK11
- could block release of comparison functionality
|
|
<15 mins | AOB |
| |