Wikidata:Property proposal/Woolworths product ID

Woolworths product ID edit

Originally proposed at Wikidata:Property proposal/Generic

Descriptionunique identifier of a product sold via the Woolworths online shop
RepresentsWoolworths product identifier (Q109361809)
Data typeExternal identifier
Domainproduct (Q2424752)
Allowed values\d{6}
Example 1iceberg lettuce (Q1310886)154340
Example 2bell pepper (Q1548030)135306
Example 3bell pepper (Q1548030)135156
Example 4Cavendish banana (Q1051869)133211
Example 5Cavendish banana (Q1051869)157649
Example 6Lady Finger banana (Q1616531)133390
Formatter URLhttps://www.woolworths.com.au/shop/productdetails/$1/
See alsoAmazon Standard Identification Number (P5749)
Applicable "stated in"-valueWoolworths (Q109361685)
Distinct-values constraintyes
Wikidata projectWikiProject Australia (Q11036831)

Motivation edit

Provides information about mostly food products from one of the largest supermarket chains in Australia. This includes nutritional, price and occasionally usage and "market conditions" information. --Dhx1 (talk) 14:19, 2 November 2021 (UTC)[reply]

Discussion edit

  • @Thierry Caro: This is a good point and I do agree that it would be better to have separate items for Cavendish banana (Q1051869) (the entire plant) and the fruit of this cultivar of banana plant. It is even trickier for grafted fruit trees where you can mix and match rootstocks with scions producing different types of fruit. Then there are also different items for cauliflower (Q23900272) vs. "caulilini" [1] (and also just cauliflower (Q23900272) at a different maturity). We have this exact problem today with PLU code (P4030) where there is a different produce code for small apples of a particular cultivar and medium apples of the same cultivar. They're botanically the same thing but are different saleable products currently modeled in Wikidata as a single item with multiple PLU codes. Ideally this property proposal and PLU code (P4030) would also have a single best value and distinct value constraint in the future but that is a lot of work possibly not achievable with the editing resources of Wikidata today, so properties are being used flexibly with a 1:many mapping instead. --Dhx1 (talk) 00:58, 4 November 2021 (UTC)[reply]