Ways to Access Denodo

Environments

Tufts' Denodo architecture has the following environments:

• Development: All development takes place here. All other environments are read-only and only have their code updated through deployments.

• Stage: Used for testing code before deploying to Production.

• Production: Stable, high-performance environment for end users.

These environments apply to both the Data Catalog and the Design Studio. When logging into either tool, make sure to select the best environment for your purposes.

Data Catalog

• Development: https://denodo-dev.it.tufts.edu:9443/denodo-data-catalog

• Stage: https://denodo-stage.it.tufts.edu:9443/denodo-data-catalog/#/

• Production: https://denodo-prod.it.tufts.edu:9443/denodo-data-catalog/#/

The Data Catalog is an interactive tool that allows end users to explore all of the data available in Denodo and see relevant meta data (which we don’t have much of yet.) Querying directly on the data in a specific view is possible within the catalog:

Design Studio

This is the “IDE” (Integrated Development Environment) where Denodo development happens, including updates to descriptions and other meta data.

In order to log in, hit this link: https://denodo-solution-manager.it.tufts.edu:19443/denodo-design-studio/#/

and in that window, put in the dev address:

And you end up here:

You can use Design Studio to connect to the Stage and Production VDP’s, access will be read-only. You can only make edits in the Development VDP.

Useful Resources

• Denodo User Guide

• Videos!! https://community.denodo.com/videos/

• TTS Denodo intro course slides (great basic overview): https://tufts.app.box.com/s/6bmxs8y89v564q38kluyn9m83wok7ur2

• Also, turns out ChatGPT is very useful in providing instructions!

• https://tufts.app.box.com/s/wkbsud6m6qfv6hoqbcsxjn3p6wp02bcs is a field showing the json that is actually flowing from Slate to Denodo.

Accessing Slate Data in Denodo

In both the DC and DS, Denodo is organized at the top level by “virtual database.” Within the virtual database there are 7 folders that always follow the same naming convention/purpose. The data pulled from Slate is added to a virtual database named ‘student_lifecycle.'

The 01-base_layer folder contains the “root” of where the data comes from. The 02-base_views folder includes each Slate query as cached since the last data pull from Slate, which can be identified by the prefix ‘bv_’

The 02-transformation folder contains the tables where data from the individual base views get unionized together into a single resource (currently application and person).

The 04-interface_fulfillment is where “business facing views” live and where queries can be executed by people with access (which is us).

Querying in Design Studio

Design Studio