Introduction

After Canopy’s computation engine has run, the resulting output data can be accessed in a number of different ways.

DataDirect is the recommended method for analytical consumption of your data, meaning it is best suited for reports and business decisions as opposed to using the data for operational business processes. It is a read-only PostgreSQL database connection that allows you to query your data in bulk in near real-time.

📘

Who would benefit the most from DataDirect?

• Data analysts and engineers
• Credit risk and Business Intelligence teams

DataDirect vs API Requests

DataDirect was designed to solve a few key points over the API approach:

DataDirect solves the problem of having to make multiple API calls and having to store the data off somewhere in order to query it.

Common Use Cases

Loan Tapes

Export a snapshot of your customer base and loans. By connecting DataDirect to your data warehouse, automate reports to your capital provider. Relevant data from Canopy include all customers, associated products, outstanding balances and deadlines etc.

Loan Portfolio Dashboards

Overview your portfolio performance at a glance. By connecting DataDirect to your BI solution, see a high-level summary of your loan portfolio. This could include the total number of active loans, the total loan amount outstanding, and any important performance indicators such as delinquency rates or default rates.

Ad-hoc SQL Queries

Discover new business insights. By accessing DataDirect with your database app of choice (e.g. Postico), execute any SQL query to uncover new patterns in your data. The data can help you answer questions such as:

1. Which customers are paying in full each month?
2. What strategies produce the highest repayment rates?
3. Where is my highest cost of servicing coming from?

How does it fit within Canopy's Platform?

For clarity, here are a few additional methods that Canopy provides for accessing your output data, their individual use cases and read/write rights:

Checking data freshness

DataDirect data is typically refreshed every hour. To identify the time of the last refresh and the state it represents, you can check for the most recent related record in the refresh_history:

select 
  table_name,
  last_updated_at 
from data_direct.refresh_history;

Changing Timezone Configuration in Database Clients

In order to ensure that your database interactions reflect the appropriate timezone, it's essential to configure your SQL client application to use the desired timezone. By default, our databases are configured to use Coordinated Universal Time (UTC). However, depending on your location or specific requirements, you may need to adjust the timezone settings in your SQL client.

Changing the timezone configuration in your SQL client ensures that timestamps and datetime values are displayed and interpreted correctly according to your local timezone.

Below are general steps for changing the timezone configuration in some commonly used SQL client applications:

1. PostgreSQL's psql Command Line Tool:

When connecting to your PostgreSQL database using psql, you can specify the timezone using the TZ environment variable. For example:

psql -h your_database_host -U your_username -d your_database_name -c 'SET TIME ZONE your_desired_timezone;'

Replace your_desired_timezone with the timezone you want to use, such as 'America/New_York'.

2. GUI-based SQL Clients (e.g., pgAdmin, DBeaver):

In graphical SQL clients, timezone configuration settings are typically found in the connection properties or preferences menu. Look for options related to timezone, date/time format, or session settings, and adjust them according to your requirements.

DBeaver: In Window -> Preferences. Go to User Interface and change the Client Timezone. Restart dbeaver.