Changes

Jump to navigation Jump to search
no edit summary
Line 8: Line 8:  
* Add support to search into OCR results
 
* Add support to search into OCR results
 
* Create a mini-game to let users turn the Raw OCR into data<br><br>
 
* Create a mini-game to let users turn the Raw OCR into data<br><br>
'''Mentor:''' Stéphane or Laurent<br>
+
'''Mentor:''' Stephane (backend), Sebastien (backend), Johannes (backend), Laurent (backend), Pierre (OCR)<br>
 
'''Technologies:''' Perl, MongoDB
 
'''Technologies:''' Perl, MongoDB
   Line 30: Line 30:  
= Define a proper clean API (new version) =
 
= Define a proper clean API (new version) =
 
The current REST API of the Open Food Facts database was built with time and can be improved from the point of view of its completitude, consistency and error management. This proposal is about defining and implementing a new API, thought from scratch and built by learning from the lessons of the previos experience. Solutions like Swagger can be envisaged to create a self documenting API and automatic bindings for various programming languages, but the proposal is not limited to this.<br><br>
 
The current REST API of the Open Food Facts database was built with time and can be improved from the point of view of its completitude, consistency and error management. This proposal is about defining and implementing a new API, thought from scratch and built by learning from the lessons of the previos experience. Solutions like Swagger can be envisaged to create a self documenting API and automatic bindings for various programming languages, but the proposal is not limited to this.<br><br>
'''Mentor:''' Anca, Stéphane, Vincent, Aleene<br>
+
'''Mentor:''' Anca, Stéphane, Vincent (API design), Aleene<br>
 
'''Technologies:''' Experience with using (and building) APIs, knowledge of REST,  
 
'''Technologies:''' Experience with using (and building) APIs, knowledge of REST,  
  −
= Create a power contribution tool =
  −
Open Food Facts and Open Beauty Facts rely on crowdsourcing. The easier it is for contributors to complete a product, the faster the base grows. This projects is about creating a standalone power-edit tool using the API.
  −
<br><br>
  −
'''Mentor:''' depending on your tech choice<br>
  −
'''Technologies:''' Any web language (Rail, Python, Backend JS framework)<br>
      
= Create an Open Food Facts mobile game =
 
= Create an Open Food Facts mobile game =
Line 48: Line 42:  
= Create a system to update taxonomies from Product Opener =
 
= Create a system to update taxonomies from Product Opener =
 
Many core concepts of the Open Food Facts environment are organized as taxonomies (multilanguage categories of products, additives, etc).
 
Many core concepts of the Open Food Facts environment are organized as taxonomies (multilanguage categories of products, additives, etc).
Currently, we use a wiki based system for managing these taxonomies, that we have to reload in the Product Opener server every time we make updates to it. This is error prone and requires maintenance work. This feature is about adding a system in the Product Opener to allow moderators to define parent categories, add translations, wikidata links, etc.<br><br>
+
Currently, we use a wiki based system for managing these taxonomies, that we have to reload in the Product Opener server every time we make updates to it. This is error prone and requires maintenance work. This feature is about adding a system in the Product Opener to allow moderators to define parent categories, add translations, wikidata links, etc. See [[Global taxonomies]] for more details on taxonomies<br><br>
'''Mentor:''' Stephane or Laurent, Anca<br>
+
'''Mentor:''' Stephane (backend), Sebastien (backend), Johannes (backend), Laurent (backend), Anca<br>
 
'''Technologies:''' Perl, some HTML/JS
 
'''Technologies:''' Perl, some HTML/JS
   Line 55: Line 49:  
Food and cosmetics change over time. Nutrition info, ingredients sometimes slightly change. Our contributors are here to document all that using photos, and then update the product.
 
Food and cosmetics change over time. Nutrition info, ingredients sometimes slightly change. Our contributors are here to document all that using photos, and then update the product.
 
Product Opener already stores these basic changes, but, once a product is edited, we can not see how it evolved over time. This project is about providing an interface for displaying the subsequent revisions of a product and all the tools that come with that (comparisons between versions, rollback, tracing an information to a revision, etc). It would be tremendously interesting for nutrition science and contributors to be able to see how (positive) change happens over time.<br><br>
 
Product Opener already stores these basic changes, but, once a product is edited, we can not see how it evolved over time. This project is about providing an interface for displaying the subsequent revisions of a product and all the tools that come with that (comparisons between versions, rollback, tracing an information to a revision, etc). It would be tremendously interesting for nutrition science and contributors to be able to see how (positive) change happens over time.<br><br>
'''Mentor:''' Stephane or Laurent<br>
+
'''Mentor:''' Stephane (backend), Sebastien (backend), Johannes (backend), Laurent (backend)<br>
 
'''Technologies:''' Perl, some HTML/JS
 
'''Technologies:''' Perl, some HTML/JS
   Line 66: Line 60:  
= Bulk edit with web GUI for mass product modifications =
 
= Bulk edit with web GUI for mass product modifications =
 
Sometimes, the same error can sneak into a massive amount of contribution, for example related to a typo or a misunderstanding on an information on the packaging. In other situations, similar products might need to be updated in a similar way, for example filling in the type of packaging for all products of a same brand. This proposal is about creating a tool that would allow a moderator to easily select the products and perform these bulk changes on the selected products.<br><br>
 
Sometimes, the same error can sneak into a massive amount of contribution, for example related to a typo or a misunderstanding on an information on the packaging. In other situations, similar products might need to be updated in a similar way, for example filling in the type of packaging for all products of a same brand. This proposal is about creating a tool that would allow a moderator to easily select the products and perform these bulk changes on the selected products.<br><br>
'''Mentor:''' Anca, Pierre, Stephane<br>
+
'''Mentor:''' Anca, Pierre, Stephane (backend), Sebastien (backend), Johannes (backend), Laurent (backend)<br>
 
'''Technologies:''' some Perl, HTML/JS, REST<br>
 
'''Technologies:''' some Perl, HTML/JS, REST<br>
  −
= Create a bot to perform smart edits on the products =
  −
Open Food Facts has a basic bot system. You will have to design sensible rules and create an edition bot based on it.<br><br>
  −
'''Mentor:''' Pierre<br>
  −
'''Technologies:''' Pick your favorite
  −
  −
= Create a Google Cardboard / Daydream compatible viewer app =
  −
Enable browsing Open Food Facts in VR with Google Cardboard or Google Daydream. Bonus point if you enable contributions using the camera.<br><br>
  −
'''Mentor:'''<br>
  −
'''Technologies:'''<br>
      
= Re-work gamification and make it an important part of the User experience =
 
= Re-work gamification and make it an important part of the User experience =
 
Currently there is a basic gamification system in Open Food Facts, giving badges to contributors based on their amount and type of contributions. However, this system is not receiving the attention it should, from a developement point of view, and the concept is not exploited to the maximum of its capabilities. As Open Food Facts relies on contributions from users, gamification can be used to improve retention of users, boost their contributions and increase the quality. Also, it can be used as a tool to drive the contributions in a direction that would not be followed naturally by the users but which is very valuable for the purpose of collecting open data. This proposal comprises the re-working of the gamification backend, along with ideas and implementations of the presentation of the badges, to make it an important part of the Open Food Facts experience.<br><br>
 
Currently there is a basic gamification system in Open Food Facts, giving badges to contributors based on their amount and type of contributions. However, this system is not receiving the attention it should, from a developement point of view, and the concept is not exploited to the maximum of its capabilities. As Open Food Facts relies on contributions from users, gamification can be used to improve retention of users, boost their contributions and increase the quality. Also, it can be used as a tool to drive the contributions in a direction that would not be followed naturally by the users but which is very valuable for the purpose of collecting open data. This proposal comprises the re-working of the gamification backend, along with ideas and implementations of the presentation of the badges, to make it an important part of the Open Food Facts experience.<br><br>
'''Mentor:''' Stephane, Anca, Pierre<br>
+
'''Mentor:''' Stephane (backend), Sebastien (backend), Johannes (backend), Laurent (backend), Anca, Pierre (frontend and UX)<br>
 
'''Technologies:''' Perl, HTML/JS, UI/UX<br>
 
'''Technologies:''' Perl, HTML/JS, UI/UX<br>
   Line 102: Line 86:  
= Add content management capabilities to all static pages of the product opener =
 
= Add content management capabilities to all static pages of the product opener =
 
The Product Opener server side software contains, besides the product pages, lots of pages with helper text, explanation and extra information about the elements of the Open Food Facts environment. Currently, these texts are in the source code, or, in the best cases, stored and edited on the wiki and regularily migrated to the Open Food Facts database site. This project is about implementing / integrating a content management system to allow this content to be easily authored by moderators of the site.<br><br>
 
The Product Opener server side software contains, besides the product pages, lots of pages with helper text, explanation and extra information about the elements of the Open Food Facts environment. Currently, these texts are in the source code, or, in the best cases, stored and edited on the wiki and regularily migrated to the Open Food Facts database site. This project is about implementing / integrating a content management system to allow this content to be easily authored by moderators of the site.<br><br>
'''Mentor:''' Anca, Stephane<br>
+
'''Mentor:''' Anca, Stephane or Sebastien <br>
 
'''Technologies:''' basic understanding of CMS, Perl or other technology(?)<br>
 
'''Technologies:''' basic understanding of CMS, Perl or other technology(?)<br>
   Line 112: Line 96:  
'''Mentor:''' Pierre<br>
 
'''Mentor:''' Pierre<br>
 
'''Technologies:''' Perl, REST, Open data concepts, Wiki data<br>
 
'''Technologies:''' Perl, REST, Open data concepts, Wiki data<br>
 +
 +
= Create a power contribution tool =
 +
Open Food Facts and Open Beauty Facts rely on crowdsourcing. The easier it is for contributors to complete a product, the faster the base grows. This projects is about creating a standalone power-edit tool using the API.
 +
<br><br>
 +
'''Mentor:''' depending on your tech choice<br>
 +
'''Technologies:''' Any web language (Rail, Python, Backend JS framework)<br>
 +
 +
= Create a bot to perform smart edits on the products =
 +
Open Food Facts has a basic bot system. You will have to design sensible rules and create an edition bot based on it.<br><br>
 +
'''Mentor:''' Pierre<br>
 +
'''Technologies:''' Pick your favorite
 +
 +
= Create a Google Cardboard / Daydream compatible viewer app =
 +
Enable browsing Open Food Facts in VR with Google Cardboard or Google Daydream. Bonus point if you enable contributions using the camera.<br><br>
 +
'''Mentor:'''<br>
 +
'''Technologies:'''<br>
 +
 
= Create a connected microwave prototype =
 
= Create a connected microwave prototype =
 
*[[Project:Microwave]]<br><br>
 
*[[Project:Microwave]]<br><br>
Line 131: Line 132:     
= Other ideas =
 
= Other ideas =
*[[Project:Archeology]]
  −
*[[Project:Blind people]]
   
*[[Project:Community portal]]
 
*[[Project:Community portal]]
 
*[[Project:Contribute Back]]
 
*[[Project:Contribute Back]]
Line 141: Line 140:  
*[[Project:What's in my yogurt?]]
 
*[[Project:What's in my yogurt?]]
 
*[[Project:Structured Data]]
 
*[[Project:Structured Data]]
*[[Project:Internationalization]] & [[Global taxonomies]] & [[Translations]]
+
*[[Project:Internationalization]] & & [[Translations]]
*[[Project:Fast Food]]
   
*[[Project:Gamification]]
 
*[[Project:Gamification]]
 
*[[Project:Google Glass]]
 
*[[Project:Google Glass]]
Line 148: Line 146:     
*[[Project:OCR]]
 
*[[Project:OCR]]
*[[Project:Public Data]]
  −
*[[Project:Roadmap]]
  −
*[[Project:Social Media]]
  −
*[[Project:Stands]]
   
*[[Project:ProductOpener]]
 
*[[Project:ProductOpener]]
*[[Project:Food Open Data Challenge UK 2014]]
+
 
*[[Project:EU Project Citizen Observatories]]
   
*[[Project:Redesign]]
 
*[[Project:Redesign]]
 
*[[Project:Food establishments]]
 
*[[Project:Food establishments]]
43

edits

Navigation menu