Licenses (UXPROD-574)

[UXPROD-609] Manage organisations for a License Created: 23/May/18  Updated: 17/Mar/22  Resolved: 14/Mar/19

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

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

Issue links:
Defines
is defined by ERM-7 Add an Organisation to a License Closed
is defined by ERM-10 Remove an Organisation from a License Closed
is defined by ERM-8 Add an Organisation to an existing Li... Closed
is defined by ERM-9 Change a license organisation's role Closed
Epic Link: Licenses
Front End Estimate: Medium < 5 days
Back End Estimate: Medium < 5 days
Development Team: Bienenvolk
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R1
Rank: 5Colleges (ERM Jun 2020): R1
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

Enable the addition of organisations to licenses with different roles.

  • needs to be able to accommodate potential lists of 1000s of available organisations
  • needs to be consistent UI with Agreements
  • Role must be specified for each Organisation
  • no role constraints (number or type)
  • creating an Organisation in this context is specifying the name only
  • duplicate organisations should not be created

Roles:

  • Licensor
  • Licensee
  • Consortium
  • Consortium Administrator

Out of scope:

  • edit an organisation
  • define or edit organisation roles
  • roles cannot be changed by tenant
  • contacts for organisations added to Licenses
  • filtering License search by Organisation or Organisation Role

TBC whether implementation will initially support Organisations are shared between Folio apps within a tenant implementation



 Comments   
Comment by md331 (Inactive) [ 06/Feb/19 ]

There's currently some debate about how the list of organisations to select from will be managed by the backend. An identical feature already exists for Agreements which users can assign organisations to, and the backend for that is in place. So the question when designing the backend for this is:

Should the organisation management used in mod-agreements be generalised so that it can be used by ui-licenses?

Required for Generalising the Existing Code (non-exhaustive)

  • everything in the existing org code is named like `SubscriptionAgreementOrg` so that could be weird if we’re using the same one
  • the `owner` of that model is a `SubscriptionAgreement` so work would definitely need to be done to generalise it
  • the org role RDV is also already managed under the SAOrg domain

Issues with Maintaining Separate Lists

  • feels like bad UX because users will see the same UI but with different organisations available in both places. Especially problematic once we apply different permissions for assigning an existing org to a license/agreement vs creating a new organisation.
  • the new code will be basically copy-pasted from mod-agreements with some names changed which feels really dirty
  • we won't be able to reuse frontend components specifically designed to manage selecting from the the long list of organisations
Generated at Fri Feb 09 00:09:08 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.