r3 User Guide

Create the products and intls. Product, intl, and pages are examples of r3 dimensions. Products and intls are created in much the same way. From the command line:

$ r3 dimension product create generic_product
product generic_product created

The above command creates a product called generic_product. While not required, generic dimension elements provide a common location for templates, target specifications, and translations. However, if you do not create generic dimension elements, inheritance defaults to whichever domain being searched is located at the top of the structure..

After creating generic_product, create the real products as descendants:

$ r3 dimension product create cookery -p generic_product
product cookery created with parent generic_product for page, template and translation domains.

The -p flag stands for parent.

Created the rest of the products and intls in the same way:

$ r3 dimension product create wine -p cookery
product wine created with parent cookery for page, template and translation domains.
$ r3 dimension product create cars -p generic_product
product cars created with parent generic_product for page, template and translation domains.
$ r3 dimension intl create generic_intl
intl generic_intl created
$ r3 dimension intl create us -p generic_intl
...
$ r3 dimension intl create ca -p us
$ r3 dimension intl create fr -p generic_intl
$ r3 dimension intl create jp -p generic_intl

This is the hierarchy for product:

This is the hierarchy for intl:

Change French-speaking Canada to inherit its translations from fr.

r3 recognizes three domains in which inheritance operates. These domains correspond to the things that r3 searches for:

r3 maintains separate inheritance trees for each dimension in each domain (except for the page dimension which, again, has only one set of inheritance data). When you create a product or intl and specify its parent, the same parent relationship is set up for all domains. This is normally what you want. However, in the special case of ca inheriting its translations from fr, you must change the inheritance relationship between ca and fr only for the translation domain. To do this:

$ r3 dimension intl parent ca set fr -d translation
parent of intl ca changed to fr in the translation domain

Change the parent of fr in the translation domain so that it doesn't inherit from generic_intl .

$ r3 dimension intl parent fr unset -f -d translation
intl fr set with no parent in the translation domain
$ r3 dimension intl parent us unset -d translation
intl us set with no parent in the translation domain
$ r3 dimension intl parent jp unset -d translation
intl jp set with no parent in the translation domain

The -f flag is the "force" flag to change the parent of fr, because ca is a child of fr, and by default r3 refuses to move nodes with children.

The intls in the template and page domains retain the previous hierarchy, but for the translation domain has following hierarchy:

	Note
	Note that generic_intl still exists in the translation domain. The existence of intls, products and pages is independent of domains, it is only the inheritance relationships between them that may differ between domains.

To view the inheritance structure for a given dimension within a given domain:

$ r3 dimension intl list -t translation
jp
us
fr
    ca
generic_intl

The -t flag says produce a "tree" view, and therefore needs an argument domain to get the inheritance data.