Does BODI support OMG / CWM (Common Warehouse Metamodel) metadata model? Could anyone help me?
ssrinimani (BOB member since 2009-05-09)
Yes, in the Designer -> Tools -> export metadata
Werner Daehn 
(BOB member since 2004-12-17)
Doesn’t that just export the list of tables referenced by the datasource in a CWM-suitable format? My point is that table definitions are just one small part of the CWM. The ability to export metadata capturing (e.g.) transformations within DI is not present.
Am I missing something?
finbo 
(BOB member since 2006-12-15)
You cannot exchange entire repository metadata information. DI supports only datastores information to exchange. So that we can import this metadata in Business Objects to build universes.
gssharma 
(BOB member since 2006-10-30)
That was my point. I’ve been looking at the Common Warehouse Metamodel standard of late and most vendors claim to adhere to it. In reality though the ability to integrate with this is limited and in this case restricted to a small part of the metadata (i.e. just via the datasources; ETL transforms and the like have no way of being exchanged in any sort of CWM-compliant format).
finbo (BOB member since 2006-12-15)
The CWM standard is precise when it comes to table metadata but very vage for expressing transformations. I’d like to join two tables, apply a substring() function and do a target based CDC. How do you express that in CWM? You can but it is more like a free text description than anything else. That’s the root of the problem. If that transformations would be standardized as well, supporting it would make sense, but so…
Werner Daehn (BOB member since 2004-12-17)
Fair point. That’s exactly what I’ve come up against… expressing well-defined structures such as table metadata in the CWM is fine but I’m having issues finding anything tangible (as opposed to pages of theoretical musings) relating to the storage of metadata relating to more abstract concepts such as transforms. Meta-meta-meta-data… 
finbo (BOB member since 2006-12-15)