Introduction

For a functional overview of how the integration works, see Functional Overview.

The Element451 integration with CFNC is designed to be simple and automatic from a user perspective, while handling complex data processing behind the scenes.

Element451 has built a baseline integration that interacts with CFNC’s API endpoints and syncs their application data (including biographic/demographic, previous school history, emergency contacts, etc) as well as an application PDF and transcripts associated with the application/student. While a lot of data is brought in, there may be additional properties your integration is configured to bring in based upon your SOW.  Additionally, there can be multiple types of applications synced in from CFNC into Element depending upon a partner’s needs.  This guide assumes the traditional undergraduate application is being synced, but additional application types can be done and would follow the same pattern.

Scope of This Guide

This section provides a high-level technical overview of what occurs after the integration process is by the various sync schedules (see Functional Overview).

Primary Tool

Element451 uses Dagster to orchestrate all integration processes.

Dagster manages the following sync types:

• CFNC Application Data → Element451
• CFNC Application PDFs → Element451
• CFNC Transcripts → Element451

How It Works

• Dagster runs a series of jobs and sensors to monitor and execute integration activity.
• Within each sync process, multiple operations (ops) are performed to:
  • Extract data
  • Transform data
  • Send data to Element451

Each sync is composed of these coordinated steps to ensure data is processed and transmitted correctly across systems.