Looker operating model

The Looker scanner collects Looker metadata and sends it to the Collibra Data Lineage service. Collibra processes the metadata and creates new Looker assets and relations in Data Catalog. You can see them on the asset page overview or visualize them in a diagram or in a technical lineage.

Note 
  • The assets have the same names as their counterparts in Looker. Full names and Display names cannot be changed in Data Catalog.
  • Asset types are only created if you have all specific Looker and Data Catalog permissions.
  • All Looker asset types are created in the same domain.
  • Relations that were manually created between Looker assets and other assets via a relation type in the Looker operating model are deleted after a refresh of the Looker metadata.

Looker metadata overview

The following image shows the relations between Looker asset types.

Harvested metadata per asset type

The following table shows the harvested Looker metadata for each Looker asset type. This table also shows the resource ID for each asset type and metadata.

Asset type

Synchronized metadata

Resource ID

Looker Dashboard

Resource ID: 00000000-0000-0000-0000-100000000013

Full name

 
Display name  
Description 00000000-0000-0000-0000-000000003114
Document creation date 00000000-0000-0000-0000-000000000260
Document last accessed date

00000000-0000-0000-0000-000000000268

Favorites count

00000000-0000-0000-0000-000000000269

Owner in source

The only harvested metadata are email addresses.

00000000-0000-0000-0000-200000000001
Technical Data Type 00000000-0000-0000-0000-000000000219
URL 00000000-0000-0000-0000-000000000258
Visit count

00000000-0000-0000-0000-000000000264

Business Dimension groups / is grouped into Report 00000000-0000-0000-0000-120000000002
Report groups / is grouped into Report 00000000-0000-0000-0000-120000000004
Report related to / impacted by Business Asset 00000000-0000-0000-0000-120000000006
Report uses / used in Report 00000000-0000-0000-0000-120000000007

Looker Data Set

Resource ID: 00000000-0000-0000-0000-100000000017

Full name

 
Display name  
Description 00000000-0000-0000-0000-000000003114
Data Set contains / is part of Data Element

00000000-0000-0000-0000-000000007062

Technology Asset source system for / source system Data Asset 00000000-0000-0000-0000-000000007050

Looker Data Set Column

Resource ID: 00000000-0000-0000-0000-100000000018

Full name

 
Display name  
Description 00000000-0000-0000-0000-000000003114
Data Set contains / is part of Data Element

00000000-0000-0000-0000-000000007062

Report Attribute sourced from / is source of Data Attribute 00000000-0000-0000-0000-120000000010

Looker Folder

Resource ID: 00000000-0000-0000-0000-100000000012

Full name

 
Display name  

Document creation date

00000000-0000-0000-0000-000000000260

Owner in source

The only harvested metadata are email addresses.

00000000-0000-0000-0000-200000000001
BI Folder assembles / is assembled in BI Folder 00000000-0000-0000-0000-120000000001
Business Dimension groups / is grouped into Report 00000000-0000-0000-0000-120000000002
Server hosts / is hosted in Business Dimension 00000000-0000-0000-0000-120000000000

Looker Look

Resource ID: 00000000-0000-0000-0000-100000000014

Full name

 
Display name  
Description 00000000-0000-0000-0000-000000003114
Document creation date 00000000-0000-0000-0000-000000000260
Document last accessed date

00000000-0000-0000-0000-000000000268

Document modification date 00000000-0000-0000-0000-000000000261
Favorites count

00000000-0000-0000-0000-000000000269

Owner in source

The only harvested metadata are email addresses.

00000000-0000-0000-0000-200000000001
Report image 00000000-0000-0000-0000-000000000262
URL 00000000-0000-0000-0000-000000000258
Visit count

00000000-0000-0000-0000-000000000264

Business Dimension groups / is grouped into Report 00000000-0000-0000-0000-120000000002
Report groups / is grouped into Report 00000000-0000-0000-0000-120000000004
Report uses / used in Report 00000000-0000-0000-0000-120000000007

Looker Report Attribute

Resource ID: 00000000-0000-0000-0000-100000000019

Full name

 
Display name  

Report Attribute contained in / contains Report

00000000-0000-0000-0000-000000007058
Report Attribute sourced from / is source of Data Attribute 00000000-0000-0000-0000-120000000010

Looker Query

Resource ID: 00000000-0000-0000-0000-100000000016

Full name

 
Display name  

URL

00000000-0000-0000-0000-000000000258

Business Dimension groups / is grouped into Report

00000000-0000-0000-0000-120000000002
Report Attribute contained in / contains Report 00000000-0000-0000-0000-000000007058

Report uses / used in Report

00000000-0000-0000-0000-120000000007

Looker Tenant

Resource ID: 00000000-0000-0000-0000-100000000011

Full name

 
Display name  
Description 00000000-0000-0000-0000-000000003114
Server hosts / is hosted in Business Dimension 00000000-0000-0000-0000-120000000000
Technology Asset source system for / source system Data Asset 00000000-0000-0000-0000-000000007050

Looker Tile

Resource ID: 00000000-0000-0000-0000-100000000015

Full name

 

Display name

 
Business Dimension groups / is grouped into Report 00000000-0000-0000-0000-120000000002
Report uses / used in Report 00000000-0000-0000-0000-120000000007

Note The metadata that is shown on the assets' pages depends on the asset type's assignment. As a result, you might not see all harvested metadata on the asset's page by default.

Additional information

For the Owner in source attribute, the following rules apply:

  • If the system creates a Looker data object and the Looker data object does not have a user ID, the Owner in source attribute is shown as System on the asset page.
  • If the user who created a Looker data object no longer exists, the Owner in source attribute is shown as empty on the asset page.

Example of ingested Looker metadata

The following image shows an example structure after Looker ingestion.

Recommended hierarchy within a domain

You can enable hierarchies for the domain (or domains) in which your Looker assets were ingested. Doing so makes it easier to understand the relation between your Looker assets, when viewing the assets on the domain page.

Follow these steps to enable and configure the recommended hierarchy.

Steps

  1. Open the domain page of the relevant BI Catalog domain.
  2. On the content toolbar, click .
    The Configure Hierarchy dialog box appears.
  3. Select Enable Hierarchy.
  4. Select Multipath.
  5. Start typing and select each of the following relation types:
    • Server hosts Business Dimension
    • Business Dimension groups Report
    • Report contains Report Attribute
    • Technology Asset source system for Data Asset
    • Data Set contains Data Element
    • Data Attribute is source of Report Attribute
  6. Click Apply.

Note 
  • In an asset view, if any asset is deleted, for example via synchronization or manual deletion, the view is recreated and the hierarchy is lost. In this case, you can again enable and configure the recommended hierarchy.
  • When viewing the hierarchy for a community or domain, if the parent of a node that is in the community or domain belongs to a different community or domain, that node is not shown in the hierarchy.

Create a Looker operating model diagram view

You can create a Looker-specific diagram view, to visualize the operating model. The following procedure provides instruction on how to quickly create a new diagram view by copying and pasting the JSON code in the diagram view text editor.

Steps

  1. Open an asset page.
  2. In the tab pane, click Diagram.
    The diagram appears in the default diagram view.
  3. Click to add a new view.
  4. Click the Text tab, to switch to the diagram view text editor.
  5. Click Show me the JSON code below this procedure, to expand the code.
  6. Click Copy code in the top-right of the expanded code, to copy the code.
    The code is copied to your clipboard.
  7. Paste the code in diagram view text editor.
  8. Click Save.
  9. Edit the name and description of the diagram view, to suit your needs.