PIM training: About data migration

Author: adriendupuis

docs/trainings/commerce/pim/000_syllabus.md

@@ -7,12 +7,13 @@ page_type: training
 
 ## Syllabus
 
-In this training, you learn how to create complex products, to quote their prices, and to organize them in catalogs, using the build-in features.
+In this training, you learn how to create complex products, and to sort them.
 
-| Section                                     | Estimated | Description                                               |
-|:--------------------------------------------|----------:|:----------------------------------------------------------|
-| [Product modeling](011_product_modeling.md) | X minutes | Learn about product types, products and product variants. |
-| [Product shelving](012_product_shelving.md) | Y minutes | Organize your products with categories and catalogs.      |
+| Section                                     | Estimated | Description                                                 |
+|:--------------------------------------------|----------:|:------------------------------------------------------------|
+| [Product modeling](011_product_modeling.md) | X minutes | Learn about product types, products and product variants.   |
+| [Product shelving](012_product_shelving.md) | Y minutes | Organize your products with categories and catalogs.        |
+| [Product migration](021_migration.md)       | Z minutes | Export your product model for deployment on other installs. |
 
 ## Requirements
 
@@ -31,9 +32,7 @@ In this training, you learn how to create complex products, to quote their price
 - [[= product_name_exp =]] [[= latest_tag_4_6 =]]
 - [[= product_name_com =]] [[= latest_tag_4_6 =]]
 
-TODO: Make sure that everything used is in Ibexa DXP Headless scope, so to speak, ibexa/product-catalog
-
-TODO: Trainees working on Ibexa DXP Commerce could pick examples from ibexa/storefront but others mustn't be frustrated of having installed an inferior edition.
+TODO: Make sure that everything used is in Ibexa DXP Headless scope, so to speak, ibexa/product-catalog. It mustn't use features from ibexa/storefront.
 
 ### Cluster elements
 
@@ -47,6 +46,6 @@ This training can be run on the minimal stack.
 
 ### Starting state
 
-To follow this training, you must install code, config and data on top of a fresh installation.
+To follow this training, you must install code, configuration, and data on top of a fresh installation.
 
 TODO: Experience clean install, or previous bike ride design and content?

docs/trainings/commerce/pim/011_product_modeling.md

@@ -9,7 +9,7 @@ page_type: training
 ## Product types
 
 The product type base concept is close to the content type one.
-Like a content type structures a family content items, a product type structures products.
+Like a content type structures a family of content items, a product type structures products.
 
 See a first conceptualisation of what a product is, and what a product type is, in [Documentation > PIM (Product management) > Products](products.md).
 
@@ -40,8 +40,10 @@ SELECT cg.group_id, cg.group_name, g.is_system, c.id, c.identifier, c.version
 The "Product specification" field type (`ibexa_product_specification`) brings in the power of attributes.
 
 Notice that you don't need to add a field or an attribute for price.
-Prices are handled by a particular side mechanism, the price engine, which is treated later in the training with VAT, currencies, etc.
+Prices are handled by a particular side mechanism, the price engine, which is not treated in this training.
 But, also notice that VAT is set at product type level.
+The associations of VAT categories to regions are also stored by the `ibexa_product_specification` field.
+TODO: This is demonstrated in migration.
 
 ## Attributes VS Fields
 
@@ -55,8 +57,6 @@ Only the display of those properties changes with the language. See the followin
 - The color of a product is the same whatever the language is, only the corresponding color name is translated.
 - The radius of a sphere doesn't depend on the language, only its numeral representation need translation according to local length units.
 
-TODO: Later in the training, in the templating part, is shown how to localize the attributes.
-
 Unlike fields, attributes are first defined outside the product types.
 Attributes and attribute groups are to be reused from product type to product type.
 
@@ -237,6 +237,7 @@ But, if you're curious, you can read or implements as a bonus the following cust
 ??? note "TODO: Possible solution(s)"
 
     TODO: Propose grouped attributes and product type(s), illustrate their usage with few products and product variants.
+    TODO: Materials as 1 attribute. Paintjobs as 2 attributes, one per series to reduce selection list length? 3 attributes groups, one common, one per series? Then 2 product types, one per series?
 
 Your new products are in the "Uncategorized products" section of the **Products** admin page.
 It's now time to fix this in the next chapter.

docs/trainings/commerce/pim/021_migration.md

@@ -0,0 +1,41 @@
+---
+description: "PIM training: Migration"
+edition: experience
+page_type: training
+---
+
+# Product model migration
+
+After having modeled your catalog organization on your local developer instance,
+you may want/need to [generate migration files](exporting_data.md) to install the model on a shared instance
+(for example a staging instance or the production instance) where the creation of the products will be done.
+
+Export attribute groups, attributes, and product types:
+
+``` bash
+php bin/console ibexa:migrations:generate \
+  --type=attribute_group --mode=create \
+  --match-property=identifier --value=bike --value=mtb-s4 --value=mtb-s5 \
+  --siteaccess=admin;
+
+# Where 2, 3, and 4 are the IDs of the attribute groups bike, mtb-s4, and mtb-s5
+php bin/console ibexa:migrations:generate \
+  --type=attribute --mode=create \
+  --match-property=attribute_group_id --value=2 --value=3 --value=4 \
+  --siteaccess=admin;
+
+php bin/console ibexa:migrations:generate \
+  --type=content_type --mode=create \
+  --match-property=content_type_identifier --value=mtb-s4 --value=mtb-s5 \
+  --siteaccess=admin;
+```
+
+Export product categories:
+
+``` bash
+# Where 63 is the "Product Root Tag" Location ID (Product catalog > Categories)
+php bin/console ibexa:migrations:generate \
+  --type=content --mode=create \
+  --match-property=parent_location_id --value=63 \
+  --siteaccess=admin;
+```