Diagram Enhancements v5.3: Pictures and JSON

Instructor:

Allison Selby, Sr Manager, Instructional Design

Objectives:

  • Explain picture feature with traceability diagram
  • Demonstrate View Editor layout options
  • Show access to JSON edits

Description:

In this course, we will review the additional features found in v5.3 impacting the diagrams. In the 5.3 version, now we have an option for taking a picture of the traceability diagram. This allows you to save a state, literally take a picture of the traceability diagram, and save that whether for future reference for a report, to pin it, or to share it with a team. The pictures are still interactive as well, allowing you to start a workflow, apply trace, expand and collapse. Also, for the view editor, there’s some additional layout options using JSON. Some of those layout options include changes to the “edgeBends” and “nodeCompaction.”

Structural Concepts: Working with Assets v5.x

Instructors:

  • Trevor Gori, Data Steward
  • Matthew Tager, Data Steward
  • Romy Weidner, Data Steward

Objectives:

  • Classify asset types
  • Explain Global Create for business terms
  • Demonstrate importing assets from Excel

Description:

We will begin this course by creating assets, which represent the structural concepts of the operating model. Assets are often grouped together according to their function, project, or knowledge area. There are different types of assets, and each have different characteristics called attributes, and those attributes can have different relations. The Collibra Platform includes five core asset types to start your data governance structure based on their use, business assets, technology assets, data assets, governance assets and issues.In this course, we’ll learn how to create assets and different asset types, and we’ll see how the asset types affect the domain type they’re assigned. We will also address creating business terms and importing additional assets from Excel.

Traceability and Interactive Lineage Diagrams v5.x

Instructor:

Erwin Dral, Product Manager

Objectives:

  • Explain diagram features
  • Show asset type customization
  • Interpret nodes and edges

Description:

Never leave the diagram! Learn everything about how to maximize the capabilities of our interactive data lineage diCD- Done us, tags, communities, domains and responsibilities. Or simply turn off the overlays with a simple click. 

Business and Technical Lineage

Instructor: 

Ralf Strichau, Customer Advisory Manager

Objectives:

  • Explain business and technical lineage
  • Summarize levels of automation
  • Demonstrate relationships between assets and policies

Description:

In this course, we will be addressing business and technical lineage. We will demonstrate how technical and business lineage can be presented in diagrams to view the relations between assets and data sources. We will cover different levels of automation, from fully manual to the fully automated documentation of data lineage. We’re going to touch on stitching, which is a technique to document data lineage between different systems. Stitching is applied when the data leaves one system and it is fed into another system or data store. Lastly, we going to add on data governance, including the use of your policies and procedures on top of your data governance as well as issue management.

Enterprise Information Management: The Operating Model 5.x

Instructor:

Vasiliki Nikolopoulou, Presales Engineer

Objectives:

  • Define data governance and enterprise information management
  • Assess governing council and responsibilities
  • Develop procedures and catalogs of assets

Description:

Learn the definition of data governance, the definition of the operating model, and the operating model components. We will begin by defining data governance and enterprise information management. We will review the process of establishing a governance council of people with responsibilities and roles, a defined set of procedures with an execution plan for these people to execute, and catalogs of assets with their hierarchies and relationships or lineage.The operating model is a visual representation of how data governance is implemented at an enterprise level. The operating model consists of the following; a governing body or council with the responsibilities and roles, a defined set of procedures with an execution plan or workload, and catalogs of assets and types of assets with their characteristics and relationships.

Introduction to the Operating Model 5.x

Instructor:

Benedict Benoit, Sales Engineer

Objectives:

  • Analyze strategic planning
  • Examine the meta model
  • Classify roles and responsibilities

Description:

The Operating Model is based on three pillars, consisting of the organization, the assets that are of value to the organization and the people and processes, who will be responsible for certain tasks. Begin the process with strategic planning to determine the approach, to design the meta model and to determine the execution within Collibra. Other aspects to consider will be assigning roles and responsibilities, and to identify the processes to guide the data governance procedures. Our workflow process will dictate what processes need to be executed in order to do certain tasks, such as introducing a new business term. What process do we need to follow? That’s going to be part of the processes that we configure within Collibra.

If you are learning about the Operating Model for the first time, we recommend the following sequence:

  • Introduction to the Operating Model 5.x
  • Out-of-the-Box Operating Model 5.x
  • Operating Model 5.x: Organization Concepts

Operating Model 5.x: Organization Concepts

Instructor:

Benedict Benoit, Sales Engineer

Objectives:

  • Establish community and domain types
  • Assign responsibilities
  • Assess workflows

Description:

Learn the process regarding the organizational components of the operating model. In the lesson example, we will have a top level Community called Operating Model Organization, with two sub-communities, one for Operations, one for Reference Data. Within Operations, we will have two domains, one for Production Reports and one for Finance Reports. Within Production Reports, we can have multiple assets of the type Report, which is the master type of the type Internal Report and External Report. The same can happen within that Finance Reports. We will also review assigning roles and responsibilities, from the Chief Data Officer to Data Steward. The roles will determine who is responsible for certain tasks. We will use the Simple Approval process to review this particular workflow and identify the tasks assigned to various roles.

If you are learning about the Operating Model for the first time, we recommend the following sequence:

  • Introduction to the Operating Model 5.x
  • Out-of-the-Box Operating Model 5.x
  • Operating Model 5.x: Organization Concepts

Organizational Concepts: Communities and Domains v5.x

Instructor:

Claire Boger, Director of Education

Objectives:

  • Construct communities and subcommunities
  • Select domain types
  • Choose Business Glossary

Description:

Your company is continuously aiming for improved financial performance, product quality, or operational excellence. The organization is structured help achieve these goals. Just like your company is organized to achieve its business goals, your data governance initiative should be organized to support your governance goals. The foundation components of data governance organization are communities and domains.

NOTE: Some of the concepts demonstrated in this lesson require settings associated with the role of Community Manager. We’ve included the demonstrations so you understand how communities and domains are created. 

Out-of-the-box Operating Model 5.x

Instructor:

Benedict Benoit, Sales Engineer

Objectives:

  • Identify the operating model
  • Organize asset types
  • Apply characteristics to assets

Description:

Learn the procedures involved with designing your Operating Model or to use an out-of-the-box model by reviewing the process step by step. Review how to assign and understand inheritance when assigning attributes, as well as the option to disconnect from the parent attributes. We will create custom asset types while evaluating how they are part of a hierarchy. In our example, the report asset type is inherited from the business asset. We will review the relations between asset types and how to edit the characteristics and any unnecessary fields. And then we will focus on some of the reference data codes and creating global assignments.

If you are learning about the Operating Model for the first time, we recommend the following sequence:

  • Introduction to the Operating Model 5.x
  • Out-of-the-Box Operating Model 5.x
  • Operating Model 5.x: Organization Concepts

Structural Concepts: Asset Characteristics v5.x

Instructors: 

  • Trevor Gori, Data Steward
  • Matthew Tager, Data Steward

Objectives:

  • Explain asset characteristics
  • Demonstrate roundtrip import/export
  • Infer relationships between assets

Description:

We will review the types of characteristics and their importance, including how to create, edit, export and import attributes and relations for assets. There are two types of characteristics that you can assign to an asset: attribute types and relation types. An attribute is a literal value that captures information about an asset and an attribute is an instance of exactly one attribute type. We will also conduct a roundtrip, with importing from Excel and then export an updated table. Finally, we will start to form relationships between various assets inside of the Collibra Platform.

>