Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 7
Next »
Meeting Details
Date | |
---|
Time | 09:30am ET, 2:30pm UK, 3:30pm Germany |
---|
Location | Video Call in FOLIO Slack: #erm-developers |
---|
Discussion items
Time | Item | Notes | Action Items |
---|
<5 mins | Introductions | | |
| Vagrantbox / backend development settings | - MD has backend and frontend on separate machines
- CM - potentially with network mount - had some success with that
- SO - will require network bridge / address changes to the vagrant files
|
|
30 mins | Demos | Vote for priority in #erm-developers poll
ERM-217
-
Getting issue details...
STATUS
- ui-data-import is hardcoded for MARC files, so is not useful for our purposes
- How big are the package files?
- If large, this probably needs to do a background task.
- Therefore we need to track and present (a) upload and (b) import status
- Is there an existing progress indicator UI element? If not, can promote the data-import indicator, and implement within Agreements setting (rather than agreements)
- How do we handle error reporting? Report exceptions and failures at end of batch
ERM-184
-
Getting issue details...
STATUS
| |
10 mins | Sprint Completion | - Merge Cutoff
- Items at Risk / Spillover
| |
10 mins | Upcoming Sprint | See ERM Next Sprint Candidates list in https://issues.folio.org/secure/RapidBoard.jspa?rapidView=89&view=planning.nodetail |
|
5+ | AOB | | |
Sprint WIP Demos
Delivery Board: https://issues.folio.org/secure/RapidBoard.jspa?rapidView=89
Feature ID | Issue ID | Who | Notes / TODO |
---|
|
ERM-189
-
Getting issue details...
STATUS
| |
|
UXPROD-1597
-
Getting issue details...
STATUS
|
ERM-132
-
Getting issue details...
STATUS
| | |
UXPROD-1520
-
Getting issue details...
STATUS
|
ERM-162
-
Getting issue details...
STATUS
| | |
UXPROD-1520
-
Getting issue details...
STATUS
|
ERM-163
-
Getting issue details...
STATUS
| | |
UXPROD-1601
-
Getting issue details...
STATUS
|
ERM-220
-
Getting issue details...
STATUS
| | |
UXPROD-1601
-
Getting issue details...
STATUS
|
ERM-219
-
Getting issue details...
STATUS
| |
|
UXPROD-1300
-
Getting issue details...
STATUS
|
ERM-165
-
Getting issue details...
STATUS
| | |
UXPROD-1660
-
Getting issue details...
STATUS
|
ERM-198
-
Getting issue details...
STATUS
| | |
UXPROD-1159
-
Getting issue details...
STATUS
|
ERM-184
-
Getting issue details...
STATUS
| |
|
UXPROD-1513
-
Getting issue details...
STATUS
|
ERM-217
-
Getting issue details...
STATUS
| | 10/5/19: Questions raised on
ERM-217
-
Getting issue details...
STATUS
about the scope and functionality. Once discussed I'll make a start on the wireframing. |
UXPROD-1548
-
Getting issue details...
STATUS
|
ERM-186
-
Getting issue details...
STATUS
| |
|
|
ERM-218
-
Getting issue details...
STATUS
| | PR submitted. A separate issue to consider is that description fields are differently CLOB or varchar(255), depending on app. ERM to apply going forward: - single line text: varchar(255)
- textarea: CLOB
|
|
ERM-190
-
Getting issue details...
STATUS
| | Same error as ERM-193. |
|
ERM-193
-
Getting issue details...
STATUS
| | Grails is attempting to delete the agreement, but not remove the tag link, which violates the validation. Delete should cascade, but not where a tag is re-used. steve.osguthorpeto take a look and feed back to John Fereira. |