Families and Relationship Tables

[Former Member]

Hi,

What is the purpose of families and relationship table and How to work with those table?

can anyone help me?

Thanks

Narendra

[Former Member]

Hi,

Families table is used for publishing the catalog.

Families table otself works on taxonomy table.

For eg:you hav a taxonomy for suppliers with various attributes

supplier

|_Tools

|_Hand Tools

|_Machine Tools

|_Services

|_Repair

Now you want to furthur categorize this hierarchy based on say Manufacturer or Catalog Name.This can be done using Families table.In console create a families table as type families using Category as family field.Add a field say Image (look up Image).

After importing the taxonomy table category.

Goto Data manager select Family mode.Select a node .Under partion tab select one of the look up values or Attributes based on which u want to categorize further.Then go to Family detail here u can link a image or PDF to this family.

Relationship Table.

It is used to establish relation between records

2 types :Parent /Child(main table and look up) and Sibling(Only look up).In Console u can see the relationship,u can u add one

IN data manager say there are 2 records Steel Hammer Ch Handle And other just Steel Hammer.

Select Steel Hammer Double Click on Relationship it opens a pop up showing all relation say substitute item,related item etc

Select Substitute Item.Then go to other record select it and just drag and drop it to the substitute item pop up.Close the box.

Next time u can see the two related items.

Also u can import relation from a file from Menu Relaionship-Import from file and also u can export it

Regards

Nisha

[Former Member]

Hi,

When i try to create Family table in console,it is diaplaying pop-up box saying that The operation could

not be completed because repositories with families are not supported at this time.See the upgrade

guide for more information.

I am using MDM 5.5 SP6 .Is there any version problem here?

Thanks

Narendra

[Former Member]

Hi Narendra,

Family table has not supported in MDM 5.5 SP6 Patch 0. But it is available in MDM 5.5 SP6 patch 1.

Regards,

Jitesh Talreja

[Former Member]

Hi Narendra,

Kindly update the Thread if your query has been solved.

Regards,

Jitesh Talreja

[Former Member]

Hi Narendra,

Family Mode:

Family mode prepares Master data for publishing both the Web and to Paper. It is the first step in preparing master data for paper publication.

There is a single Hierarchy table named Families. It is used to further partition main table records in each category into smaller groups based upon the values of other fields and/or attributes. You can associate family data ( a paragraph , an image , bullets) once with a family of products rather than with each individual product and also define the table layout of field and/or attribute data (field order , stack, vertical and horizontal pivots and other display options). This table is only available in Family mode.

A Product Family is a group of main table product records that are related by one or more common fields and/or attributes having the same value, and that may also have additional fields of family data, such as an image, a logo, a paragraph of descriptive text and bullets of specifications and so on.

Relationships :

The Relationships table is a special table with a predefined set of fields,and records that that appear in the top-right relationships pane of the MDM Console. Each record that you add in the MDM Console defines a particular product-level relationship, chosen from among several different basic structural relationship types. Once we have defined relationship table in Console add the products in data manager.

Two types of relationship :Parent/child and siblings.

A sibling relationship relates a group of main table product records that are equivalent and/or interchangeable from some

merchandising or structural standpoint.

A parent/child relationship relates a group of records that are not equivalent, where one of them is the parent, and the rest of them are the children.

Examples of sibling relationships include u201Ccross-sellsu201D and u201Cinterchange products.u201D Examples of parent/child relationships include u201Cassemblies and componentsu201D and u201Ckits and parts.u201D

Use of Relationships :

Actually Add to Group , Remove from Group and Split from Group are the options which you can only use if you have maintained a relationship (parent - child or sibling)

Add to Group : When a Parent Child relationship is made then all the records that are coming under the same parent child relationship are maintained in the same group. In case we want to add a new record under the same relationship this option can be used.

Remove from Group : If we want to delete one particular record that is coming under the group that has been maintained under relationship, this option can be used.

Split from Group : In case we want to break a relationship that is existing we can use this option that is we are splitting the relationship between a sibling relationship. In this case two siblings would be maintained.

Hope this would be helpful!!!!!!!!!!

Regards,

Parul

[Former Member]

Hi Narendra,

Families

Families can be used to group together records, which have the same value or the same attribute in certain fields. The families table contains one record for each family. So attributes valid for all family members can be assigned directly to the family and need not be maintained individually for each family member.

This means that instead of having to store group-specific information for every single record, the main table can be more manageable. This group-specific information (for example, for product categories) is stored in the families table and therefore applies to every family member.

The families table must also contain the lookup field in the main

table, which is used to define family membership. This stored lookup field must be of type taxonomy or hierarchy. This allows the family records to be generated automatically.

Relationships

Relationships between master records can be represented using the Relationships relationships table. These relationships show the relations between master records and how the objects they represent are related to one another. T

These relationships can be of type parent/child or sibling.

Relationships can also exist between records in multiple tables, as long as they are of the types main, flat, hierarchy, or taxonomy.

Relationships between multiple tables can be only single-level. Relationships within the same table, on the other hand, can be multilevel, that is, we can branch from child to grandchild to great-grandchild and so on.

Sibling relationships, on the other hand, are best suited for relationships between records of the same level (in the main table), for example, as ideas for the potential of cross-selling, or as a product alternative with similar performance characteristics.

Hope it will help you.

Regards

Richa

[Former Member]

hi,

there are two type of relation ships will be there they are sibling and parent child realtionship.

sibling is like alternative for example if we are having three prodct records then they are similar then make them as sibling relation ship.

Parent/child. A parent/child relationship relates a group of records that are not equivalent, where one of them is the parent, and the restof them are the children.

ex:

in a computer

the monitor ,cpu,motherboard ,etc re child components.

whre as lcd monitor ,colout monitor are like sibling relation .

[Former Member]

Hi Narendra,

Families table is used in Print Publishing i.e. with MDM Publisher. Only one family table is possible in the repository and only for one taxonomy table.

Relationship table helps to maintain the relationship among the records.

e.g. Computer is a product and its record is created. Also there exists information for processor, hardisk etc. Now there is a relationship between Computer and other parts.

So we maintain a Parent/Child relationship between Computer and Processor, Hardisk etc.

Hope you got the basic info.

Regards,

Jitesh Talreja