Developer Documentation Library > Data Model > UNICOM Intelligence Data Model reference > Metadata Model to Quantum component
 
Metadata Model to Quantum component
The Metadata Model to Quantum component is designed to make it easier to allocate card, column, and punch definitions programmatically; for example, in a Data Management Script (DMS) file. Card, column, and punch definitions are required in the Metadata Document (.mdd) file when you use Quantum DSC to export response data to a Quantum-format ASCII file.
If you are new to setting up card, column, and punch definitions, read Metadata Model to Quantum. Metadata Model to Quantum is a Windows accessory that comes with the UNICOM Intelligence Data Model for defining card, column, and punch definitions in a Metadata Document (.mdd) file and it uses the Metadata Model to Quantum Component internally. For an overview of custom properties in the MDM in general and card and column custom properties in particular, see MDM custom properties.
The Metadata Model to Quantum Component writes card, column, and punch definitions as custom properties in the DataSourceProperties collections. These custom properties are visible only when the same DataSource object is selected as the current DataSource for the MDM document. For information on viewing DataSourceProperties in Metadata Model Explorer, see Viewing custom properties in MDM Explorer.
Using more than one shared list for a question, and using the same shared lists in other questions, can result in errors. The errors are the result of Metadata Model to Quantum being efficient in terms of file size and time to allocate. Efficiency is achieved by allocating card, column and punch values on the shared list object. The allocations made on the shared list objects can overlap when the shared list is used with other shared lists (in different combinations). When the Allocate shared lists separately for each question option is selected Metadata Model to Quantum allocates card, column, and punch values separately for each question, instead of allocating the shared list. The process is time consuming, but ensures that the allocations are unique. When the option is not selected, Metadata Model to Quantum usually allocates card, column, and punch values on the shared list object, which is more efficient but can result in overlaps.
To use the Metadata Model to Quantum Component with the Metadata Model in Visual C++, import MDM2QuantumLib.dll. To use the Metadata Model to Quantum Component with the Metadata Model in Visual Basic, add SPSS MR MDM2QuantumLib Type Library to the project references.
Samples
The UNICOM Intelligence Developer Documentation Library comes with some sample .mrs files that demonstrate using the Metadata Model to Quantum Component. For more information, see Sample mrScriptBasic files.
Requirements
UNICOM Intelligence Data Model
See also
Metadata Model to Quantum ErrorConstants
Metadata Model to Quantum
Quantum DSC
Working with card and column definitions
Setting up card and column definitions using the Metadata Model to Quantum component
I have used Metadata Model to Quantum to set up custom properties, but I can't see them when I look in MDM Explorer. Where are they and why can't I see them?
What's new in the Metadata Model to Quantum component
Metadata Model to Quantum ErrorConstants
UNICOM Intelligence Data Model reference