Wikidata:Property proposal/Global Trade Information Number (GTIN)

Global Trade Item Number edit

Originally proposed at Wikidata:Property proposal/Economics

Done: Global Trade Item Number (P3962) (Talk and documentation)

Description	GTIN is used to identify products via their barcodes
Represents	Global Trade Item Number (Q521568)
Data type	External identifier
Domain	tangible good (Q1485500) = Trade items
Allowed values	\d{14}
Example	Apple iPhone 7 128GB Jet Black (Q29972750) → 00640520098905
Source	http://www.gs1.org/docs/barcodes/GS1_General_Specifications.pdf
Planned use	To add GTIN numbers to Items, like common objects.
See also	https://www.wikidata.org/wiki/Wikidata:Property_proposal/Universal_Product_Code en:Global Trade Item Number

Motivation

As a part of wikiobject project meta:WikiObject – The preceding unsigned comment was added by Qupro (talk • contribs) at 14:30, 19 November 2016‎ (UTC).[reply]

Note - I have edited some of the property proposal fields to be more concise and complete, and moved some of the text here: ArthurPSmith (talk) 19:56, 15 May 2017 (UTC)[reply]

From old description: Global Trade Item Number (GTIN) is an identifier for trade items, developed by GS1. Such identifiers are used to look up product information in a database (often by entering the number through a barcode scanner pointed at an actual product) which may belong to a retailer, manufacturer, collector, researcher, or other entity. The uniqueness and universality of the identifier is useful in establishing which product in one database corresponds to which product in another database, especially across organizational boundaries.

From old entry for allowed values:

GTINs may be 8, 12, 13 or 14 digits long but when any of these GTINs is encoded in a data carrier that must encode a fixed-length data string of 14-digits (in this case Wikidata), the GTINs less than 14-digits in length must be prefixed by leading zeroes that simply actas filler digits. The presence or lack of these leading zeroes does not change the GTIN concerned. GTINs may be stored with or without leading zeroes in the same database field, depending on the requirements of the particular application.

Discussion

Oppose. Appears to conflate two properties ("url of file" vs. "may be 8, 12, 13 or 14 digits long"). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:17, 21 November 2016 (UTC)[reply]
Comment We already had two similar proposals, Wikidata:Property proposal/Universal Product Code and Wikidata:Property proposal/Archive/15#Barcode, which were both rejected. -

I see, I have added my point of view at UPC proposal disscussion.Qupro (talk) 13:18, 25 December 2016 (UTC)[reply]

Nikki (talk) 17:53, 3 December 2016 (UTC) @Qupro: Can you respond? ChristianKl (talk) 11:08, 24 December 2016 (UTC)[reply]

@Nikki: Sorry, I am not use to wikidata template editor. It's update.Qupro (talk) 13:18, 25 December 2016 (UTC)[reply]

@Qupro: If you want to have this property approved, then I recommend you to get familiar with our data model and what it means for a value to be stored as a number. Afterwards you can change the property proposal to be internally consistent. ChristianKl (talk) 09:38, 28 February 2017 (UTC)[reply]
- @ChristianKI , I was taking a look to https://www.mediawiki.org/wiki/Wikibase/DataModel. When you say "what it means for a value to be stored as a number" , do you mean that number datatype doesn't fit for GTIN values? Maybe this values have to be defined with internal structure like in geographic coordinates case ( latitude, longitude, and possibly a height). Schema.org defines several GTIN properties , like GTIN13 , GTIN14 , ... , maybe It should be the same in Wikidata.
  - In your example the Ballpoint Pen might have been the ID "070330101272". That's a string and not a number. If you would convert it to a number it wouldn't have a leading 0. If you describe a number you can say that it has to be between X and Y or either between X and Y or between Q and W. If you speak about the individual digits you are generally talking about a string representation. ChristianKl (talk) 09:56, 29 March 2017 (UTC)[reply]
    - Thanks, good point, I have changed data type from number to string. I have to go depper at GTIN definition because maybe It should be disaggregated by GTIN types too (one property for GTIN-13 , other for GTIN-12 and so on). I will update with my guess.
      - A GTIN-14 is a GTIN-8 whit 6 leading zeros. A GTIN-14 is a UPC-12 whit 4 leading zeros. A GTIN-14 is a EAN-13 / GTIN-13 / GLN whit 1 leading zero. etc. Schlag.tel (talk) 16:22, 26 April 2017 (UTC)[reply]

Support A GTIN is 14 digits long. There's nothing more to say about that. Schlag.tel (talk) 16:22, 26 April 2017 (UTC)[reply]

@Schlag.tel: can you update the example in the proposal so that it is in fact a 14-digit code? Right now the value provided is a URL which isn't helpful for this. Also if there's a formatter URL that resolves these id's that would be nice to know. ArthurPSmith (talk) 19:22, 27 April 2017 (UTC)[reply]

@ArthurPSmith I have updated source and allowed values following GS1 specification. Although GTIN can be several digits long, it can be always encoded safely as 14 digits long , see page 28 from GS1 specifications document (source in template)

@Qupro: So what is the GTIN for "Bic Cristal Ballpoint Pen Black" - i.e .what value should wikidata hold for this item? The example right now shows a URL, which is wrong. ArthurPSmith (talk) 17:37, 12 May 2017 (UTC)[reply]

@ArthurPSmith I have updated the example, a 12 pack Bic ballpoint pens with its GTIN. Product packs have specific GTINs, maybe too early to start listing packs but It's ilustrative about the possibilities of this.

@Qupro, ChristianKl, Schlag.tel, Nikki, Pigsonthewing: I have updated this proposal to be closer to our usual property proposals, with links for domain and subject item. I

Support it as it is now. Does this seem ready to create now, or any further issues? ArthurPSmith (talk) 19:56, 15 May 2017 (UTC)[reply]

I changed the name to Global Trade Item Number. @ArthurPSmith: There's an open question of whether external-id or string is the better datatype. I err in the direction of external-id. ChristianKl (talk) 21:21, 15 May 2017 (UTC)[reply]

good point - I've changed it to external-id. Also modified the description to reflect the label change. @Qupro: are you happy with this as it looks right now? ArthurPSmith (talk) 13:36, 16 May 2017 (UTC)[reply]

@ArthurPSmith very happy, It is my first property proposal I have learned several things now that I have seen real example format in " Data Type", "Domain" and "Allowed Values". Everything looks ok for me.

I remain opposed - the item in the example is not notable, and we generally don't have items for specific packages of products or the like. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:10, 16 May 2017 (UTC)[reply]

@Andy Mabbett I have changed the example from BIC ballpoint pen pack to an Iphone 7 since it's more relevant (there are wikipedia articles for each Iphone generation). Also there is a list of IOS devices https://en.wikipedia.org/wiki/List_of_iOS_devices#iPhone that maybe could be autogenerated from wikidata items as another proof of concept of "wikiobjects".

@ArthurPSmith, Qupro, Schlag.tel, Nikki, Pigsonthewing: Done There's are more support votes than against votes and the proposer changed the example to one that's more clearly notable and which thus addresses the objection. If there's a project to add a lot of new items automatically, that likely will need a bot that's approved separately (our usual rules for bots). ChristianKl (talk) 18:22, 19 May 2017 (UTC)[reply]