Changes

Jump to navigation Jump to search
Updated version typology
Line 30: Line 30:  
* We store revisions of the product pages. Those revisions were intended for revisions of the product page itself (e.g. adding more data or fixing data corresponding to one set of product pictures), not for different versions or evolutions of the products.
 
* We store revisions of the product pages. Those revisions were intended for revisions of the product page itself (e.g. adding more data or fixing data corresponding to one set of product pictures), not for different versions or evolutions of the products.
 
** In practice, revisions mix different versions, evolutions and revisions.
 
** In practice, revisions mix different versions, evolutions and revisions.
 +
 +
== Typology ==
 +
Not all versions are equal. In order to have a better understanding of the kind of versions that might occur, one can differentiate several type of versions:
 +
* Views - product versions that are essentially the same, but have different packages. Each package is intended for a different locale (country and/or language). Sometimes, this can be just a sticker that has been added. Lidl-products are a good example of this;
 +
* Marketing - The product (ingredients/nutritional values/etc) did not change. However the packaging evolved. Examples are Coca Cola, Perrier, etc;
 +
* Evolutions - In this case the product has been changed and thus the package as well;
 +
* Instances - the product as bought by a consumer with its own expiry date, purchase place and possibly producer-code;
 +
* Re-usage - In this case only the barcode is the same. The product and package has been changed; Thus is barcode is only repurposed;
    
== Solution ==
 
== Solution ==
Line 59: Line 67:     
== Questions ==
 
== Questions ==
Some Questions related to product versions
+
Some Questions related to product versions.
 
* Purchase place - how does the purchase place fit into this?
 
* Purchase place - how does the purchase place fit into this?
 
* Expiration date - and the expiration date?
 
* Expiration date - and the expiration date?
 
* Production place can be dependent on the expiration date imprint, thus two versions?
 
* Production place can be dependent on the expiration date imprint, thus two versions?
To be continued.
+
There should be a clear definition what a product is. The thing I buy in a shop is a product instance with unique packaging, purchase place, expiration date and packaging. Somebody else can buy another product instance in the same shop, same expiration date and packaging. Only the purchase time is different. Other product instance might be bought in the same shop, but with other expiration dates. Or in other shops, but with the same expiration date. All other aspects of the product instance are the same, defining what a product is. The system should allow the registration if these instances. It can be seen as an issue not related to product versions.
3,390

edits

Navigation menu