UXPROD-1511 - Licenses - Notes Support Closed

ERM-269 - Manage 'Notes' on Licenses Closed

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. 

ERM-253 - Convert from SearchAndSort to SearchAndSortQuery Closed

md331 (Deactivated)

BE 0h FE 2w

Incorporates  ERM-237 - Move the "Agreements, E-resources" menu options to the "Search & filter" panel Closed

ERM-254 - Document ERM JSON Schema Closed

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. 

ERM-276 - Investigate cause and impact of date/timezone issues Closed

steve.osguthorpe

BE 8h FE 0h

Relates to  ERM-189 - Custom coverage dates display with a time offset in some environments Closed  and  ERM-262 - Agreement start and end date display with a time offset in some environments Closed . 

Investigation is to test there are no issues with 

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

UXPROD-1517 - Support export of entitlements in current agreements for discovery systems Closed

ERM-265 - Export Agreement data as JSON Closed

John Fereira

UXPROD-1643 - KB Data integrity checking and error handling Closed

ERM-182 - On sync with remote KB, keep TIPPs where coverage data is incompatible Closed

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  ERM-183 - Log issues with remote KB sync Closed  for logging, and  ERM-217 - Import package via UI Closed  for presenting.)

UXPROD-1643 - KB Data integrity checking and error handling Closed

ERM-183 - Log issues with remote KB sync Closed

Kurt Nordstrom

UXPROD-1597 - Support annotations for license terms Closed

ERM-268 - Adding a note to a license term without setting a term value fails silently Closed

Claudia Malzer

UXPROD-1302 - Apply Tags: ERM: Agreements Records Closed

ERM-190 - Deleting a tag shared between two agreements throws an error Closed

steve.osguthorpe

ERM-193 - Deleting a License (and possibly Agreement) with a Tag isn't possible Closed

steve.osguthorpe

UXPROD-1159 - Support for file upload for document attachments Closed

ERM-274 - Add cleanup task for orphan file uploads Closed

Kurt Nordstrom

UXPROD-1517 - Support export of entitlements in current agreements for discovery systems Closed

ERM-215 - Export Agreement data as KBART Closed

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

UXPROD-1601 - Support Organisations app as source of Organisations Closed

ERM-230 - Display interface data using Card design Closed

Aditya matukumalli

UXPROD-1159 - Support for file upload for document attachments Closed

ERM-277 - Document file upload errors are sometimes hidden Closed

Aditya matukumalli

UXPROD-1159 - Support for file upload for document attachments Closed

ERM-278 - Document file uploads should show a spinner when upload is in progress Closed

ERM-261 - Restructure the Agreement accordions Closed

Aditya matukumalli

UXPROD-1157 - Link resources in agreements (agreement lines) to Purchase Orders / Purchase Order Lines Closed

ERM-239 - Link existing Purchase Order Line (POL) to an Agreement Line Closed

 Requires  UINV-7 - Add invoice line based on POL Closed

 Clashes with  ERM-253 - Convert from SearchAndSort to SearchAndSortQuery Closed

UXPROD-1157 - Link resources in agreements (agreement lines) to Purchase Orders / Purchase Order Lines Closed

ERM-240 - Display Purchase Order Line (POL) information with an Agreement Line (edit view) Closed

 Requires  ERM-239 - Link existing Purchase Order Line (POL) to an Agreement Line Closed

 Clashes with  UINV-7 - Add invoice line based on POL Closed

UXPROD-1157 - Link resources in agreements (agreement lines) to Purchase Orders / Purchase Order Lines Closed

ERM-242 - Display Purchase Order Line (POL) link on an Agreement Line Closed

 Requires  ERM-239 - Link existing Purchase Order Line (POL) to an Agreement Line Closed

 Clashes with  UINV-7 - Add invoice line based on POL Closed

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

UXPROD-1751 - eUsage/agreements integration: select usage data provider Closed

ERM-273 - Manage usage data providers on agreements Closed

 Clashes with  ERM-253 - Convert from SearchAndSort to SearchAndSortQuery Closed