Wikidata:Property proposal/stock keeping unit
stock keeping unit[edit]
Originally proposed at Wikidata:Property proposal/Authority control
Motivation[edit]
We (including me Photocyte (talk) 20:16, 17 March 2023 (UTC)) are working on a Scientific Labware ontology + database (https://github.com/Bioprotocols/labware-databank/issues/3), and it would be useful to represent the company-specific stock keeping units & keep them in sync with Wikidata. Generally speaking, stock keeping units are used everywhere in global physical and electronic commerce. Would be worth representing in Wikidata.
An alternative approach is to make project proposals for vendor-specific SKUs, but that would be extremely laborious to implement for all companies on Wikidata. (some millions?)
But here are some large vendors, at least in the scientific space, where it might make sense to have independent Property proposals:
Some past discussion happened here: https://www.wikidata.org/wiki/Wikidata_talk:WikiProject_Ontology?markasread=883442226&markasreadwiki=wikidatawiki#c-Lectrician1-20230317181100-Photocyte-20230317180400
I expect there are some "real" ontologies out there with an equivalent stock keeping unit term, so would love feedback on how to rigorously tie this property into those ontologies.
It might be useful to have a format constraint of: [A-Z\d]{200} (could represent sha512 hashes in base36, in the unlikely event any company is using that) Photocyte (talk) 15:42, 25 March 2023 (UTC)
On second thought, a purely alphanumeric format constraint may exclude non-western scripts which do not use arabic numerals. So, perhaps there should be no constraints. Photocyte (talk) 14:41, 27 March 2023 (UTC)
Discussion[edit]
WikiProject Ontology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
Notified participants of WikiProject Companies
WikiProject Properties has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
Comment The datatype should not be external identifier but string - similar to ticker symbol (P249) this is an identifier only with respect to the issuer, not universal. ArthurPSmith (talk) 19:34, 28 March 2023 (UTC)
@ArthurPSmith: , If taking https://www.wikidata.org/wiki/Wikidata:Property_proposal/Amazon.com_ID and https://www.wikidata.org/wiki/Wikidata:Property_proposal/part_number as examples, both those properties use External Identifier, rather than string. So I guess before I change it to string on this particular property proposal, I'd like to clarify if it should also be changed on those other accepted & in progress property proposals? Also pinging the properties group. I'm starting to realize that there are many similar concepts: model code, part number, SKU, and I want to be sure they are kept appropriately harmonized with external ontologies & uses of these terms Photocyte (talk) 18:32, 29 March 2023 (UTC)
- @Photocyte: The Amazon ID uniquely identifies a product, as it is a code specific to Amazon, so there's no problem calling that an external id. The part number proposal was not done, but if it had been it should not have been an external identifier as it does not uniquely identify items (the same part number could be used by different vendors to identify different things). ArthurPSmith (talk) 12:11, 30 March 2023 (UTC)
- @ArthurPSmith :, would you like to give your opinion? Regards, ZI Jony (Talk) 06:57, 24 January 2024 (UTC)
- @Photocyte: The Amazon ID uniquely identifies a product, as it is a code specific to Amazon, so there's no problem calling that an external id. The part number proposal was not done, but if it had been it should not have been an external identifier as it does not uniquely identify items (the same part number could be used by different vendors to identify different things). ArthurPSmith (talk) 12:11, 30 March 2023 (UTC)
Not done, no consensus of proposed property at this time based on the above discussion. Regards, ZI Jony (Talk) 05:37, 4 February 2024 (UTC)
