brandtg/Dinr — Issue #3: Compute negation of intersection for attribute display
Author: brandtg
Created: 2012-01-27 20:09:09+00:00
State: open

The attributes displayed in comparison view for restaurant A should be {metadataA} - {metadataB}, and for restaurant B, {metadataB} - {metadataA}. That is, we should only display metadata that are unique to each restaurant, and not values that they share. For example, if restaurant A had the metadata {"ambience": "hipster", "priceRange": "$$"} and B had {"ambience": "hipster", "priceRange": "$"} , we would only display price range on both.

The attributes that we select to display might be able to be intelligently picked as a result of machine learning, or could be manually selected by us (i.e. we could say that price range is more important than good for kids).