Business Discovery Blog

1 Post authored by: Arthur Lee
Arthur Lee

Metadata Made Easy

Posted by Arthur Lee Jul 19, 2011

In an earlier blog post, “Qlikview’s Pragmatic Approach to Metadata,” we explained how QlikView takes a fresh approach to metadata that doesn’t involve a lot of overhead to create or maintain since it is naturally exposed.  Perhaps the biggest difference is that most other solutions offer a separate module sometimes at an additional cost that is often difficult to set up and maintain.

 

Recently, we released a utility called the Meta Model that helps developers and administrators automate the entire process of understanding the metadata of a QlikView deployment (download here).  With this utility, it is now possible to gain deep insight into QlikView’s metadata.

 

The Meta Model is composed of two QlikView documents:

 

  • MetaScanner.qvw – this is the metadata “collector” application. Run this application each day after your daily reloads are completed and it will collect and accumulate your QlikView metadata into a “Meta Model.”  You can then leverage this Meta Model for many monitoring, cataloging, analysis, and support capabilities.

 

  • MetaMonitor.qvw – this is a fully functional demonstration application based on the Meta Model.  This application is not required as part of the Meta Model solution but can be used as a starting point to discover some of the great things in the Meta Model such as gaining a better understanding of the data lineage, server performance statistics, detailed history of data loads and much more.

Example of the Meta Monitor application.png

One advantage of QlikView’s approach to metadata is that developers can easily create their own applications on top of the Meta Model and/or extend the Meta Model for their specific needs.   You can see one such example at the QlikCommunity Meta Model User Group which is dedicated to this utility. This example uses Google’s charting API to enable QlikView developers and administrators to visually see the data connections within your deployment.

 

If you are using QlikView today, we encourage you to download the utility here and experience the power of the Meta Model.  If you are new to QlikView, you can be assured that the metadata of your future applications can be unlocked without the headaches of most other BI solutions.

In an earlier blog post, “Qlikview’s Pragmatic Approach to Metadata,” we explained how QlikView takes a fresh approach to metadata that doesn’t involve a lot of overhead to create or maintain since it is naturally exposed.  Perhaps the biggest difference is that most other solutions offer a separate module sometimes at an additional cost that is often difficult to set up and maintain[WU1] .

Recently, we released a utility called the Meta Model that helps [EDR2] developers and administrators automate the entire process of understanding the metadata of a QlikView deployment (download here).  With this utility, it is now possible[WU3] [EDR4] to gain deep insight into QlikView’s metadata.


[WU1]Erica – I changed the sentence structure around – hopefully it makes more sense.

[EDR2]Helps who – developers? Administrators?

[WU3]So since I addressed it in the previous sentence – I probably don’t need to repeat it.

[EDR4]Possible for who – developers? Administrators?

In an earlier blog post, “Qlikview’s Pragmatic Approach to Metadata,” we explained how QlikView takes a fresh approach to metadata that doesn’t involve a lot of overhead to create or maintain since it is naturally exposed.  Perhaps the biggest difference is that most other solutions offer a separate module sometimes at an additional cost that is often difficult to set up and maintain.

Recently, we released a utility called the Meta Model that helps developers and administrators automate the entire process of understanding the metadata of a QlikView deployment (download here).  With this utility, it is now possible to gain deep insight into QlikView’s metadata.

The Meta Model is composed of two QlikView documents:

·         MetaScanner.qvw – this is the metadata “collector” application. Run this application each day after your daily reloads are completed and it will collect and accumulate your QlikView metadata into a “Meta Model.”  You can then leverage this Meta Model for many monitoring, cataloging, analysis, and support capabilities.

·         MetaMonitor.qvw – this is a fully functional demonstration application based on the Meta Model.  This application is not required as part of the Meta Model solution but can be used as a starting point to discover some of the great things in the Meta Model such as gaining a better understanding of the data lineage, server performance statistics, detailed history of data loads and much more

In an earlier blog post, “Qlikview’s Pragmatic Approach to Metadata,” we explained how QlikView takes a fresh approach to metadata that doesn’t involve a lot of overhead to create or maintain since it is naturally exposed.  Perhaps the biggest difference is that most other solutions offer a separate module sometimes at an additional cost that is often difficult to set up and maintain.

Recently, we released a utility called the Meta Model that helps developers and administrators automate the entire process of understanding the metadata of a QlikView deployment (download here).  With this utility, it is now possible to gain deep insight into QlikView’s metadata.

The Meta Model is composed of two QlikView documents:

·         MetaScanner.qvw – this is the metadata “collector” application. Run this application each day after your daily reloads are completed and it will collect and accumulate your QlikView metadata into a “Meta Model.”  You can then leverage this Meta Model for many monitoring, cataloging, analysis, and support capabilities.

·         MetaMonitor.qvw – this is a fully functional demonstration application based on the Meta Model.  This application is not required as part of the Meta Model solution but can be used as a starting point to discover some of the great things in the Meta Model such as gaining a better understanding of the data lineage, server performance statistics, detailed history of data loads and much more

In an earlier blog post, “Qlikview’s Pragmatic Approach to Metadata,” we explained how QlikView takes a fresh approach to metadata that doesn’t involve a lot of overhead to create or maintain since it is naturally exposed.  Perhaps the biggest difference is that most other solutions offer a separate module sometimes at an additional cost that is often difficult to set up and maintain.

Recently, we released a utility called the Meta Model that helps developers and administrators automate the entire process of understanding the metadata of a QlikView deployment (download here).  With this utility, it is now possible to gain deep insight into QlikView’s metadata.

The Meta Model is composed of two QlikView documents:

·         MetaScanner.qvw – this is the metadata “collector” application. Run this application each day after your daily reloads are completed and it will collect and accumulate your QlikView metadata into a “Meta Model.”  You can then leverage this Meta Model for many monitoring, cataloging, analysis, and support capabilities.

·         MetaMonitor.qvw – this is a fully functional demonstration application based on the Meta Model.  This application is not required as part of the Meta Model solution but can be used as a starting point to discover some of the great things in the Meta Model such as gaining a better understanding of the data lineage, server performance statistics, detailed history of data loads and much more

Filter Blog

By date:
By tag: