Agreements (UXPROD-573)

[ERM-430] Display license and license amendment terms on agreement Created: 13/Aug/19  Updated: 23/Sep/19  Resolved: 23/Sep/19

Status: Closed
Project: ERM Platform
Components: mod-licenses
Affects versions: None
Fix versions: None
Parent: Agreements

Type: Story Priority: TBD
Reporter: Owen Stephens Assignee: Unassigned
Resolution: Done Votes: 0
Labels: erm
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-1472 Manage amendments on a license/agreem... Closed
Relates
relates to ERM-464 Agreements | Amendment with the most ... Closed
Sub-tasks:
Key
Summary
Type
Status
Assignee
ERM-441 Define testable scenarios with data Sub-task Closed Owen Stephens  
Sprint: ERM Sprint 72
Development Team: Bienenvolk
Epic Link: Agreements

 Description   

License terms are presented in the Agreements view, in the 'License and business terms' accordian. The following rules are used to determine when terms from a license or amendment are presented, if there is a conflict.

In all cases below, the amendment is considered Current if the "Status (this agreement)" field for the amendment is set to Current (as per ERM-428 Closed ), rather than the status of the amendment captured in the licenses app.

License with a single amendment with conflicting terms:

  1. the amendment will always be seen as additive to the license. i.e. license terms will still apply and any additional terms in the amendment will also apply.
  2. If the amendment includes a term that is also in the license, the amendment value for that term will apply instead of the license term

For example:

Term Controlling License Current Amendment Resulting terms on Agreement
Walk-in Access Permitted not set Permitted
Include in e-reserves not set Permitted Permitted
Text and data mining Not permitted Permitted Permitted

It will always be the case that the amendment ‘amends’ the license so we will always assume that terms of a current amendment terms will add to and (where necessary) override the terms stated in the underlying license.

Where there are multiple “current” amendments at the same time the amendment with the most recent "Start date" will take precedence. For example:

Term Controlling License Current Amendment 1 (SD: 01/01/2019) Current Amendment A (SD: 02/02/2019 Resulting terms on Agreement
Walk-in Access Permitted not set Not permitted Not permitted
Include in e-reserves not set Permitted Not permitted Not permitted
Text and data mining Not permitted Permitted Not permitted Not permitted


 Comments   
Comment by steve.osguthorpe [ 09/Sep/19 ]

Enrich the license display when we have a `context` variable so that we can mutate the list of terms to only show terms that apply to the contextual resource. This should mean we can implement without the need to change any UI.

Comment by steve.osguthorpe [ 13/Sep/19 ]

md331 License that is embedded when fetching the agreement now has mutated custom props representing the aggregation of the amendments set to current for the license. Could easily have the "appllicableTerms" in a separate property against the license instead so if you feel it's too confusing then I can change it. I did it this way to mean we shouldn't need to change the UI.

Comment by Jag Goraya [ 16/Sep/19 ]

Ready for QA pending ERM-428 Closed

Generated at Fri Feb 09 00:20:17 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.