Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-217

  • 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

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-184

10 minsSprint Completion
  • Merge Cutoff
    • Friday 2pm UK
  • Items at Risk / Spillover
  •  
10 minsUpcoming SprintSee 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

Demo'd
Feature IDIssue IDWho

Notes / TODO


Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-189


Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1597

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-132


Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1520

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-162


Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1520

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-163


Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1601

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-220

Demo'd

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1601

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-219

Demo'd

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1300

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-165

(tick)


Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1660

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-198


Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1159

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-184


Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1513

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-217

10/5/19: Questions raised on 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-217
 about the scope and functionality. Once discussed I'll make a start on the wireframing.

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1548

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-186



Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-218

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

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-190


Same error as ERM-193.

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-193



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 Allen Fereira