Public and internal license term values (ERM-357)

[ERM-359] Allow term values in a specific license to override default visibility Created: 24/Jun/19  Updated: 08/Aug/19  Resolved: 08/Aug/19

Status: Closed
Project: ERM Platform
Components: ui-licenses
Affects versions: None
Fix versions: None
Parent: Public and internal license term values

Type: Sub-task Priority: TBD
Reporter: Jag Goraya Assignee: Owen Stephens
Resolution: Done Votes: 0
Labels: erm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-2.png    
Issue links:
Requires
requires ERM-358 Support public and internal-only lice... Closed
Sprint: ERM Sprint 69
Development Team: Bienenvolk

 Description   

Purpose: to filter out the property value of terms on public feeds, specifically discovery systems.

  • So if we have an API which can be used by a user facing system, when the details for “license terms applying to this resource” is made, we need to be able to only return values that are OK to display publicly.
  • Generally we can say that for a term, there is a default of whether the term value would be public or not (as per ERM-358 Closed )
  • But in some cases people may want to override - to hide values or display values that would normally be shown/hidden

This is controlled at a license term value level and will require addition to the license term edit UI for users to be able to set the Visibility of the term value as either Public or Internal.



 Comments   
Comment by Jag Goraya [ 24/Jun/19 ]

Elaboration based on Slack conversation between Owen Stephens and steve.osguthorpe.

Comment by steve.osguthorpe [ 29/Jul/19 ]

The visibility dropdown should add a property named `internal` and its value should be `true` / `false`

Comment by steve.osguthorpe [ 30/Jul/19 ]

Back end work is now in licenses.

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