/
2020-02-12 ERM Weekly Delivery Update

2020-02-12 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Feb 12, 2020

Meeting Details

Date
 
Time

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

LocationVideo Call in FOLIO Slack: #erm-developers

Participants

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions


30 minsWIP Updates

QA / UAT: all in good place to test 

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

  • ERM-434 - Getting issue details... STATUS
  • ERM-683 - Getting issue details... STATUS
  • ERM-714 - Getting issue details... STATUS
  • ERM-719 - Getting issue details... STATUS

Code Review

  • ERM-644 - Getting issue details... STATUS  - good to move to QA

In Progress 

  • ERM-685 - Getting issue details... STATUS  / ERM-687 - Getting issue details... STATUS  /  ERM-690 - Getting issue details... STATUS  
    • backend PR submitted
    • frontend / UI begun this morning 
    • query about selection tool that allows for type-ahead filter on Edit
      • free text is used for Provider
      • update existing package expected to autofill - that's the long-term goal
    • PO happy to go with single form with just free text
    • given this, should be ready for code review today
    • there may be some attention needed for dynamic array handling in the future (as with Organizations)
      • should this be done at a (smart) component level?
      • maybe ... not a concern for it now, or any clear value for typedown at the moment

Sprint Backlog

  • ERM-689 - Getting issue details... STATUS
    • issue updated to show database location of fields
    • 4 of the fields are coming off the title instance (so should be good to update existing KBART export service)
    • date_monograph_published_print  and date_monograph_published_online may be slightly more tricky
    • if trying to populate both, we would have to look for sibling title references. That would be a useful general ERM utility, so is perhaps best built elsewhere first to be reusable, rather than burying in an export lookup. 
      • ermResources/electronic
  • ERM-711 - Getting issue details... STATUS  - to pick up after Steve returns from holiday
  • ERM-703 - Getting issue details... STATUS
  • ERM-715 - Getting issue details... STATUS
    • validation is in code, but not being actioned
    • needs further investigation
    • lower priority than LASER
  • ERM-698 - Getting issue details... STATUS  /  ERM-699 - Getting issue details... STATUS
    • ready to pickup by Adi
  • ERM-655 - Getting issue details... STATUS  /  ERM-427 - Getting issue details... STATUS

Needs Elaboration

  • ERM-681 - Getting issue details... STATUS  /  ERM-716 - Getting issue details... STATUS
  • ERM-689 - Getting issue details... STATUS
  • ERM-696 - Getting issue details... STATUS
  • ERM-700 - Getting issue details... STATUS  /  ERM-701 - Getting issue details... STATUS
  • ERM-702 - Getting issue details... STATUS
  • ERM-713 - Getting issue details... STATUS  /  ERM-718 - Getting issue details... STATUS
    • selection via SaS
    • leaning towards
      • export rather than on-screen report in first instance
      • multiple licenses in tabular format
    • still to determine how to  handle selection across results pages
    • further conversation about output needs in next ERM subgroup (19 Feb)
    • doesn't rule out supplementing with a basket mechanism
      • could work nicely to build up results across multiple queries without having to deal with complex queries
  • ERM-720 - Getting issue details... STATUS
  •  

10 mins

New Issues

Raised / brought into sprint: 

  • ERM-721 - Getting issue details... STATUS
    • Adi to have a look
    • Not yet been tested on Supplementary Properties - Gill/Owen to verify
  • ERM-722 - Getting issue details... STATUS
    • looks like URL structure has changed in mod/ui-organizations-storage
    • This is a breaking change done as part of an in-progress/unversioned tech debt refactor
    • Cannot easily be done outside of major release versions, where explicit dependencies are defined
    • No heads-up / warning that this - some project communication issues to be addressed
    • Awaiting clarification from Dennis/Craig as to whether this i a permanent change
    • There would likely be peer dependency failures if ERM built to the new (unversioned) specification



<15 minsAOB





Related content