https://folio-org.atlassian.net/browse/UXPROD-1669

https://folio-org.atlassian.net/browse/ERM-306

@Gill Osguthorpe

Carried over for QA

https://folio-org.atlassian.net/browse/ERM-274

@Kurt Nordstrom

BE: 6h FE: 0h

TODO: implement handlers

Expecting something to review on Tuesday. 

https://folio-org.atlassian.net/browse/ERM-362

@steve.osguthorpe

Tenant API endpoints causes both agreements and licenses.

https://folio-org.atlassian.net/browse/UXPROD-1755

https://folio-org.atlassian.net/browse/ERM-359

@Claudia Malzer

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

https://folio-org.atlassian.net/browse/UXPROD-1755

https://folio-org.atlassian.net/browse/ERM-355

@Claudia Malzer

BE:  FE: 

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

• Public notes should not be hidden

https://folio-org.atlassian.net/browse/UXPROD-1513

https://folio-org.atlassian.net/browse/ERM-290

@steve.osguthorpe

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

https://folio-org.atlassian.net/browse/UXPROD-1513

https://folio-org.atlassian.net/browse/ERM-217 / https://folio-org.atlassian.net/browse/ERM-349

@steve.osguthorpe

https://folio-org.atlassian.net/browse/UXPROD-1513

https://folio-org.atlassian.net/browse/ERM-217 / https://folio-org.atlassian.net/browse/ERM-337

@Aditya matukumalli

https://folio-org.atlassian.net/browse/UXPROD-1791

https://folio-org.atlassian.net/browse/ERM-332

Carried over for QA pending completion of https://folio-org.atlassian.net/browse/ERM-290

https://folio-org.atlassian.net/browse/UXPROD-1643

https://folio-org.atlassian.net/browse/ERM-338

@steve.osguthorpe

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

https://folio-org.atlassian.net/browse/UXPROD-1643

https://folio-org.atlassian.net/browse/ERM-182

@steve.osguthorpe

BE 2h

https://folio-org.atlassian.net/browse/UXPROD-1517

https://folio-org.atlassian.net/browse/ERM-265

@John Fereira

• 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

https://folio-org.atlassian.net/browse/UXPROD-1517

https://folio-org.atlassian.net/browse/ERM-327

@Aditya matukumalli

• Backend elements require code review

• UI elements in place

• UI conflicts re translation need resolving

https://folio-org.atlassian.net/browse/UXPROD-1517

https://folio-org.atlassian.net/browse/ERM-215

@John Fereira

• 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

https://folio-org.atlassian.net/browse/UXPROD-1517

https://folio-org.atlassian.net/browse/ERM-328

@Aditya matukumalli

• Should come at the same time as ERM-215

• Frontend needs to be verified

https://folio-org.atlassian.net/browse/UXPROD-1755

https://folio-org.atlassian.net/browse/ERM-356

@Owen Stephens

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)