<5 mins

Introductions

• Attendees / Apologies

• Upcoming Availability

• Next ERM developer gathering:
  • October
  • All other details TBD

45 mins

• In Progress
  • what's left?
• Pending:
  • what's dependent?
  • what's clear to proceed?

5+

AOB

PR expected this afternoon

Status as per ERM-355

• ERM-334 - expected today
  • Delete functionality in place.
  • Front-end behaviour to be applied (confirmation dialog, toast, return to the refreshed job list)
• ERM-333 Code review pending pending Tested this morning
  • Error log display needs verifying (date stamp fix required) 
  • ERM-349  not required for this
  • ERM-334
• ERM-351 Front end integration tests

Clear for front-end implementation

•  Backend elements require code review
•  UI elements in place
• TODO: UI conflicts re translation need resolvingresolving 

• Duplicates issue resolved
• TSV capability (ERM-325) included  
• TODO: split coverage information needs calculating correctlyshould this be two lines in the flat KBART file  YesTODO: 
• • Issue with db connections
  • trying to make work with streams

• Should come at the same time as ERM-215
• Frontend needs to be verified

• to begin today

• Clear to begin (needs backend work of course to integrate)

• How Need to specify the errors for different types of source?rework the package import service first (to be delivered as part of ERM-349)

TODO

• Backend elements require code review
• UI elements in place
• UI conflicts re translation need resolving

• Duplicates issue resolved
• TSV capability (ERM-325) included  
• TODO: split coverage information needs calculating correctly
  • should this be two lines in the flat KBART file  Yes

• Should come at the same time as ERM-215
• Frontend needs to be verified

• Potentially needs to build on the package import rewqrk (to be delivered as part of ERM-349)

TODO:

• Confirmation of outstanding ERM-361 queries
• ERM-360 Define JSON format
  • need to confirm which parts of the agreement are public
  Clarify rationale of Edge v OKAPI 
  • (expecting to use existing JSON format, just need to confirm which fields are exposed)
• Clarify implementation via Edge v OKAPI
  • Implement for OKAPI for now
  • This should be sufficient, based on Khalilah's comment