Difference between revisions of "Project:WikiBase-OpenFoodFacts"

From Open Food Facts wiki
Jump to navigation Jump to search
Line 4: Line 4:
 
However, Wikibase lacks certain features that are unique to OpenFoodFacts.
 
However, Wikibase lacks certain features that are unique to OpenFoodFacts.
  
This page is aimed at listing the pros and cons, and evaluating the feasability.
+
This page is aimed at listing the pros and cons, and evaluating the feasibility.
  
 
https://www.mediawiki.org/wiki/Extension:Wikibase_Repository
 
https://www.mediawiki.org/wiki/Extension:Wikibase_Repository
Line 10: Line 10:
  
 
==Pros==
 
==Pros==
 +
* Powerful Revision history
 +
* Structured data
 +
* Easy to add new fields
 +
* Integrated API
 +
* Unique identifier in case two products share the same barcode (barcode demoted as a mere value)
 +
* Integrated synonym and translation support
 +
* Ability to link to wikis
 +
* Ability to reuse the data for products in a easy to edit wiki
 
==Cons==
 
==Cons==
 +
* Need to code a beautiful frontend to visualize the data
 +
* Need to code a friendlier frontend to edit the data
 
==Feature developpement needed for feature parity==
 
==Feature developpement needed for feature parity==
 
[[Category:Project]]
 
[[Category:Project]]

Revision as of 20:01, 16 May 2015

This projects aims at evaluating the pros and cons of using Wikimedia, Wikibase Repository and Wikibase Client, the software running Wikidata to operate OpenFoodFacts.

In short, this software enables a collaborative structured data wiki, which is what OpenFoodFacts is about. The pros mainly revolve about the vitality of the codebase and the ecosystem. However, Wikibase lacks certain features that are unique to OpenFoodFacts.

This page is aimed at listing the pros and cons, and evaluating the feasibility.

https://www.mediawiki.org/wiki/Extension:Wikibase_Repository https://www.mediawiki.org/wiki/Extension:Wikibase_Client

Pros

  • Powerful Revision history
  • Structured data
  • Easy to add new fields
  • Integrated API
  • Unique identifier in case two products share the same barcode (barcode demoted as a mere value)
  • Integrated synonym and translation support
  • Ability to link to wikis
  • Ability to reuse the data for products in a easy to edit wiki

Cons

  • Need to code a beautiful frontend to visualize the data
  • Need to code a friendlier frontend to edit the data

Feature developpement needed for feature parity