Project:Open-Prices: Difference between revisions
(new section "Usage ideas") |
mNo edit summary |
||
| Line 42: | Line 42: | ||
|- | |- | ||
| Price comparison between stores for a specific product | | Price comparison between stores for a specific product | ||
| | | | ||
|- | |- | ||
| | | ... | ||
| | | | ||
|} | |} | ||
| Line 65: | Line 64: | ||
| Launch meeting | | Launch meeting | ||
|- | |- | ||
| 21/ | | 21/10/2023 | ||
| First prototype by a volunteer. Official Github repo created | | First prototype by a volunteer. Official Github repo created | ||
|- | |- | ||
| 20-22/ | | 20-22/10/2023 | ||
| OFFdays 2023 in Paris: discussions on how to store price data | | OFFdays 2023 in Paris: discussions on how to store price data | ||
|} | |} | ||
Revision as of 13:49, 9 November 2023
The goal of this project is to store prices of food products and to make them available to the public, through a REST API and web interface.
The data is licensed under OdBL 1.0, images (proof) are licensed under CC-BY-SA 4.0.
Data sources
We currently consider the following data sources:
- crowdsourced price data, with if possible a proof (either a store receipt, or a picture of the product with its price tag). Prices obtained through GDPR request to stores are also welcome.
- prices provided by retailers, through the API
- prices obtained from users on the web using a web extension
Crowdsourcing the data collect has the advantage of mobilizing the community around the project and of getting traction and visibility. We want to reach a critical mass of data to make the project useful, and we think that crowdsourcing is the best way to achieve this goal. Scan parties in stores can be organized to collect data.
We currently don't allow scraping as a data source for a first version, as it bears some legal concerns and technical challenges to overcome:
- the database protection law in Europe may prevent us from extracting the price from the website, if we don't have the authorization of the website owner
- the price can be different depending on the user selected store. Furthermore, some retailers (in the UK for example) start to adapt their prices depending on the user profile (if they are identified as a regular customer, or if they are a new customer). This makes it difficult to have a consistent price for a product.
Current status
A POC developed during OFFdays 2023 is currently running here : https://open-prices.osc-fr1.scalingo.io (Github code)
A migration is in progress to host the code on https://github.com/openfoodfacts/open-prices and deploy the service on https://openprices.org (on Open Food Facts server).
We're not displaying the price on Open Food Facts website yet, as it has to be thoroughly considered first (and as Open Food Facts website attracts a lot of traffic).
Challenges
- On receipt images, there may be some personal data (name, fidelity card number, etc.). We need to find a way to remove this data before publishing the image.
- Find a way to collect efficiently prices (probably through a mobile app)
Usage ideas
| In a few words | Details |
|---|---|
| Price trends for a specific product | |
| Price comparison between stores for a specific product | |
| ... |
Documentation and communication
Slack channel: #prices
Weekly meeting: every Wednesday at 2PM (CET), feel free to join if you're interested in the project: https://meet.google.com/oin-hiqp-tmd
Timeline
| Date | Description |
|---|---|
| 08/11/2023 | Launch meeting |
| 21/10/2023 | First prototype by a volunteer. Official Github repo created |
| 20-22/10/2023 | OFFdays 2023 in Paris: discussions on how to store price data |