Catalog

The Catalog Audit Trails showcase actions related to Terms, Tags, Data Objects, Codes, Custom Fields, Custom Object Definitions, and Descriptions.

Terms

In OvalEdge, when a term is associated or disassociated from a data object such as Schema, Table, Table Column, File, etc., the system records and displays the following details:

• Object Name: Name of the specific data object where association or dissociation occurred.

• Data Object Type: The specific type of data object, such as Schema, Table, Table Column, File, etc., on which association or dissociation has occurred.

• Term: The name of the term involved in the association or dissociation.

• Action: "Add" for association, "Delete" for dissociation.

• Updated by: The user who made the change.

• Audit Date: Timestamp of the action.

Sorting and Filtering: Audit details can be sorted/filtered by Object Name, Object Type, Term, and Audit Date.

Example: On December 2, 2023, at 06:20:40 PM, user Peter Scot associated the term "100% marks" (from the Education domain) with the IPEDS Report and removed the term "School" (from the Education domain) from the "Student_Identifier” Table Column.

Object Name	Object Type	Terms	Action	Updated By	Date
IPEDS	Report	Education.100% Marks	ADD	[email protected]	2023-12-02 06:20:40 PM
Student_identifier	Table Column	Education.School	DELETE	[email protected]	2023-12-02 06:20:40 PM

Sample screenshot featuring Audit Trails > Catalog > Terms information.

Tags

In OvalEdge, when a tag is associated or disassociated with a data object such as Schema, Table, Table Column, File, etc., the system records and displays the following details:

• Object Name: Name of the specific data object where association or dissociation occurred.

• Data Object Type: The specific type of data object, such as Schema, Table, Table Column, File, etc., on which association or dissociation has occurred.

• Tag: The name of the tag involved in the association or dissociation.

• Action: "Add" for association, "Delete" for dissociation.

• Updated By: The user who made the change.

• Audit Date: Timestamp of the action.

Sorting and Filtering: Audit details can be sorted/filtered by Object Name, Object Type, Term, and Audit Date.

Example: On December 2, 2023, at 06:20:40 PM, user Peter Scot associated the tag "tagger" with the "bhg" report and removed the tag "tag223" from the data object "Student_Identifier” Table Column.

Object Name	Object Type	Tag	Action	Updated By	Date
bhg	Report	tagger	ADD	[email protected]	2023-12-02 06:20:40 PM
Student_identifier	Table Column	tag223	DELETE	[email protected]	2023-12-02 06:20:40 PM

Sample screenshot featuring Audit Trails > Catalog > Tags information.

Data Objects

The "Data Objects" tab tracks changes to governance roles assigned to data objects. This includes:

• Crawled Data: When a data object is crawled, its initial association with a governance role is audited.

• Governance Role Updates: Any subsequent modifications to the data object's governance role are also captured.

The audit log records the following details:

• Connection Name: Connector used for the action (if applicable).

• Data Object Details:

  • Type (e.g., schema, table, column, file)

  • Unique ID

  • Name

• Action: "INSERTED" for crawling, "UPDATED" for subsequent changes.

• Governance Role Changes (From/To):

  • Owner

  • Steward

  • Custodian

  • Any other optional roles

• Source: Where the change originated (crawling or catalog).

• Updated By: The user who made the change.

• Updated On: Timestamp of the action.

Sorting and Filtering: Audit details can be sorted/filtered by Connector Name, Object Type, Action, Updated By, and Updated On.

Example: On December 2, 2023, Peter Scot changed the owner of the "Cali vs Texas" report from Harry to himself.

Connection Name	Object Type	Object Id	Object Name	Action	Ownership Changed From	Ownership Changed To	Updated By	Updated On
Tableau	Report	1000	Cali vs Texas	UPDATED	Owner	Peter Scot	Peter scot	2023-12-02 06:20:40 PM
Tableau	Report	1000	Cali vs Texas	DELETED	Owner	Harry	Peter scot	2023-12-02 06:20:40 PM

Sample screenshot featuring Audit Trails > Catalog > Data Objects information.

Codes

The "Codes" tab tracks user activity related to queries executed and downloads within the OvalEdge Query Sheet. It captures the following information:

• Code Name: Name associated with the code.

• Code: The actual query or script used.

• Downloaded: Whether the user downloaded the code (Yes/No).

• Execution User: The user who ran the code.

• Execution Type: The type of code executed (e.g., SQL, trigger, procedure).

• Execution Date: Timestamp of when the code was run.

Sorting and Filtering: Audit details can be sorted/filtered by Code Name, Code, Download, and Execution Date.

Sample screenshot featuring Audit Trails > Catalog > Codes information.

Custom Field Values

The "Custom Field Values" tab tracks changes to custom fields associated with data objects.

The audit log captures the following:

• Custom Field Details:

  • Type (Text, Number, Code, Date)

  • Name

• Object Details:

  • Name

  • Type (Schema, Table, Column, File, etc.)

• Action: "Add," "Update," or "Delete."

• Changed Value: The specific value modified

• Updated By: The user who made the change

• Audit Date: Timestamp of the action

Sorting and Filtering: Audit details can be sorted/filtered by Custom Field Type, Custom Field Name, Object Type, Action, Updated By, and Date.

Sample screenshot featuring Audit Trails > Catalog > Custom Field Values information.

Custom Object Definition

The "Custom Object Definition" tab tracks changes to custom objects associated with data objects. This helps users understand the details of code, text, and date custom fields added to a data object.

The audit log captures the following:

• Custom Field Details:

  • Type (Text, Number, Code, Date)

  • Name

• Object Details:

  • Type (Schema, Table, File, Report, etc.)

• Action: "Add," "Update," or "Delete" for the custom object

• Changed Element: Specifies the particular element type where the change occurred. This includes the name of a custom field, the option of enabling or disabling, making the custom field editable in UI, editable in API, and LMDF (Load Metadata From Files).

• Connector ID: ID of the connector on which the change occurred.

• Updated By: The user who made the change

• Audit Date: Timestamp of the action

Sorting and Filtering: Audit details can be sorted/filtered by Custom Field Type, Custom Field Name, Object Type, Action, Changed Value, Connector ID, Updated By, and Date.

Sample screenshot featuring Audit Trails > Catalog > Custom Object Definition information.

Description

The "Description" tab tracks changes to descriptions associated with data objects. This helps users understand the details related to business or technical descriptions added or updated for a data object.

The audit log captures the following:

• Object Details:

  • Name

  • Type (Schema, Table, Column, File, Term, etc.)

• Source: Where the change originated (Data Catalog, LMDF, Service Desk, OvalEdge APIs)

• Action: "Added" or "Updated"

• Description Type: "Business" or "Technical"

• Updated By: The user who made the change

• Audit Date: Timestamp of the action

Sorting and Filtering: Audit details can be sorted/filtered by Object Name, Object Type, Description, Source, Action, and Date.

Sample screenshot featuring Audit Trails > Catalog > Description information.