Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

This page is in development, and focuses on Oracle connections & organization for JIRA-based views & tables.

Further information on these and other Atlassian applications can be found here: Genomics Platform Atlassian Applications


Schemas & Usernames:

SCHEMA& USERNAMEDESCRIPTIONWHEN TO USE ITNOTES
REPORTING

This is where to write view synonyms that point to JIRADWH views. This can also be where view code drafts get written before being transferred to JIRADWH.

For all report-related read access, or when creating a view in REPORTING schema 
JIRADWHHome of actual DWH views. Home of ETL packages & functions that work on multiple JIRA schemas' data. This is where to write DWH code.Only when creating views or tables in JIRADWH schema 
LABOPSJIRA_5Home of the labopsjira data that the DWH looks at.

Rarely

 
PRODINFOJIRA_5Home of the labopsjira data that the DWH looks at. Rarely 
GPDEVJIRAThis is the "LABOPSJIRADEV" clone of labopsjira_5, which is refreshed on demand.During testing 
PRODINFOJIRA5_TEST This is the "GPDEVJIRA" server test clone which can be anything, depending on current testing needs.During testing 

Note: SEQPROD.REPORTING and COGNOS.COGNOS are home to lots of pipeline data, but also contain database links to SEQBLDR to allow joining of pipeline data with JIRA data.

More info for analytics users can be found here: JIRA DB Schemas

 

 

Datamart structure

Creating a new view

New views are created using as much standardization as possible, and are generally created in REPORTING schema until peer code-review has been performed. Views in the JIRADWH schema are good templates. Use the ETL functions whenever possible.

Custom fields

The ETL functions described above (Jira DWH) can be used to pull custom fields from specific JIRA schemas and projects. 

This document (JIRA Custom Fields) facilitates view SQL creation (and is especially useful when you need to add several CFs to your SQL). If you aren't sure which ETL function to use (e.g. get_text_fields vs get_option_fields), trial and error is okay.

ETL

We have built ETL functions to simplify view creation, standardize SQL structure, and provide scalability and schema flexibility. These functions are generic, allowing you to plug in whatever specifiers you need. Use ETL functions to specify schemas, projects, and custom fields. When querying JIRA data, most of the functions you'll need live in JIRADWH/Packages/ETL/Entries (see image at right).

More info and partial list of functions here: Jira DWH

Deprecated & Dropped schemas:

LABOPSJIRA
LABOPSJIRA44
LABOPSJIRA44_QA
LABOPSJIRADEV42
LABOPSJIRADWH
LABOPSJIRATEST_5
LABOPSJIRAUPTEST
LOJ_REPORTER
PRODINFOJIRA44
PRODINFOJIRA5_TEST
PRODINFOTESTJIRA42
  • No labels