[MLEARN-10] Provide user-friendly way to configure the ranking strategy Created: 06/Mar/19  Updated: 17/Apr/19  Resolved: 20/Mar/19

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

Type: Improvement Priority: Neutral
Reporter: Christoph Meier Assignee: Federico Grilli
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 2d 1.35h
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLPER-72 Make Find Bar result ranking user spe... Closed
is related to MLEARN-12 DOC: YAML based periscope ranker syst... Closed
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)
Epic Link: Periscope improvements
Sprint: Foundation 6, Foundation 7
Story Points: 2

 Description   

Current situation

MGNLPER-72 basically provides the API to use different strategies to memorize periscope result search ranking.

Per default the module comes with the strategy to memorize the ranking for every user.
Plus it provides one other implementation to memorize the ranking per user, IF a user has the role ranker or superuser - which allows to control the number of users with their own distinct ranking network.

The "issue"

Currently, to changing the strategy requires a change in the module-descriptor of the periscope-result-ranker module. Such a change requires the build of a custom module, rebuilding the module or hacking into the jar-file ... and a redeployment of the webapp.

Aim

Provide a mechanism which allows "easy" configuration of the strategy. E.g. on the config. workspace under /modules/periscope-result-ranker/config.

Further info

https://wiki.magnolia-cms.com/display/ARCHI/2019-01-17+Memory+issues+with+user+specific+result+rankings?focusedCommentId=176794676#comment-176794676

 

 


Generated at Mon Feb 12 02:29:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.