Organization of Repository Space in ActiveSpaces

The repository space is organized in ActiveSpaces in different ways.

The repository space is organized in the following ways:

  • The fields of the space are named using the database column name assigned to each attribute. Therefore, the space appears similar to the database table.
  • All the predefined attributes are prefixed with Z_. The predefined attributes are displayed in ActiveSpaces as follows:
    Mapping of the Column, Space Field, and Data Type
    Column Name Space Field (Predefined Attributes) Data Type, if different 
    PrincipalKey. MODVERSION, MCT.CMODVERSION
    		 
    Z_MODVERSION
    		   
    PrincipalKey.CATALOGID
    		 
    Z_CATALOGID
    		   
    PrincipalKey.CATALOGVERSIONNUMBER
    		 
    Z_CATALOG_VERSION
    		   
    PrincipalKey.MODDATE
    		 
    Z_MODDATE
    		 
    LONG
    		 
    PrincipalKey.ACTIVE
    		 
    Z_ACTIVE
    		   
    PrincipalKey.MODMEBERID
    		 
    Z_MODMEBERID
    		   
    PrincipalKey.CREATIONDATE
    		 
    Z_CREATIONDATE
    		 
    LONG
    		 
    PrincipalKey.LASTIMPORTTIME
    		 
    Z_LASTIMPORTTIME
    		   
    PrincipalKey.CHECKSUM
    		 
    Z_CHECKSUM
    		   
    PrincipalKey.LASTCONFRIMEDVERSION
    		 
    Z_LASTCONFRIMEDVERSION
    		   
    PrincipalKey.OWNERID
    		 
    Z_OWNERID
    		   
    PrincipalKey.PRODUCTKEYID
    		 
    Z_PRODUCTKEYID
    		   
    PrincipalKey.STATE
    		 
    Z_STATE
    		  
  • Due to the inherent limitation in ActiveSpaces, some data types cannot be mapped as is. The following table describes the mapping of the TIBCO MDM data types to the ActiveSpaces types:
    Mapping of the MDM Data Types to ActiveSpaces Types
    TIBCO MDM Data Types ActiveSpaces Types
    String String
    Boolean Boolean
    Date Long
    Long (IDs) Long
    Integer Integer
    Decimal, Custom Decimal, Amount, Number Float
    Timestamp Long
    FILE String