About Core Data

The Anthology platform enables institutions to collect, manage and report on data useful for accreditation, student success, as well as teaching and learning. 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.

Core Data

The core data exchange process enables an institution to send basic, large data sets to the Anthology platform in order to establish user accounts and course information that will be used for data insight and reporting. There are three sets of data that Anthology considers Core Data:

  1. Accounts
  2. Course Data
  3. Demographics

The data will need to be extracted from your institution’s SIS or Data Warehouse and transferred in a .csv format or via API to Anthology in the central repository known as Core Data Management.  Each of the tools in the Anthology platform being utilized by your institution will look to Core Data to get some of the data points needed.   


MicrosoftTeams-image (2).png

Resource Roles

Role Role Source Responsibilities
Data Manager(s) Institution This role will be responsible for acquiring the required data and transferring it to Anthology.  They will be the primary contact from the institution for the Anthology Technical Team. The person in this role must have a thorough understanding of the selected exchange type(sFTP, API or Manual) as well as have access and familiarity with the SIS/Data Warehouse from which the data will be extracted from. This role will also be responsible for communicating risk from the institution to the Anthology team. This would include any risk or change to the expected timeline, and any relevant information that could affect the success of the implementation.
Consultant Anthology This role will be responsible for managing communication between the Data Manager, Technical Implementation Team and other stakeholders at the institution. The Consultant will work with the institution to ensure that the data transferred meets the needs of the platform.  This role will also communicate risks and needed changes to the timeline.
Technical Implementation Specialist Anthology This role will be responsible for working with the Data Manager to transfer knowledge specific to the Core Data process. For initial transfers, this role will assist the Data Manager in data validation and troubleshooting errors. The Technical Implementation Specialist will also be responsible for working with the institution to set expectations and an estimated timeline for the implementation of Core Data.


Data Transfer Methods

Scheduled file import via Secure File Transport Protocol (sFTP)

(Recommended Data Transfer Method)

This data transfer method allows institutions to send large data sets to the platform by saving .CSV "flat" files containing data for Accounts, Courses, and Demographics into a Anthology hosted directory via a sFTP connection.  The institution must provide the data in the file format indicated by Anthology 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.


MicrosoftTeams-image (1).png


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.  

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 where your Data Manager(s) will go 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 Core Data technical meeting with Anthology.  

This site is divided into three areas; importing data, exporting data and exploring your data.


Have more questions? Submit a request