|Overview||Importing These Files|
|Populating These Files||Products That Use These Files|
Demographics are used in Beacon and Insight to present interesting data visualizations, generate logical filtering, and create rules-based actions within the platform
For a deeper look into how Student Demographics are used in Insight, review the Implementing Student Demographics for Insight document.
There are two types of Demographic Imports;
- Faculty (69 available data points)
- Students (126 available data points)
Best Practices for Populating Demographics
This file typically includes demographic data for all students who registered or enrolled in a section during the term, so the scope should match the student query of the Accounts file.
To properly link demographic data to the accounts it describes, the PersonIdentifier AND the ExternalID should match the PersonIdentifiers defined in the Accounts file.
Generally, the EffectiveOn date should be populated with the current datetime that the data is extracted from the SIS. The initial load of Demographics data should use the start date of the current term. For a more detailed discussion of EffectiveOn dates for error correction and historical data loads, please see the Implementing Student Demographics for Insight document.
Because many of the Demographics fields are optional or may not be populated for all individuals, many tables must be left joined, and the files will likely contain many null values. Build the script to convert null values to blank values to ensure they are imported correctly.
For some datapoints, the Demographics file provides multiple fields, permitting up to 3 unique values. For example, the fields Major1-3 accommodates students with multiple majors. For most of these datapoints, the SIS stores each value associated with a user on its own record, so the script must pivot this data from a derived table that assigns each value a row number partitioned by user.
Selecting the correct records
Some tables used in Demographics retain historical data when changes are made. These records may be differentiated by inactive statuses, sequence numbers, timestamps, term identifiers, or other datapoints. When joining these tables, build in conditional statements to prevent duplicates and inaccuracies. For example, this may require the script to join on subqueries that find the most recent record for a given user.
Demographics term logic should typically align with the Accounts term logic, with the caveat that the same student should not be pulled for multiple terms simultaneously. Because demographic data can change from term to term, pulling demographics for a future term will overlay the data for the current term. If your Accounts term logic starts at the web registration date for a given term, consider delaying your Demographics term logic until the term begins. This may require exceptions for new students to ensure their data is populated ahead of the term if needed.
You should also send graduated and withdrawn at least once after the term is over in order support analytics around retention and graduation. Best practice is to complete a one-time send of just students who graduated or withdrew completely from your institution the previous term.
Suggested SIS Tables
Important Information About Importing These Files
Demographics should be imported after Accounts, to ensure that the accounts referenced exist in the repository.
The Demographics importer will add new records and update existing records based on the EffectiveOn date. Please see the Implementing Student Demographics for Insight document for a more in depth discussion of this process.
Products That Use Demographics
|Baseline - Rubrics|