Changes

Jump to navigation Jump to search

GSOC/2023 ideas list (view source)

Revision as of 11:02, 7 February 2023

7,785 bytes added ,  11:02, 7 February 2023
no edit summary
Line 47: Line 47:  
<span id="bring-taxonomy-editor-to-a-fully-usable-tool"></span>
 
<span id="bring-taxonomy-editor-to-a-fully-usable-tool"></span>
 
=== Bring Taxonomy editor to a fully usable tool ===
 
=== Bring Taxonomy editor to a fully usable tool ===
 +
 +
<span id="description-1"></span>
 +
==== Description ====
 +
 +
Taxonomies are at the heart of Open Food Facts in many aspects. It helps identify components (ingredients, labels, brands,…) and link them to useful properties, at the base of nutri-score, eco-score, allergens identification and some other properties.
 +
 +
Each taxonomy is a DAG (directed acyclic graph) where leaves have one or more parents. Currently the taxonomy is in a raw text file in our repository: https://github.com/openfoodfacts/openfoodfacts-server/tree/main/taxonomies.
 +
 +
While effective for the application, this format is quite cumbersome to edit for contributors.
 +
 +
Taxonomy editor was started during last Google Summer of code. Thanks to the work of Aadarsh, we got a first demonstration of the product, and it’s been in continuous development since then. But a boost would be needed to make it a really usable project.
 +
 +
<span id="expected-outcomes-1"></span>
 +
==== Expected outcomes ====
 +
 +
Minimum feature set to be added would be: good inline documentation to on board users, an ergonomic UI, searching for potential issues in the taxonomy, tracking modification to enable undoing changes and comparison to original taxonomy, helping find entries to translate. The idea is to enable a wide public of contributors to participate in adding translation or simple items (like ingredients) while ensuring quality and helping moderators validate changes. Another important technical feature will be to augment significantly test coverage (at least on backend part).
 +
 +
From there, according to the pace of the projects many more features could be added which would be of great benefit: embarked assistance integrating tools (eg. searching / linking to wikidata, or wiktionary), integration of the products database (eg. seeing which entries need to be added or translated first), navigation in the taxonomy.
 +
 +
An important aspect: as this tool is meant to live a long time quality and maintainability of the project is important.
 +
 +
<span id="project-information-1"></span>
 +
==== Project information ====
 +
 +
<ul>
 +
<li><blockquote><p>repository: [https://github.com/openfoodfacts/taxonomy-editor/ <u>https://github.com/openfoodfacts/taxonomy-editor/</u>]</p></blockquote></li>
 +
<li><blockquote><p>Slack channels: #taxonomy-editor</p></blockquote></li>
 +
<li><blockquote><p>Potential mentors: Daniel, Alex</p></blockquote></li>
 +
<li><blockquote><p>Project duration: 350 hours</p></blockquote></li>
 +
<li><blockquote><p>Skills required: Reactjs / Python / Neo4j</p></blockquote></li>
 +
<li><blockquote><p>Difficulty rating: Medium</p></blockquote></li></ul>
 +
 +
<span id="section"></span>
 +
===  ===
 +
 +
<span id="section-1"></span>
 +
=== <br />
 +
===
 +
 +
<span id="improve-our-producer-platform-to-the-next-level"></span>
 +
=== Improve our producer platform to the next level ===
 +
 +
<span id="description-2"></span>
 +
==== Description ====
 +
 +
One lesser known but very important aspect of Open Food Facts is that, not only do we encourage citizens to contribute to the database (crowdfunding) but we also propose producers to do so. The incentive for them is to ensure they provide up to date and accurate information, that their products are well represented (eg. with studio photography). They also get hints on data quality to make their product better, which is an important goal to Open Food Facts.
 +
 +
Thanks to the support of the national French public health agency Santé Publique France, the platform is already alive and working. Though it is a bit rough for our users that are not tech savvy, also there are a lot of features which could help adoption and lessen the support needed to operate it.
 +
 +
Technically the producer platform uses the same code base as the main website.
 +
 +
<span id="expected-outcomes-2"></span>
 +
==== Expected outcomes ====
 +
 +
The project will bring many new features to the producer platform. Here are some of the current priorities: add more inline help, make UX more convenient, support advanced updates patterns on fields, add a workflow to product edition, connect to our internal CRM (allow automating many tasks), collect more statistics on usage, support more fields and format for data import, more robust import/publishing workflows and add more tests.
 +
 +
Extended goals include adding rules to help producers make products with better Eco-score, advanced features to make editing products easier (like picture upload).
 +
 +
<span id="project-information-2"></span>
 +
==== Project information ====
 +
 +
<ul>
 +
<li><blockquote><p>presentation of the platform: https://world.pro.openfoodfacts.org/</p></blockquote></li>
 +
<li><blockquote><p>repository: https://github.com/openfoodfacts/openfoodfacts-server/</p></blockquote></li>
 +
<li><blockquote><p>Slack channels: #productopener</p></blockquote></li>
 +
<li><blockquote><p>Potential mentors: Stephane, Alex</p></blockquote></li>
 +
<li><blockquote><p>Project duration: 350 hours</p></blockquote></li>
 +
<li><blockquote><p>Skills required: Perl</p></blockquote></li>
 +
<li><blockquote><p>Difficulty rating: Medium</p></blockquote></li></ul>
 +
 +
<span id="section-2"></span>
 +
===  ===
 +
 +
<span id="section-3"></span>
 +
=== <br />
 +
===
 +
 +
<span id="data-quality-moderation-hub"></span>
 +
=== Data Quality &amp; Moderation Hub ===
 +
 +
<span id="description-3"></span>
 +
==== Description ====
 +
 +
Open Food Facts infrastructure is currently focused on reflecting the current state of the database, which is its primary goal. However, it would be beneficial to introduce a queue/backlog system to coordinate the efforts of users in data cleaning and moderation.
 +
 +
The system currently provides some level of coordination through the facets, indicating missing nutritional data and providing a list of products that need completion. However, this system lacks flexibility.
 +
 +
<span id="expected-outcomes-3"></span>
 +
==== Expected outcomes ====
 +
 +
Currently, robots send messages to Slack channels that the admins need to clean. A queue of remaining problems to moderate would simplify the workload for the team and make it easier to track progress. It would also allow users to request moderation or ask questions.
 +
 +
In a perfect world, users would be able to create their own tasks, such as &quot;extract nutritional table,&quot; and associate barcodes with each step.
 +
 +
<ol style="list-style-type: decimal;">
 +
<li><blockquote><p>select nutritional table image</p></blockquote></li>
 +
<li><blockquote><p>crop nutritional table image</p></blockquote></li>
 +
<li><blockquote><p>fill nutriments</p></blockquote></li></ol>
 +
 +
The MVP would include a back-end with an API for moderation, providing a table with information such as barcode, image_id, type_of_problem, author (including Robotoff), and moderation status (has_been_moderated). The front-end would allow users to delete pictures and mark elements as moderated.
 +
 +
The next steps would involve supporting questions from users and allowing moderators to answer them. This would include:
 +
 +
<ul>
 +
<li><blockquote><p>Extending the database to save questions</p></blockquote></li>
 +
<li><blockquote><p>Send emails with the answer from moderation interface</p></blockquote></li>
 +
<li><blockquote><p>Add buttons in main website to send questions</p></blockquote></li></ul>
 +
 +
<span id="project-information-3"></span>
 +
==== Project information ====
 +
 +
<ul>
 +
<li><blockquote><p>repository: https://github.com/openfoodfacts/hunger-games/</p></blockquote></li>
 +
<li><blockquote><p>Slack channels: #hunger-games #robotoff #data-quality</p></blockquote></li>
 +
<li><blockquote><p>Potential mentors: Raphael, Charles, Pierre, Alex</p></blockquote></li>
 +
<li><blockquote><p>Project duration: 350 hours</p></blockquote></li>
 +
<li><blockquote><p>Skills required: PostgreSQL, Python, Frontend (React/ReactNative or Flutter)</p></blockquote></li>
 +
<li><blockquote><p>Difficulty rating: Medium</p></blockquote></li></ul>
Retrieved from "https://wiki.openfoodfacts.org/Special:MobileDiff/18863"

Navigation menu