Wikidata:Property proposal/Universal Product Code
Universal Product Code
edit Not done
Description | UPC-A barcode number |
---|---|
Represents | Universal Product Code (Q1193047) |
Data type | String |
Allowed values | [01678]\d{11} (12 digits) |
Example | |
Source |
|
Formatter URL | http://www.searchupc.com/?q=$1 or http://www.upcitemdb.com/upc/$1 or http://www.upcdatabase.com/item/$1 |
UPC | EAN | Type |
---|---|---|
0 | 00 | Products |
1 | 01 | |
2 | 02 | In-house: Encoded weight |
3 | 03 | UPN codes (medicine/pharmaceutical) |
4 | 04 | In-house use (loyalty cards/store coupons) |
5 | 05 | Manufacturer coupons |
6 | 06 | Products |
7 | 07 | |
8 | 08 | |
9 | 09 | Manufacturer coupons |
- Motivation
From MusicBrains:
- Barcodes are numbers used as stock control mechanisms by retailers: as such they are highly standardised and well recognised, and form an invaluable identifier for communication between companies.
So I want to add UPCs to video games as this is the only unique identifier that exists (like an ISBN). This property would make it easy for other systems to integrate Wikidata. Or the reverse such as searching Amazon by UPC.
A cool thing we can do is auto create the barcode itself with Lua and image segments. The only question is should it be complicated by including the European superset, EAN?
Dispenser (talk) 02:48, 17 March 2016 (UTC) Updated 01:46, 27 April 2016 (UTC)
- Discussion
- Weak oppose I believe Wikipedia/Wikidata simply isn't granular enough for this to make sense. Usually there are different barcodes for different versions, packaging sizes, multi-packs, regions, etc of a product. Even simply a change in packaging design may result in a new barcode. So that may result in an item having tens or hundreds of bar codes attached. For example, the Cheerios (Q2425291) item won't just have one value, it should have at least 71 according to upcitemdb.com. Intgr (talk) 08:54, 17 March 2016 (UTC)
- For video games, UPCs are like a book's ISBN. As an example, The Orange Box (Q374556) is more findable by its UPC 0-14633-09852-5 (4,000 Google results) than by its ISBN (which is unusual to have) 0-7845-4306-2 (5 Google results). Dispenser (talk) 04:20, 25 March 2016 (UTC)
- See Wikidata:Property_proposal/Archive/15#Barcode for a similar proposal from several years ago. - Nikki (talk) 09:39, 17 March 2016 (UTC)
- Updated with more rational. Dispenser (talk) 01:46, 27 April 2016 (UTC)
- Oppose Unfortunately it is not that easy. For example, the UPC/EAN for the Orange Box is not just "5030931058936". That is just the EAN for one particular edition. The German, French, and other language edition have a different code. The UPC for Cheerios is just for a specific package size. The 685 gram package listed here has a different number. UPC/EAN in general is much for volatile than, for example ISBN numbers. --Srittau (talk) 23:50, 5 May 2016 (UTC)
- Comment maybe we could attempt to determine a range of products where this could be helpful.
--- Jura 15:21, 19 May 2016 (UTC) - Support I am agree with @Intgr about this require more wikidata granularity but this would give a new powerfull functionality to wikidata as is explained here https://meta.wikimedia.org/wiki/WikiObject. Probably it's early to start using wikidata in this way since nowdays there are not tools developed speciffically aimed at listing and searching objects (https://query.wikidata.org/ would be the closest thing) but this could be reached little by little.Qupro (talk) 06:22, 12 May 2017 (UTC)
@Dispenser: Not done, no consensus. --Srittau (talk) 23:22, 11 June 2016 (UTC)