Folksonomy Engine/Uses cases
What do Folksonomy Engine makes possible? We list here some use cases. These ones are a good way to test how Folksonomy Engine can work.
For the key (property) names, we use the same convention as OpenStreetMap: minus letters with underscores for spaces. Eg. seen_on_tv
Seen on TV (advertising)
What kind of products are most seen on TV? Can we compare these products with the rest of their category? Is it possible to collect those products without barcode?
Proposed keys (properties):
| Key (property) | Values | Description | Type | Comments |
|---|---|---|---|---|
seen_on_tv
|
yes or no
|
Is this product have been seen on TV? No value doesn't mean it can't be yes or no, it's just unknown. | closed list (yes or no) | |
seen_on_tv:date
|
Examples:
|
The date when it has been seen on TV. An interval is a better information, but a fixed date is a good first step. | ISO 8601 format | Entered manually or by a date picker |
seen_on_tv:tv_channels
|
Examples:
|
On what channel? | open list | TODO: see if we can reuse wikidata TV channels |
Products with film- or cartoon characters
These data can represent some interest. The characters can infer the target of the product. It can be interesting to understand if certain types of products are targeting special public, kids for example.
| Key (property) | Values | Description | Type | Comments |
|---|---|---|---|---|
packaging:has_character
|
yes or no
|
Is there a film- or cartoon character on this product? No can be interesting to share. Lack of value doesn't mean it can't be yes or no, it's just unknown.
|
closed list (yes or no) | |
packaging:character:date
|
Examples:
|
The date when it has been seen on the packaging. An interval is a better information, but a fixed date is a good first step. | ISO 8601 format | Entered manually or by a date picker |
packaging:character
|
Examples:
|
The common name of the character. | open list | |
packaging:character:wikidata
|
Example: Q51785 (Star Wars' Stormtrooper)
|
The wikidata reference, to disambiguate the character. | wikidata |
Recalled products
Listing products recalls can be an interesting service.
Proposed keys (properties):
| Key (property) | Values | Description | Type | Comments |
|---|---|---|---|---|
recalled_product
|
yes, no
|
The product has been recalled or not. No value doesn't mean it can't be yes or no, it's just unknown. | closed list (yes or no) | |
recalled_product:date
|
Examples:
|
The date when it has been recalled. | ISO 8601 format | Entered manually or by a date picker |
recalled_product:comments
|
Any more information can be put here. Eg. the serial numbers of the product. | Free text | ||
recalled_product:link
|
Examples: | A link to the official source of the recall. | link | Possibility of many links? |
Some official websites dealing with product recalls:
- Europe:
- European Union website: https://webgate.ec.europa.eu/rasff-window/screen/list
- France: https://rappel.conso.gouv.fr/
- USA:
Annotation
Providing further information about products for other contributors, and even for users in some cases. Here are some proposed keys:
| Key (property) | Values | Description | Type | Comments |
|---|---|---|---|---|
fixme
|
yes or no
|
Does this product's data has to be fixed? | closed list (yes or no) | See fixme tag in OpenStreetMap database. |
producer_data_issue
|
Any string or sentence. Examples:
|
Some data printed by the producer on the product are wrong, without any doubt. | ||
multiple
|
Examples:
|
When a barcode is used for different products. | open list | |
wikipedia
|
Examples:
|
The specific wikipedia URL corresponding to this product. Users can add the two letter language to precise a page in a specific language. | URL | Should be controlled. |
wikidata
|
Example: Q212193 (for Nutella)
|
The wikidata reference, to allow links with other data. | wikidata |