Many tasks use customizable reference data. This customized data is imported into the databases. The catalog, model, and catalog schema databases work together to apply the custom reference data.
The rules rely on the following databases:
This database organizes and controls the location of all reference data.
This database defines the relationships between objects and rules.
This database contains the objects and connections that run the rules.
The catalog database points to two-dimensional symbol geometry files. These symbols accept inputs and then define the shape of the feature in the model.
This database also points to the Visual Basic and C# rule files. These rules select valid features for a connection.
The catalog is built by loading Excel workbooks. You load these workbooks by using the Bulkload utility. By default, this utility is delivered to the [Product Folder]\CatalogData\Bulkload\Bin\Bulkload.exe file.
You can use this utility to do the following:
Create new catalogs
Append new classes to existing catalogs
Add, modify, or delete items from catalogs
Delete and replace records in catalogs
Catalog Schema Database
The catalog schema database defines relationships between objects and rules. You can define customized properties to control the rules. For example, you can define a StressLevel property in the schema for a collar object and specify that the user can set it to Low, Medium, or High.
The catalog schema database is built by loading Excel workbooks, using the same technique as the catalog database.
You can view the catalog schema data through the MetaDataBrowser. By default, this utility is delivered to the [Product Folder]\Core\Tools\Developer\Bin\MetaDataBrowser.exe file. Click Data/Open Database, and then click the catalog schema. When the catalog schema is open, you can expand UserDefinedPackage and scroll down to view the custom data. Custom data is marked with a yellow dot. In the example used before, you could view (but not modify) the StressLevel properties and their user-defined values. These properties can then be used by the rules.
The model database contains the objects and logical connections that define how the software applies the reference data. This database provides the interface for the user to make interactive reference data decisions.
Connections are objects in the model database. They define penetration and bounding relationships between objects.
You can control reference data through questions which are exposed in the model database.