Initial release

🎉 New features

• Open Metadata Repository Proxy Connector for IBM Information Governance Catalog, conformant to mandatory metadata sharing profile of CTS from v11.5.0.2 of IGC onwards
• Only implements read (and search) operations, no write, update, delete or purge
• Separate client library for interacting with IBM Information Governance Catalog REST API

🥽 Technical previews

• Data Engine Proxy Connector for IBM DataStage: to integrate design-time data lineage information with Egeria
• Client library for interacting with IBM Information Analyzer REST API

🔨 Dependencies

• Egeria core 1.2

🧩 Open metadata type mappings added / changed in this release

(📦 Entities, 🔗 Relationships, 🏷 Classifications)

🧩	OMRS type	IGC type(s)	Notes
🔗	AssetSchemaType	database_schema - database_schema	generated relationship (all properties for both endpoints are on a single entity instance in IGC)
🔗	AssetSchemaType	data_file - data_file_record
🏷	AssetZoneMembership	database, data_file, database_schema, data_file_folder	The provided implementation simply assigns the list of default zones that have been specified as default.zones in the configuration of the connector anytime these IGC types are retrieved
🔗	AttachedTag	information_asset - label
🔗	AttributeForSchema	data_file_record - data_file_field
🔗	AttributeForSchema	database_table - database_column
🔗	CategoryAnchor	category - category	between the ultimate parent IGC category (Glossary) and any offspring
🔗	CategoryHierarchyLink	category - category
🏷	Confidentiality	term	The provided implementation assigns a Confidentiality classification using the assigned_to_term relationship to any term within the Classifications/Confidentiality parent category. The terms contained within this Confidentiality category in essence represent the ConfidentialityLevel enumeration in OMRS.
📦	Connection	data_connection
🔗	ConnectionConnectorType	data_connection - connector
🔗	ConnectionEndpoint	host - data_connection	via the IGC connector type
🔗	ConnectionToAsset	data_connection - database
🔗	ConnectionToAsset	data_connection - data_file_folder
📦	ConnectorType	connector
📦	ContactDetails	user
📦	ContactDetails	group
🔗	ContactThrough	user - user	generated relationship (all properties for both endpoints are on a single entity instance in IGC)
🔗	ContactThrough	group - group	generated relationship (all properties for both endpoints are on a single entity instance in IGC)
📦	Database	database
📦	DataClass	data_class
🔗	DataClassAssignment	information_asset - data_class	including relationship-level properties from IGC classification type for detected assignments
🔗	DataClassHierarchy	data_class - data_class
🔗	DataContentForDataSet	database - database_schema
📦	DataFile	data_file
📦	DeployedDatabaseSchema	database_schema
📦	Endpoint	host
📦	FileFolder	data_file_folder
🔗	FolderHierarchy	data_file_folder - data_file_folder
🔗	ForeignKey	database_column - database_column
📦	Glossary	category	all top-level categories in IGC that are not named Classifications
📦	GlossaryCategory	category	all categories in IGC whose parent_category is not null and not Classifications
📦	GlossaryTerm	term
📦	GovernancePolicy	information_governance_policy
🔗	GovernancePolicyLink	information_governance_policy - information_governance_policy
📦	InformalTag	label
🔗	NestedFile	data_file_folder - data_file
🔗	NestedSchemaAttribute	database_table - database_column
📦	Person	user
🏷	PrimaryKey	database_column	The provided implementation looks for the presence of either the defined_primary_key or selected_primary_key properties, and if present adds a PrimaryKey classification to that RelationalColumn.
🔗	RelatedTerm	term - term
📦	RelationalColumn	database_column
📦	RelationalDBSchemaType	database_schema
📦	RelationalTable	database_table
🔗	ReplacementTerm	term - term
🔗	SemanticAssignment	information_asset - term
🏷	SpineObject	term	The provided implementation assigns a SpineObject classification when the referencing_categories of the term in IGC includes Classifications/SpineObject.
🏷	SubjectArea	category	The provided implementation assigns a SubjectArea classification when the assigned_to_term relationship of the category in IGC links to the term Classifications/SubjectArea. The name of the SubjectArea will be the name of the category.
🔗	Synonym	term - term
📦	TabularColumn	data_file_field
📦	TabularSchemaType	data_file_record
📦	Team	user
📦	Team	group
🔗	TermAnchor	category - term	between the ultimate parent IGC category (Glossary) and an IGC term
🔗	TermCategorization	category - term
🔗	TermHASARelationship	term - term
🔗	TermISATypeOFRelationship	term - term
🔗	Translation	term - term
🏷	TypeEmbeddedAttribute	database_table, database_column, data_file_field	The provided implementation adds this classification to all RelationTable, RelationalColumn and TabularColumn instances to simplify the management of type information without requiring additional SchemaType subclasses (like RelationalTableType, RelationalColumnType and TabularColumnType) and their additional relationships.

Temporary initial release mechanism

This is an initial release mechanism to ensure that we have continuity for the Helm templates in the Egeria core project. We are investigating alternative long-term mechanisms to handle the binary content of releases.

(Note: the jar asset is being manually kept in-sync with the latest changes to master, so despite any commit differences being suggested to the contrary the jar file contains the latest version of the connector.)