The Campus Labs platform enables institutions to collect, manage and report on data useful for teaching and learning, accreditation and student success program design and improvement. The platform is offered to end-users as a software as a service (SaaS) web application, accessible via any modern web browser. The platform can, should, and in some cases, must be integrated into existing institutional data infrastructure to gain the most benefit from its capabilities through methods outlined in this document.
The core data exchange process enables an institution to send basic, large data sets to the Campus Labs platform in order to establish user accounts and baseline user information that will be used for data insight and reporting. There are three sets of data that are considered core data:
- Course Data
The data will need to be extracted from your institution’s SIS, LMS or Data Warehouse and transferred in a .csv format to Campus Labs in the central repository known as Core Data. From Core Data, the data will be pushed to all of the tools in the Campus Labs platform being utilized by your campus.
When it is determined that your campus will need to conduct a technical implementation, your technical contact will be contacted by Campus Labs to set up a Technical Discovery Meeting. During this initial meeting we will;
- Assess and analyze the technical needs of your institution
- Identify the primary data manager and technical contacts
- Identify important deadlines to determine our timeline
- Review provided technical documentation
- Assign initial action items initiate implementation
After the initial implementation meeting, a plan/timeline will be created by the Technical Implementation Specialist and provided to the technical contact/data manager.
Core Data Exchange
Data Transfer Methods
Scheduled file import via Secure File Transport Protocol (sFTP)
Allows institutions to send large data sets to the platform by saving .CSV "flat" files containing data for Accounts, Demographics, and Courses into a Campus Labs hosted directory via a sFTP connection. The institution must provide the data in the file format indicated by Campus Labs along with a manifest file (.done file) which indicates to the platform that the data file is complete and ready to be imported. Once the data and manifest files are saved to the directory, the platform processes the file and incorporates the information into its data set. Any errors are displayed via a web interface accessible by the Campus Data Manager.
Web service & API endpoints
A more advanced method, requiring proficient campus IT professionals, which allows both bulk and individual field loading of data to the platform via secure, scheduled transactions over the internet. Each data type endpoint offers the ability to create, retrieve, and update the data. This additional, fine-toothed control of each data type offers institutions ultimate flexibility in the delivery and management of core data in the platform.
For more information regarding our API end point, check out the Campus Labs API Explorer.
Manual file uploads
This method requires a user to import the data via a web interface (Data Management site). This method is the most limited in terms of flexibility and is generally reserved as a last resort if the more robust options are not possible.
Data Management Site
The Data Management site is the site your Data Manager(s) will use to manually upload, review errors (from manual and automated imports), and validate data. The site will be made available to the identified Data Manager(s) after your first Technical Meeting with Campus Labs.
This site is divided into three areas; Demographics, Courses and Accounts. Each area is where you access, import and validate, for the corresponding area of Core Data.