Versions Compared

Old Version 8

changes.mady.by.user John Kostakos

Saved on

compared with

New Version Current

changes.mady.by.user Will Rensmith

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

The nVIRO Data Hub provides is a replicated read-only repository of data populated from nCORE, nFORM, and nSPECT.  The data is structured to store key nVIRO entities and relationships and to facilitate fast reporting.  A new database schema (DataHub) and several new database tables are added to support this capability. 

Long term direction for the Data Hub is to provide support for:

  • Data reporting / analytics
    • Advanced data reporting (fast, powerful data access, for ad-hoc and standard reporting)
    • ‘Executive’ dashboards (future)
  • Data re-use
    • Cross-pollinate data between nVIRO products
    • Support 3rd party integration
  • Low Code
    • Enable easier user report and data source definition (less SQL)
    • Consolidated way to configure form prefill, reports, doc gen, inspection plans etc.

Data Hub Population

  • Data Hub is populated in real-time from new nFORM submissions
  • Data Hub is (currently) updated nightly from nCORE, nFORM, nSPECT
  • Data Hub is available for reporting data in the new version of nVISAGE

Data Hub Reporting

The nVIRO nVISAGE / Data Hub Data Viewer is automatically configured to access data sources from the Data Hub. 

ExcerptData sources are classified

 The datahub is optimized for high performance inquiry and reporting.

Data Hub is populated in near real-time for the majority of data stored in nCORE and nFORM.

Data Hub is the data source for nVISAGE Data Viewer reports (with the exception of custom-written data sources)

Data Hub Entity Classification

Data entities in the Data Hub are categorized as follows:

  • CORE – Core nVIRO entities such as submissions, permits, and evaluations.

  • IDENTIFIER - Provides related Identifiers / Alternate Names for Sites

  • FORM – Submitted forms. Typically FORM data sources would be reported in conjunction with a SECTION data source.

  • PROGRAM – Program component forms. Typically PROGRAM data sources would be reported in conjunction with a SECTION data source.

  • SECTION – FORM or PROGRAM form section data.  These are available after selecting a FORM or PROGRAM data source

  • CUSTOM – Custom (non-Data Hub) data sources.

REFERENCE – A list of the

  • Custom data sources

.
Info

The following data source types support real-time reporting:

  • FORM
  • PROGRAM
  • SECTION
  • REFERENCE
  • CUSTOM

The following data source types are refreshed on a nightly basis:

  • CORE

  • are developed for specific clients/implementations. Data is fetched real-time from transactional data, often resulting in slower performance.

Data Hub Structure

The following diagram provides an high level overview of the core data CORE Data hub entities and relationships

On this page

Table of Contents

Sub-Topics

Page Treeroot@self

Future Capabilities

Long term direction for the Data Hub is to provide support for:

  • Data reporting / analytics

    • Advanced data reporting (fast, powerful data access, for ad-hoc and standard reporting)

    • ‘Executive’ dashboards (future)

  • Data re-use

    • Facilitate data sharing between nVIRO products

    • Support 3rd party integration

  • Low Code

    • Enable easier user report and data source definition (less SQL)

    • Consolidated way to configure form prefill, reports, document generation, inspection plan search tools, etc.

On this page

Table of Contents

Related Content