Licenses (UXPROD-574)

[UXPROD-583] Support licence amendments/addenda Created: 17/May/18  Updated: 16/Sep/20  Resolved: 12/Jun/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q2 2019
Parent: Licenses

Type: New Feature Priority: P3
Reporter: Owen Stephens Assignee: Owen Stephens
Resolution: Done Votes: 0
Labels: erm, licenses
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by ERM-82 Support amendments for a license Closed
is defined by ERM-147 Manage amendments for a license Closed
Gantt End to Start
has to be done before UXPROD-1472 Manage amendments on a license/agreem... Closed
has to be done before UXPROD-1473 Support for attaching documents to li... Closed
has to be done before UXPROD-1557 Manage License properties on License ... Closed
Epic Link: Licenses
Front End Estimate: XL < 15 days
Front End Estimator: md331 (Inactive)
Back End Estimate: Medium < 5 days
Development Team: Bienenvolk
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Licenses can be amended, often done to indicate changes of content or to specify new/different terms to those specified in the original license. Amendments may apply to all resources covered by the original license, or to a subset of resources.

This feature is to support the addition of Amendments to existing licenses. These amendments can have documents attached which describe the amendment, and terms that are derived from the document. Amendments can have their own start/end dates and statuses independently from the license they amend.

Also note that each amendment can optionally apply to any Agreements linked to the license. While linking licenses to Agreements is not in the scope of this feature, the requirements for the indicating the status of amendments in relation to a linked agreement may be of some consideration when developing this feature

*Notes*
Amendments share most of the properties of licenses, so plan is to

  • Abstract from licenses and amendments all shared properties
  • Still have licenses and “amending license”
  • Amending licenses have to be attached to a license
  • Licenses can apply to agreements, and amending licenses can apply to agreements only where the license they amend is already applied to the agreement

Licenses vs Amendments

Property License Amendment
Type Yes No
Status Yes Yes
End date semantics Yes Yes
Name Yes Yes
Description Yes Yes
Start date Yes Yes
End date Yes Yes
Orgs Yes No
Tags Yes Yes
Docs Yes Yes
Supplementary docs Yes Yes


 Comments   
Comment by Jag Goraya [ 22/Mar/19 ]

Owen Stephens what does end-date semantics mean please? is it the open-ended option?

Comment by Owen Stephens [ 22/Mar/19 ]

Jag Goraya yes that's correct

Comment by Owen Stephens [ 22/Mar/19 ]

Note that ERM-82 Closed has the detail for this including wireframes

Comment by md331 (Inactive) [ 22/Mar/19 ]

Front-end estimate is based on the mockups for ERM-82 Closed . I think it'll necessitate a rethink of our routing and page layout structure, which may have knock-on effects to how we fetch data and provide it to components in lower levels.

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