Different types of tables and modes

Question

Hi Experts
What is the specification of different tables in console and different modes in data manager.
What is the major difference between them.
Can we create a table of one type in console and can use the same table in another mode in data manager, say if I create a taxanomy table and can I use it as the hierarchy mode in the data manager.
have fun..
Hari

Answer 1

Hi Hari,
Differnt types of tables in Console are :
Actually the Tables in Console are further categorized as :
Main Table and Sub table which include:
Flat Tables : It is a simple table consisting of record and fields ( rows and column) . In MDM Main table is always a flat table.
Hierarchy Table : A hierarchy table organizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records.
Taxonomy Table : A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various organizing, searching, editing and publishing purposes.
Qualified Table : A qualified table in MDM stores a set of lookup records,and also supports qualifiers, u201Csubfieldsu201D that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.
Tables are also Categorized as Object Tables like :
Images : For storing Images
Sounds : For Sound File.
Videos : For storing Video Files .
Binary Objects : To store Binary Objects.
Text Blocks : To store block of text.
Copy Blocks : Stores block of text interpreted as a Copy.
Text HTML`s : Stores block of text interpreted as a HTML.
PDFs : To store PDF files.
There are various types of Special Tables also:
Image Variants : Used to define the structure
and format of each of the variants for each image. Each variant is a modified version derived from an original image; the original image is never modified.
Masks : In this defined subset of records are included in Mask i.e. in any scenario whether new records are added or deleted in the repository the records in the Mask remains the same unless edited by the user.
Families : Used to further partition main table records in each category into smaller groups based upon the values of other fields and/or attributes.
Relationships : Used to define each of the different record-level relationships. Each relationship can be either bidirectional (sibling) or unidirectional (parent-child).
Workflows : Stores the workflows of an MDM repository, where each workflow is stored as a record in the table.
Name Searches : Unlike Masks in case of Name search there are again a defined set of records but those records are selected on the basis of Search Selection. In this case if a record is added then the record is checked whether it fulfills the particular search criteria if it does than it is added to the Name serach else not.
Data Groups : Stores the hierarchy of data groups used to break the entire set of objects in the MDM repository into manageable subgroups.
There are various types of System Tables :
Roles :  A single table named Roles. One of three tables used to implement MDM repository security and access control. Each role can selectively grant or deny access to any MDM function and to any table or field. This table is managed in the MDM Console and is not visible in the MDM Client.
Users : A single table named Users. One of three tables used to implement MDM repository security and access control. Each user can have one or more roles. This table is managed in the MDM Console and is not visible in the MDM Client.
Connections : A single table named Connections. One of three tables used to implement MDM repository security and access control. Contains an entry for each currently connected MDM client application, which can be terminated by the MDM Console user. This table is not visible in the MDM Client.
Change Tracking : A single table named Change Tracking. Allows you to specify the fields for which adds, modifies, and deletes should be tracked and stored in the Change Tracking table.
Remote Systems : A single table named Remote Systems. Used to define the different remote systems for import and export. Each specifies whether it supports inbound, outbound, or both. This table is managed in the MDM Console and is not visible in the MDM Client.
Ports : A single table named Ports. Used to encapsulate the logistical and configuration info for inbound and outbound processing of MDM data, for consolidation and distribution respectively. This table is managed in the MDM Console and is not visible in the MDM Client.
Links : A single table named Links. Used to specify the URLs that can be used as the target of an embedded browser in the Web tab in the MDM Client. This table is managed in the MDM Console and is not visible in the MDM Client.
XML Schema : A single table named XML Schemas. Used to identify the XML schemas for import and syndication. Each XML schema is the name of an .xsd file. This table is managed in the MDM Console and is not visible in the MDM Client.
Reports : A single table named Reports. Contains an entry for each report file generated by the various MDM repository operations, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
Logs : A single table named Logs. Contains an entry for the log files generated by the MDM Server, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
Data Manager:
Data Manager in simple terms can be stated as a place where we manage the data that is taken from various systems.
All the data that you take from all the various systems that a business is using is then taken into data manager, so that it could be cleansed and can be maintained easily in future.
There are basically four different modes in Data Manager:
1. Record Mode:  This mode allows us to search, view and edit the records of any table in MDM repository. This is the mode that one uses most often, primarily to view and edit records in the main table and also to view and edit records in any of the sub tables.
2. Hierarchy mode. This mode allow us to view and edit the hierarchy tables in the MDM repository, including regular hierarchy tables, taxonomy tables, and the Masks table. Though we can also view and edit the records of a hierarchy table in Record mode, Hierarchy mode specifically allows us to edit the parent/child relationships and the sibling ordering of the hierarchy.
3. Taxonomy mode. This mode allows us to view and edit the taxonomy tables in the MDM repository. We usually use this mode to create and maintain the category hierarchy used in the repository, and to manage the attributes associated with each category and subcategory. Though we can also view and edit taxonomy tables in both Record mode (for searching) and Hierarchy mode (for editing the other fields of information associated with each category), Taxonomy mode is unique in that instead of focusing on the records of the taxonomy table, it allows you to create and manage the pool of attributes associated with the taxonomy table, and to assign attributes to categories on a category-by-category basis.
4. Matching mode.  This mode allows us to identify and eliminate duplicate records within an MDM repository. When you view the main table in Matching mode, MDM allows you to perform u201Cmatching-and-mergingu201D on and against any or all of its records, using various user-defined criteria (like creation of Rules and Strategies) to decide whether or not records are potential duplicates.
5. Family mode. This mode allows us to view and edit the Families table, which layers a hierarchy of families upon the taxonomy hierarchy to further break down each category into smaller groups of main table records. We usually use this mode to partition the categories of the taxonomy hierarchy by the values of other fields and/or attributes, and then to associate family data (such as an image, a paragraph, and bullets) once with each family of main table records rather than each individual record.
Can we create a table of one type in console and can use the same table in another mode in data manager, say if I create a taxanomy table and can I use it as the hierarchy mode in the data manager.
The structure of the tables are defined in Console and those tables are then used in Data Manager, but if you have defined a table as a Hierarchy table you cannot use that table in Taxonomy Mode but you will be able to see all the tables in Record Mode.
Hope this would be useful...
If useful do reward points!!!!
Regards,
Parul