jthuma

Aster Tango Beta Repository DDL Explanation

Blog Post created by jthuma on Dec 18, 2015

PREFACE:  There are five entities within the Aster Tango Repository and they are all required.  Any modification to them could cause the system to fail or become unstable.  The names of the fields and entity objects should not be renamed or retyped.  You may have as many repositories within your environment that you want.  You can have a central team repository and your own repository.  Aster Tango Beta allows you to connect to any repository you want.  You can put your own custom entries into this repository.  You may secure your repositories as you desire.  Please note that this is your responsibility.  In order to load the repository you will have to be able to create table objects and you will have to access to ncluster_loader or another load utility.

 

The Aster Tango Beta Repository Scripts and DDL can be found here:  Aster Tango Beta Repository

 

SECURITY AND PERMISSIONS:  It is up to you and your organization how you secure this repository.  At a minimum users must have read access to all tables and write access to the script table.

 

What is the Aster Tango Repository:

 

A set of five table entities that hold metadata that support the Aster Tango Beta software.  Please note there is no referential integrity constraints managing these relationships.  If you change it you could break the relationships and this includes data changes.

 

Below is a brief description of the Aster Tango Repository Tables:

 

tango_type:  A table containing the genres of analytics available in Aster Tango.

  • a_type field values are expected to be unique.
  • tango_type has a 1:M relationship with tango_analytic (tango_type.a_type 1:M tango_analytic.a_type)
  • You may create your own types or buckets of analytics, just make sure that a_type is unique.
  • EXAMPLE ENTRY:

 

tango_type.JPG

 

tango_analytic:  A table containing the analytics available in Aster Tango.  A record in this table has a tango_type.a_type record associated with it as a parent.

 

  • ab_key field values are expected to be unique.
  • a_type field is required and enables the relationship to tango_type entity.
  • tango_analytic has a 1:M relationship with tango_statement (tango_analytic.a_type & tango_analytic.ab_key 1:M tango_statement.a_type & tango_statement.ab_key)
  • You may create your own analytic entries, just make sure that ab_key is unique and that a_type corresponds to an entry in tango_type.
  • EXAMPLE ENTRY:

 

tango_analytic.JPG

 

tango_statement:  A table containing the actual SQL-MR and SQL-GR statements with help content and other associated metadata.

 

  • ab_key, a_type, and ab_order field values are expected to be unique and make up the logical candidate key.
  • All fields are required and have specific meaning to the interface.  There will be a dedicated blog post to this in another section.
  • a_type field is required and enables the relationship to tango_type entity.
  • ab_key field is required and enables the relationship to tango_analytic entity.
  • ab_order field is the order in which the statements appear in the Aster Tango user interface.
  • tango_statement has no further relationship but relates to tango_type and tango_analytic.  (please see above for those relationships)
  • You may create your own statement entries, just make sure that a_type, ab_key, ab_order set is unique and that a_type corresponds to an entry in tango_type and ab_key relates to a tango_analytic entry.
  • EXAMPLE ENTRY:

 

tango_statement.JPG

 

tango_analytic:  A table entry that contains all video references for the video repository.  In order for this to work you must have access to the internet and YouTube.  Your organization might have policy that prevents you from accessing this via your network.

 

  • There is no unique constraint in this table.
  • video_url has a specific syntax:

 

tango_video.JPG

 

tango_script:  This is a script repository that can be used to save and share scripts.  Once a script is saved it becomes and artifact and is atomic.  You cannot change it unless you go directly to the table and change it manually.  This is for the sake of version control.  An Aster Tango Beta user cannot update or delete a script to a repository once it is persisted via the user interface.  Someone with the appropriate credentials and authority would have to perform this function.

 

  • tango_script comes with a set of scripts pre-loaded to assist you with learning aster.
  • EXAMPLE ENTRY:

tango_script.JPG

 

The Aster Tango Beta Entity Relationship Diagram is provided below.

ERD.JPG

 

 

 

 

 

 

READ ME FIRST:  Aster Tango Read Me First Instructions

TANGO BETA SOFTWARE ARCHITECTURE:  Aster Tango Software Architecture

INSTALLATION INSTRUCTIONS:  Aster Tango  Beta Installation

ASTER TANGO EULA: Aster Tango End User License Agreement

Outcomes