Licenses (UXPROD-574)

[UXPROD-1557] Manage License properties on License amendments Created: 04/Mar/19  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-158 Set Terms for a License Amendment Closed
Gantt End to Start
has to be done after UXPROD-583 Support licence amendments/addenda Closed
Requires
requires UXPROD-1472 Manage amendments on a license/agreem... Closed
Epic Link: Licenses
Front End Estimate: Medium < 5 days
Front End Estimator: md331 (Inactive)
Development Team: Bienenvolk
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R3
Rank: Lehigh (MVP Summer 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

Licenses can have amendments which specify usage terms (properties) which either add to the core license properties or counter-act them.

This feature is to support adding and displaying properties to license amendments. Data model for amendment terms/properties is delivered as part of UXPROD-583 Closed .

To include:

  • Display of amendment terms within license/license amendment display

Out of scope:

  • User cannot change priority order of amendment
  • Amendment terms are not related to or displayed on agreements (covered in UXPROD-1472 Closed )
    • Display controlling license terms - do we return (a) the original controlling license terms alone along with over-riding amendment terms or (b) just the final calculated terms?


 Comments   
Comment by Owen Stephens [ 15/Mar/19 ]

Was duplicate of https://folio-org.atlassian.net/browse/UXPROD-1573
Have brought over implementer rankings from UXPROD-1573 Closed where appropriate

Comment by Owen Stephens [ 22/Mar/19 ]

Based on feedback from steve.osguthorpe the approach that we'll take will mean that once UXPROD-583 Closed is done, all backend support will be in place for this. That suggests that there is unlikely to be much work to do to deliver this one (as UXPROD-583 Closed will also require the UI for Amendments to be in place)

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

Once UXPROD-583 Closed is complete, this gets a lot easier because that handles the bulk of the work to make the particular view/edit panes available. We already know how to edit/display terms so this will be simpler.

Comment by steve.osguthorpe [ 25/Mar/19 ]

Assuming Backend is covered under UXPROD-583 Closed

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