5.12.17.  Automatic Class Mapping: Edit...

As of V12 there is a new function Automatic Class Mapping: Edit....

Dialog: Edit Automatic Class Mapping

Dialog: Edit Automatic Class Mapping

An important difference in compare to function Map class systems is, that it's a virtual mapping here, so that the mapped classes and attributes are transferred into the target systems during export, but classification data is not written into the project files physically.

[Note]Note
  • Precondition: Under $CADENAS_DATA/datasetup, the directory class2class has to exist.

  • An important restriction is, that attributes cannot be mapped to already existing classes (not even when the concrete attribute is not set). If for example, the mapping is used to map from eClass 11.1 to a new, completely empty eClass 12.0, this point is irrelevant. However, if for example a mapping shall be executed from the Revit classification to the CNS classification, the mapping won't presumably be executed in many cases.

  • If a project contains mappings from the tabbed page Suggested items, classes and attributes will be displayed in reddish color , if containing mappings from the tabbed page Mapped elements, classes and attributes will be displayed in bluish color .

    Mapping from "Suggested items"

    Mapping from "Suggested items"

    Mapping from "Mapped elements"

    Mapping from "Mapped elements"

Example

In the following example, a class attribute of the CNS classification shall be mapped to a class attribute of the eClass 9.1 classification. That means, beginning in the upper table (Mapping between classes), class data is entered and then attribute data in the lower table (Mapping between characteristics).

  1. In the upper table, click on Add System.

    -> The same-named dialog box is opened.

  2. With the exact wording in lower case, enter the name of the desired classification and confirm with OK.

    -> A new line is created in the upper table.

  3. Click on Add Item.

    -> A new line with input fields is created.

  4. Fill out the fields:

    [Note]Note

    When clicking into an input field, a list field is shown with all possible options. Otherwise: If wanted activate the respective checkbox.

    • Origin Class:

    • Target System: With exact wording, in lower case, enter the name of the desired classification and confirm with Enter.

    • Target Class: Open the list field and select the desired class.

    • Number: By default, one instance is created. However, you can create multiple instances of the class.

    • Bidirectional: By default, mapping only takes place in the stated direction. When activating this option, there is a mapping from Origin Class to Target Class and the other way round.

    • Copy Instance: The whole content of the class is copied.

    • Copy Restrictions:

    • Copy features: All identical attributes are copied. This option excludes entries in the lower table.

      Or

      Copy mapped features (default): Only those attributes are mapped, which have been stated in the lower table explicitly.

      Only one of the two points can be chosen!

  5. In the lower table, click on Add System.

  6. With exact wording in lower case, enter the name of the desired classification and confirm with OK.

  7. Click on Add Item.

    -> A new line with input fields is created.

  8. Fill out the single fields:

    • Origin Class: Open the list field and select the same class as in upper table. Alternatively, you can use the wildcard symbol (*), (which affects the performance negatively.)

    • Origin Characteristic: Open the list field and select the desired attribute.

    • Origin ID: Is automatically filled.

    • Target System: With exact wording in lower case, enter the name of the desired classification and confirm with Enter.

    • Target Class: Open the list field and select the desired class.

    • Target Feature: Open the list field and select the desired attribute.

    • Target ID: Is automatically filled.

    • Copy Characteristic Name ("Copy Variable Name"): Select this option, if a certain variable shall be mapped.

      Or

      Copy Characteristic Value: Select this option, if a fixed value shall be mapped.

    • Value Mapping (optionally): Click on the button , if you want to adjust the original value.

      -> The same-named dialog box is opened.

      "Value Mapping" dialog box

      "Value Mapping" dialog box

      With entries under Original Value and Target Value, you can adjust the target value. After confirming with OK, the button looks like this .

    • Copy flags:

    • Copy unit: Default is enabled.

    • Objective Unit (optionally): If a unit is stated, a conversion of the value is automatically performed.

  9. Execute the mapping by clicking OK.

    [Note]Note

    A mapping is only executed if the target is empty.

    Changes to the mappings require restarting PARTproject; for project changes updating (F5) the Project selection is sufficient.

Test:

  1. Select a part with respective Origin Class and Origin Characteristic.

    The part is classified in the CNS classification with the order number by default.

    The part is classified in the CNS classification with the order number by default.

  2. Now the mapped attribute should show the same value accordingly.

    In eClass 9.1, the project shows a mapping from "Mapped elements".

    In eClass 9.1, the project shows a mapping from "Mapped elements".

User interface

Main features are the "table area" at the top (for Class Mapping) and the "table area" at the bottom (for Attribute Mapping).

Each "table area" has 2 tabs, one for Mapped elements and one for Suggested items. These are separate tables with separate data.

Each "table area" has it's own buttons. They work on the current active tab.

Buttons top right of the tables

  • Add System: Adds a source system (e.g. eclass8.0, eclass8.1, etc...). (No duplicates possible).

  • Add Item: Adds a new element under a Top Node with empty data and default values.

    Element is inserted at last position under current selected Top Node or current selected element.

  • Remove: Deletes the current selected Element or Top Node (also works with Del-key on keyboard).

    When deleting a Top Node all elements under the Top Node will be deleted, too. So there is a dialog for asking the user if he really wants to delete it.

Search bar

Each "table area" has it's own search bar which searches for all source and destination data (system and class (and variable and id when searching in Variables)).

Buttons below table area

  • Import eClass XML: Imports eClass Data from a directory with suitable .xml files (legacy case).

  • Import eClass CSV: Imports eClass Data from a directory with suitable .csv files. (Upgrade to next eClass Version).

  • import CSV: Imports Data from a directory with suitable .csv files. (e.g. eclass8.0_classes_mapped.csv).

  • Export CSV: Exports the Data from the tables to a directory in several .csv files (like Import-Format above).

    The exported csv files are separated by classification system, class data / variable data and mapped / suggested (e.g. eclass5.1_classes_mapped.csv or eclass5.1_variables_suggested.csv).

  • OK: Saves the data under $CADENAS_DATA/datasetup -> directory class2class -> file mapping.c2c and closes the dialog.

    Under $CADENAS_DATA/datasetup, the directory class2class has to exist.

  • Cancel: Discards the changes and closes the Dialog (also works with the X button in the top right corner).

When importing data (via .csv files), duplicates are removed (may take some time).

When exporting data (via .csv files), duplicates are removed (only changed Elements will be checked).

When saving data (via OK button) duplicates are removed (only changed elements will be checked) and Variable Mapping Data is checked for missing corresponding Class Mapping Data. If elements are found, a dialog appears where either missing Class Mapping Data can be added or wrong Variable Mapping Data can be deleted.

Normally the table cells are editable strings or checkboxes.

Special cases:

  • Some cells give you a List of possible string values, when clicked (e.g. source class if source system is existing).

  • In the table Mapping between characteristics, in the column Value Mapping, in the respective table cell, a button () opening a special dialog is found. Here, source values (possibly multiple) can be mapped to target values (warning, if it is a duplicate). That means, in the mapped variable the value is changed or the fixed value is changed.

  • Objective Unit: If the field is enabled, the unit will be converted. If there are values, they are automatically converted into the new unit.

Special note

There are classes without attributes. In this case, entries in the lower table are obsolete. The reverse case is not possible. The upper table always has to contain entries.