Claudia Malzer

BE 0h FE 8h

TODO: differences in SASQ routing from Licenses to Agreements, so slightly different. 

Aditya matukumalli to support Claudia Malzer  on accomodating the differences.

Expected to be complete by end of week. 

md331 (Deactivated)

BE 0h FE 2w

Incorporates 

steve.osguthorpe

BE 15h FE 0h

Driven by https://folio-project.slack.com/archives/CAYCU07SN/p1557421022302700 

1. Generate json schema for mod-agreements and mod-licenses.
2. Write explainer documentation: https://folio-project.slack.com/archives/CAYCU07SN/p1557491555305700?thread_ts=1557421022.302700&cid=CAYCU07SN

•  steve.osguthorpeto confer with md331 (Deactivated)on the explainer requirements

Explainer documentation in Github. Dev questions raised as tasks/bugs in Jira.

Peer review by dev team. 

steve.osguthorpe

BE 8h FE 0h

Relates to 

Investigation is to test there are no issues with 

1. using java-local and java-date types
2. front-end conversion of proposed approach

John Fereira

Kurt Nordstrom

BE 2h FE 0h.

Feeds into a piece of work around data integrity. 

Requirement is still to validate a coverage statement, but not reject it:

• coverage end < coverage start

Output of this is to introduce the mechanism to not fail the import for recoverable errors. 

Logging of errors should be done in a way that can be easily reported to user, but is out of scope (see, eg 

Kurt Nordstrom

Claudia Malzer

steve.osguthorpe

steve.osguthorpe

Kurt Nordstrom

BE ?? FE 0h.  

Some potential reuseable code in stale branch for MODERM-23. 

To complete Scenarios 1 and 2, but not Scenario 3. 

Should this even be an ERM job? OKAPI authentication is project-wide. 

•  Owen Stephensto rewrite story to clarify requirements

Aditya matukumalli

Aditya matukumalli

Aditya matukumalli

 Requires 

 Clashes with 

 Requires 

 Clashes with 

 Requires 

 Clashes with 

steve.osguthorpe Should the backend provide the data, or should the frontend fetch this (as done with organizations)?

 Clashes with