Skip to Main Content

Introducing the Core Data Exchange

Over the years, each independent feature set of the Campus Labs platform has collected bits and pieces of data elements in silos, creating a scattered representation of basic information about students, much like a campus.

We have released a new protocol that makes it easier to send Campus Labs your Account, Course, and Demographic information to be used in the platform. We call this process the Core Data Exchange.

Over the coming months we'll be asking member campuses to begin the process of migrating from sending these core data elements to individual feature sets of the platform to the new Core Data Exchange; which acts like a central storage warehouse for all elements of Campus Labs.

Current bulk data loading to Campus Labs

Using the Core Data Exchange


This fundamental change in how the Campus Labs platform receives data has many positive benefits such as reducing the number of imports that need to be prepared by a member campus and it gives our development team the ability to build more focused data features because of a stable and central data set of core data about students.


Here's what you need to know

1. Do I need to do anything right now to keep my Campus Labs features working?

- No. We will be migrating to the Core Data Exchange over the next few months. Various features will begin to take advantage of the Core Data Exchange soon.

2. If we want to use a feature that relies on the Core Data Exchange, how do we get started?

- Contact your Campus Labs consultant and they will get you started with this new process.  The first step in using the Core Data Exchange is to identify a Data Manager on your campus that can review the Core Data Exchange documentation and who can access the data that you want to send to the Campus Labs platform.  

3. Are there any important dates involved in this new way of sending data to the platform?

- Yes. we have developed some migration goal dates for members using the Course Evaluations and/or Beacon features of the platform.  Our goal is to have all member campuses using Course Evaluations or Beacon using the Core Data Exchange data loads by Fall 2017.

4. What is the biggest change that we should think about as we start the process for migrating to the Core Data Exchange?

- If you have been sending data to the Campus Labs platform via automated imports or periodic manual imports, then it is likely that the Core Data Exchange import process will feel very similar, however some file formats have been expanded or tweaked for consistency and specificity.  You will need to audit your current imports to make sure that they will work with the new process.

6. What are the different ways to transfer data to the Core Data Exchange?

- We will support three methods for loading data into the Campus Labs platform via the Core Data Exchange.

1. Automated & Scheduled sFTP file imports

Enabling regular data loads with the automated sFTP method should be very familiar to campuses who have implemented data systems in the past, including the Beacon and CollegiateLink elements of the current Campus Labs platform. This method is a popular choice form most members because of its familiarity for campus IT teams.

2. Bulk load web services (or APIs)

For more advanced member campuses who have experience in programming against Application Programming Interfaces (APIs) we have several documented endpoints that can be used to load large data sets.

3. Manual imports via the application user interface

This simplified method is used mainly for getting acquainted with the import process before using the automated sFTP method and for campuses that do not have the technical ability to achieve sFTP transfers.


Please read our Core Data Exchange technical support documentation for more information.

Have more questions? Submit a request