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), rather than the status of the amendment captured in the licenses app.
License with a single amendment with conflicting terms:
- 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.
- 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
|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|
|Define testable scenarios with data||Closed|