openfoodfacts / open-prices

An open database of food prices - 🧾💸💰🏷️🤑🍽️
GNU Affero General Public License v3.0
34 stars 10 forks source link

Avoid having a proof with multiple price locations #244

Open raphodn opened 6 months ago

raphodn commented 6 months ago

Story

On price add, we need to check that a same proof is used with the same location as other existing prices for this proof

ArturLange commented 6 months ago

I think it conflicts a little with this idea I've had with adding prices from flyers/leaflets and maybe with GDPR requests https://openfoodfacts.slack.com/archives/C02Q6KM7F/p1707152495571579 Maybe it makes sense to do that checking depending on proof type - e.g. PRICE_TAG or RECEIPT should be connected to a location but GDPR_REQUEST or FLYER (if we decide to add it in the future) not necessarily. What do you think?