Skip to main content Skip to complementary content

Meta Integration Business Glossary (CSV) - Export

Availability-note AWS

Bridge Specifications

Vendor Meta Integration Technology, Inc.
Tool Name Meta Integration Metadata Management (MIMM)
Tool Version 11.x
Tool Web Site http://metaintegration.com/Products/MIMB/
Supported Methodology [Metadata Management] Multi-Model, Data Store (Logical Data Model) via CSV File

SPECIFICATIONS
Tool: Meta Integration Technology, Inc. / Meta Integration Metadata Management (MIMM) version 11.x via CSV File
See http://metaintegration.com/Products/MIMB/
Metadata: [Metadata Management] Multi-Model, Data Store (Logical Data Model)
Component: MetaIntegrationGlossary version 11.2.0

OVERVIEW
This bridge generates a business glossary representation in comma separated value (CSV) format of the input model.

The business glossary model is composed of Terms organized in Category folders.
The generated file also contains information about the object(s) in the source model, for which a glossary term was created.
The generated file can be edited in a text editor, or in a spreadsheet application before being loaded into a business glossary management tool.

REQUIREMENTS
n/a

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

SUPPORT
Provide a troubleshooting package with:
- the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with -backup option, although this common option is not implemented on all bridges for technical reasons).


Bridge Parameters

Parameter Name Description Type Values Default Scope
File Specify the output file where to save the generated glossary. FILE
*.csv
*.xml
  Mandatory
Skip physical relational objects Specify whether to ignore physical relational objects (Tables, Columns) when generating Terms.

'True'
Physical relational objects are ignored.

'False'
Physical relational objects are considered when generating Terms.
BOOLEAN
False
True
True  
Skip physical relational objects with no description Specify whether to ignore physical relational objects (Tables, Columns) with no description when generating Terms.

'True'
Physical relational objects with no description are ignored.

'False'
Physical relational objects with no description are considered when generating Terms.
BOOLEAN
False
True
True  
Skip hidden objects Specify whether to ignore hidden objects when generating Terms.

'True'
Hidden objects are ignored.

'False'
Hidden objects are considered when generating Terms.
BOOLEAN
False
True
False  
Case sensitive Specify whether to use case sensitive comparison when generating Terms.
If several objects in different models have the same name and path, it makes sense to generate a single Term for them.
The unification of such shared Terms is based on name and path comparison, in case sensitive or insensitive fashion.
The case sensitive criteria is also applied when comparing object(s) descriptions, to compute the term description.

'True'
Compare in case sensitive fashion.

'False'
Compare in case insensitive fashion.
BOOLEAN
False
True
True  
Merge identically named terms Specify whether to merge identically named terms across models.

'True'
Identically named terms across models are merged into a single glossary term.

'False'
Identically named terms across models are not merged, multiple terms are generated in the glossary.
BOOLEAN
False
True
True  

 

Bridge Mapping

Mapping information is not available

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!