As a PM, I want user of our BN demo to "rate" the results delivered by our algorithm results. We need to store these results for later computation. My strong feeling is, that if we get enough attention, we can ask the community to build BN into their tools and continue to rate results. Over time, we should have (vandalism allowing), a labeled set of YES news and NOT news.

This method can make feedback on the BN results easier to gather and more functional in the longterm.

To do

• Like and dislike button, instead of indications column
• Store num_like and num_dislike in DB
• Once dislike or like is clicked, store in a table "reactions" with all the column values
• Do not allow users to like or dislike more than once, for a row
• Do no allow clicking both like and dislike, for a row.

Acceptance criteria

1. This ticket completion is critical to the launch of the public demo.
2. Rcesults should mimic true results of Boolean as close as possible
3. Does not need to be the most sophisticated system. This is a PoC in itself. Where the data is stored, does not matter as long as it is easily accessible. I tend to prefer spreadsheets.
4. Very lean UI, no pop ups. We want to include "add a comment". That seems like a good idea, but if so it must appear only over where the thumbs up/down was.
5. Only one reaction per user per line item, if possible. Once you react you cannot react again to the same result. To avoid button mashing, trolling. If this involves having to log-in, we can skip it. Can we do it by saving the session token?

Things to consider:

• We will have to store this data for longer than three months
• This must be ready and functional before/by the time we set the demo public
• Reaction UI does not need to be thumbs up/down necessarily.

QA

• @FNavas-foundation to pre QA