[MGNLPER-101] Bootstrap role "ranker" Created: 06/Mar/19  Updated: 17/Apr/19  Resolved: 25/Mar/19

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1

Type: Improvement Priority: Neutral
Reporter: Christoph Meier Assignee: Hieu Nguyen Duc
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 2.5h
Time Spent: 5.5h
Original Estimate: 1d

Issue Links:
dependency
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Epic Link: Periscope improvements
Sprint: Foundation 7
Story Points: 1

 Description   

MGNLPER-72 comes with an alternative implementation of a result ranking memory strategy.

As described in https://documentation.magnolia-cms.com/display/DOCS61/Search+result+ranking+configuration - when using the info.magnolia.periscope.rank.ml.jcr.JcrUserRoleNetworkStorageStrategy implementation class - mgnl-admins should "tag" users with the role superuser or ranker in order to make sure these users get their distinct ranking network.

We should bootsrap the role ranker with the appropriate ACLs for the JCR workspace rankings.



 Comments   
Comment by Roman Kovařík [ 06/Mar/19 ]

Can the role be configurable? Can we use multiple "ranking" roles with their own network?

Comment by Christoph Meier [ 06/Mar/19 ]

When using JcrUserRoleNetworkStorageStrategy:
As far as I understand it now - currently ... assign a user one of the roles - superuser or ranker - and that user gets its own distinct network.
Users without one of these roles utilize the global (per instance) ranking network.

However ... using roles raise a lot of ideas ... like having one network for one specific role - allowing to share one network among a similar group of users.
However ... that would go further as what has been described in 2019-01-17 Memory issues with user specific result rankings ... see comment from Simon => https://goo.gl/XzvKJp

Generated at Mon Feb 12 10:28:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.