/
2019-05-15 ERM Delivery Weekly Update

2019-05-15 ERM Delivery Weekly Update

Jun 04, 2019

Meeting Details

Date

 

Time

09:30am ET, 2:30pm UK, 3:30pm Germany

LocationVideo Call in FOLIO Slack: #erm-developers

Participants

Apologies

Discussion items

TimeItemNotesAction Items
<5 minsIntroductions
  •  

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 minsDemos

(star)  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 minsSprint Completion
  • Merge Cutoff
    • Friday 2pm UK
  • Items at Risk / Spillover
  •  
10 minsUpcoming SprintSee ERM Next Sprint Candidates list in https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=89&view=planning.nodetail
5+AOB
  •  


Sprint WIP Demos

Delivery Board: https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=89

Demo'd
Feature IDIssue IDWho

Notes / TODO


ERM-189 - Getting issue details... STATUS

Kurt Nordstrom


UXPROD-1597 - Getting issue details... STATUS

ERM-132 - Getting issue details... STATUS

steve.osguthorpe


UXPROD-1520 - Getting issue details... STATUS

ERM-162 - Getting issue details... STATUS

John Fereira md331 (Deactivated)


UXPROD-1520 - Getting issue details... STATUS

ERM-163 - Getting issue details... STATUS

md331 (Deactivated)


UXPROD-1601 - Getting issue details... STATUS

ERM-220 - Getting issue details... STATUS

Aditya matukumalli


Demo'd

UXPROD-1601 - Getting issue details... STATUS

ERM-219 - Getting issue details... STATUS

Aditya matukumalli

Demo'd

UXPROD-1300 - Getting issue details... STATUS

ERM-165 - Getting issue details... STATUS

(tick)


UXPROD-1660 - Getting issue details... STATUS

ERM-198 - Getting issue details... STATUS

Kurt Nordstrom


UXPROD-1159 - Getting issue details... STATUS

ERM-184 - Getting issue details... STATUS

Kurt Nordstrom


UXPROD-1513 - Getting issue details... STATUS

ERM-217 - Getting issue details... STATUS

Gill Osguthorpe


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

Claudia Malzer



ERM-218 - Getting issue details... STATUS

John Fereira

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.