1098626 - Recent recommendation user opt-in has no data in engine

Status: RESOLVED WONTFIX

(Marketplace Graveyard :: Consumer Pages, defect, P3)

Description

[Rob Hudson [:robhudson]]

Scenario: A user who opted out of recommendations gets their install data removed from the backend recommendation engine. They then decide to opt-in, which shows the nav, and they visit the recommended tab but the time between opting-in and the engine pulling in their data is too short so the engine doesn't know about this user. If this user has installed apps and we show them popular apps they may think the system isn't working.

Best way to handle this? Maybe show a notice of some sort that it may take up to 24 hours to populate? Or maybe spin off a task to send all the install data to the engine using their API -- I'm not sure how long it takes to calculate the recommendations but the messaging could be the same but just a shorter time. Other ideas?

Comment 1

[Andy McKay]

Making P3, don't think this is a blocker, just a little weird in some use cases.

Comment 2

[linas]

We can create an API called update_user where you pass list of the apps that user has. Such functionality already can be achieved via multiple install_apps calls. We can update the user model in milliseconds (I assume 500ms is enough, but it is too expensive to do on each ordinary request), so when he comes to the recommendation page, we show the fresh recommendations. 

I create a ticket https://github.com/grafos-ml/frappe/issues/19 for this feature request.

In fact, I think in the future our preferred way of updating user info should be through API and not reading the dumps.

Comment 3

[Wil Clouser [:clouserw]]

comment 2 sounds good. thanks.