/
2020-03-25 ERM Delivery Weekly Update

2020-03-25 ERM Delivery Weekly Update

Owned by Jag Goraya
Last updated: Mar 25, 2020

Meeting Details

Date

 

Time

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

LocationVideo Call in FOLIO Slack: #erm-developers

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions


30 minsWIP Updates

QA / UAT: 

  • ERM-785 - Getting issue details... STATUS
  • LAS:eR
    • demo script on Friday

Code Review

  • ERM-782 - Getting issue details... STATUS

In Progress 

  • ERM-705 - Getting issue details... STATUS
    • backend changes merged Tuesday
    • ready for frontend wiring
    • should be straightforward - out today
  • ERM-777 - Getting issue details... STATUS
    • debating in stripes how to avoid side-effects
    • expecting to complete today, depending on edge cases
    • deleting an agreement wouldn't remove from middle pane
    • compare with LKB - which has fewer constraints
  • ERM-547 - Getting issue details... STATUS
    • looking for add decision in GOKb adaptor - doesn't exist there (as in ingestor service)
    • GOKb adaptor ignores things it doesn't need
    • internal format may need to be changed to populate status (to allow read-in and interpret)
  • ERM-793 - Getting issue details... STATUS
    • tag exists now
    • traced back 7 layers to a root point, but is there a better way to access the object?
    • preferred option is to add a boolean flag directly to applicable methods
    • ignore redundant adaptors - apply to GOKb
  • ERM-735 - Getting issue details... STATUS
    • can't delete or add values to internal picklists, only edit existing labels and values
    • so, disable add new and delete, and limit edit to label/values

Sprint Backlog

  • ERM-786 - Getting issue details... STATUS
    • merged - ready for QA
  • ERM-788 - Getting issue details... STATUS
    • embargo is taking priority (ERM-800)
  • ERM-794 - Getting issue details... STATUS  /  ERM-795 - Getting issue details... STATUS
  • ERM-796 - Getting issue details... STATUS  
    • how to test backend? through frontend!
    • close this and test via 797/798
  • ERM-797 - Getting issue details... STATUS  /  ERM-798 - Getting issue details... STATUS  / 
  • ERM-801 - Getting issue details... STATUS
  • ERM-803 - Getting issue details... STATUS
    • re ERM-803 "support" cannot support, eg, AND for different values of the same property (including as arrays)
  • ERM-800 - Getting issue details... STATUS
    • confirmed requirements
    • should be ready to (1) add to data model and (2) include in import spec
    • slightly different to KBART - two statements (unit and length)
    • keep same naming convention as KBART ("moving wall ")
  • ERM-748 - Getting issue details... STATUS
    • expecting to resolve by mid-sprint
  • ERM-805 - Getting issue details... STATUS  
    • needs wireframes
  • ERM-807 - Getting issue details... STATUS
    • needs definition

Needs Elaboration

  • NA
  •  

10 mins

New Issues

Raised / brought into sprint: 

  • ERM-785 - Getting issue details... STATUS
  • ERM-553 - Getting issue details... STATUS
    • check that the name doesn't include only whitespace (after trim)
    • return an error in UI 
    • applies to licenses as well
    • validator is in stripes-erm-components

<15 minsAOB

Importing terms from LAS:eR - nothing is done with some data, eg, some paragraph fields. This can be ignored for FOLIO for now. 



Related content