BE: 6h FE: 0h

TODO: implement handlers

Expecting something to review on Tuesday. 

BE: h FE: h

• Public / internal term values need to be handled 
•  consider term value notes refactor in future

• Extend shape for new fields
• Component affected: license terms list

BE:  FE: 

• Public / internal notes need to be handled in web-toolkit-ce
• Public notes should not be hidden

BE: expected Tuesday

• ERM-333 Needs code review once delete functionality and ERM-349 completed
  • Everything in place.
  • TODO (BE): Error log display needs verifying (date stamp fix required)
• ERM-334
  • TODO (BE): Requires delete functionality to be implemented; 
  • Front-end behaviour to be applied (return to the job list)
• ERM-351 Front end integration tests
  • tests flaky against MCL
  • some more tests to be  written for view job details

• How to specify the errors for different types of source?

• PR amends required:
  • indentation 
  • if statement
• URL field data confirmed to be coming from pti
  • output QA'd 
  • happy to release once PR amends resolved

• 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

Would it be better to put public facing URL into OKAPI and serve that instead of increasing memory requirements through an additional Edge module?

Further clarification required.

JSON format to be defined (ERM-360)