In this article, we will demonstrate how to import tables from a CSV file, calculate service duration through transformations, and migrate the cleaned data into the destination database using Bold Data Hub. Follow the step-by-step process below.
Sample Data Source:
Sample CSC Data
Note: On-Demand Refresh will be triggered when the pipeline is saved. If needed, the pipeline can be scheduled in the Schedules tab.
Go to the Transform tab and click Add Table.
Enter the table name to create a transform table for customer satisfaction summary.
Note: The data will initially be transferred to the DuckDB database within the designated {pipeline_name} schema before undergoing transformation for integration into the target databases. As an illustration, in the case of a pipeline named “customer_service_data”, the data will be relocated to the customer_service_data table schema.
Learn more about transformation here
Understanding the time taken to resolve tickets helps assess efficiency and identify potential bottlenecks in the support process. This query calculates the service duration by measuring the difference between ticket creation and resolution dates.
We use the DATEDIFF
function to compute the number of days between ticket creation and resolution. Only records with valid resolution dates are considered, and negative durations are excluded.
SELECT
Ticket_ID,
Ticket_Creation_Date,
Ticket_Resolution_Date,
DATEDIFF('day', CAST(Ticket_Creation_Date AS DATE), CAST(Ticket_Resolution_Date AS DATE)) AS Service_Duration_Days
FROM {pipeline_name}.sample_csc_data
WHERE
Ticket_Resolution_Date IS NOT NULL
AND Ticket_Creation_Date IS NOT NULL
AND DATEDIFF('day', CAST(Ticket_Creation_Date AS DATE), CAST(Ticket_Resolution_Date AS DATE)) > 0;