Closed animeshpathak closed 9 years ago
Is the "augmented" part always a binary decision? In your example, we have only "sponsored" POIs (because they have been somehow positively rated by your friends) OR "normal" POIs? Or are there some POIs which are more "sponsored" than others? In summary, I'm asking if there is a notion of relevance score that can be the output of the query manager when matching with preferences and/or social profiles (friends)?
In case of a binary decision, the UI could indeed simply display a heart when results are recommended. In case of a real ranked list of results, the UI could display the associated relevance score.
Is the "augmented" part always a binary decision? In your example, we have only "sponsored" POIs (because they have been somehow positively rated by your friends) OR "normal" POIs? Or are there some POIs which are more "sponsored" than others? In summary, I'm asking if there is a notion of relevance score that can be the output of the query manager when matching with preferences and/or social profiles (friends)?
It is binary when augmenting based on ratings (of the user or his contacts), and continuous when augmenting based on location.
In case of a binary decision, the UI could indeed simply display a heart when results are recommended. In case of a real ranked list of results, the UI could display the associated relevance score.
Not sure how we would show the score when sorting by increasing distances from a certain location.
What will you send additionally in the JSON? The relevance score of the augmented items?
Tagging @Kai-Dominik for reference.
It will be as per how you want. Do you want augmented JSON objects in the list, or a separate list?
@congkinh please propose how you would like to send augmented responses for both the location-based and ratings-based cases.
Hi all,
I will send you back JSON result containing information about "augmented": true / false
. For example, if your query looks like SELECT ?s ?p ?o
, the result will contain a list of "s": ..., "p": ..., "o": ..., "augmented": true /false
. augmented: true
means that the result should be highlighted.
I just deployed a version on dev server with augmented
property added in the JSON result. Could you please check that? If you want another format, please tell me. Thanks!
/cc @Kai-Dominik , @cmbarbu , @animeshpathak
If you can also add the column name "augmented" to "head->vars" then it is okay for us
Everything seems to work fine on beta. Please check and close if no problems are found.
Worked perfectly! Closing it.
@anthonyjameson : we added 5 stars on your behalf to the Oaisi village hotel. It should show up at the top when you augment using your own ratings.
Thanks for all these efforts. I've just arrived in Trento and will try these things out this evening and/or tomorrow morning. - Tony
Sent from the iPad of Anthony Jameson, DFKI
On Jan 14, 2015, at 21:56, Animesh Pathak notifications@github.com wrote:
Worked perfectly! Closing it.
@anthonyjameson : we added 5 stars on your behalf to the Oaisi village hotel. It should show up at the top when you augment using your own ratings.
— Reply to this email directly or view it on GitHub.
Thanks Tony. Please also be sure to go to
and give it 5 stars. That way, if you need to, you can show people that the augmentation is happening because of the ratings you gave to the hotel on G+.
Housekeeping: As all the itemes in this issue were addressed (though not checked), I am clossing this issue. Please reopen this issue if needed.
(Please move the "assigned" value to the next person in the checkbox list when your bit is done.) The augmented query system currently hides the difference between the high-value responses (e.g., rated highly by my friends) and normal responses. While this is correct from an app perspective, it is difficult to demo.
Todo: