dv-mart

Generates BIG-IP Lua scripts for automated network setups.

35|7|Updated Apr 14, 2022
One-click install
npx skills add https://github.com/PatrickCuba/the_data_must_flow --skill dv-mart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dv-mart
Source: https://github.com/PatrickCuba/the_data_must_flow/tree/main/dvos-skills/skills/dv-mart
Command: npx skills add https://github.com/PatrickCuba/the_data_must_flow --skill dv-mart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Information Mart (IM) layer provides business-key oriented views built atop the Raw Vault, shielding analysts from vault internals, enabling BI tooling with stable representations and no exposure of hash keys. The IM acts as an Anti-Corruption Layer, allowing cross-hub, cross-satellite analytics without requiring users to understand complex Vault primitives.

Core Features & Use Cases

  • Generates IM views by integrating HUB, SAT, and satellite views (VC_/VH_ patterns) or PIT/Bridge patterns to deliver current-state and historical data slices.
  • Enforces governance rules like no hash keys in outputs and exposure of natural business keys, enabling clean, mission-ready BI artifacts.
  • Supports multi-hub and cross-satellite analytics, including traversal across links and bridges for comprehensive analytics.
  • Offers performance patterns (Supernova / Dynamic Iceberg) for large-scale deployments where query speed matters.

Quick Start

Create an IM view by joining HUB_<ENTITY> to SAT_<ENTITY> using VC_SAT_<ENTITY> or PIT_BRIDGE constructs to produce the business-key view, then run the Doctrine Enforcer to validate the design.

Frequently Asked Questions about dv-mart

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create BI-ready views from a Raw Data Vault?

Build Information Mart views by joining HUB and SAT tables using VC_ or VH_ patterns to expose natural business keys. This shields analysts from internal vault hash keys and delivers stable current-state or historical data slices.

What is an Information Mart in Data Vault 2.0?

An Information Mart is an anti-corruption layer that translates raw vault primitives into business-key oriented views. It enables cross-hub and cross-satellite analytics without exposing complex vault internals like hash keys to BI tools.

How do I hide hash keys when querying Data Vault satellites?

Hide hash keys by applying Information Mart governance rules that expose only natural business keys. The Doctrine Enforcer validates these views to ensure no internal hash keys leak into BI outputs.

When should I use PIT and Bridge tables for Information Mart views?

Use PIT and Bridge tables when handling cross-hub traversal and multi-satellite analytics. They align satellite data temporally, supporting complex current-state and historical requirements while maintaining scalable query performance.

Does Data Vault Information Mart support large scale analytics performance?

Information Mart supports large scale analytics performance through Supernova and Dynamic Iceberg patterns. These scalable performance modes optimize query speed for large deployments while maintaining standard business-key exposure.

How do I validate Information Mart views against Data Vault governance rules?

Validate Information Mart views against Data Vault governance rules by running the Doctrine Enforcer after view creation. This checks that outputs contain only natural business keys and confirms no vault hash keys are exposed to downstream BI tools.