Front Rush Import
- 28 Nov 2023
- 9 minute read
- Print
- DarkLight
- PDF
Front Rush Import
- Updated 28 Nov 2023
- 9 minute read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Before getting started, understand how Front Rush information is automatically delivered to each instance of Slate. Front Rush places their files into the /incoming/frontrush directory. Slate automatically monitors this directory and imports any incoming files using the Front Rush Source Format.
What Do You Need To Do?
Before Front Rush data can appear on individual person records, four steps must be taken:
Add a new directory called “frontrush” to the /incoming/ directory on the SFTP site.
Confirm that the field destinations and value mappings that Technolutions has pre-mapped are appropriate.
Customize the import by mapping any additional fields and values that are important.
Once mapping is complete, set the Front Rush Source Format’s Remap Active setting to Active.
Adding the Source Format
The CommonApp file contains the application data for students who have submitted an application to your school.
Select Database on the top navigation bar and select Source Format Library.
Add the Front Rush (Tab) Source Format.
Remapping the File
Make sure a Front Rush file has been loaded into Slate via Upload Dataset. A file must be present in order to allow any remapping.
Select Database on the top navigation bar and select Format Definitions.
Select the Remap link.
All of the Slate destination fields currently mapped for the data points included in the Front Rush file are now visible.
Stage: Fields
The Fields configuration page within Upload Dataset is where fields from the incoming Front Rush data is mapped to indicate where data is to be stored:
Source = Field sample value | Destination = Field mapping in Slate |
|---|---|
Sport 1 Name = Wrestling | Sport > Sport - Sport |
Sport 2 Name = Lacrosse (M) | Sport #2 > Sport - Sport |
Sport 3 Name = Baseball | Sport #3 > Sport - Sport |
Sport 1 ID = 08152017 | Sport > Sport - External ID |
Sport 2 ID = 13456256 | Sport #2 > Sport - External ID |
Sport 3 ID = 342764459 | Sport #3 > Sport - External ID |
PERSON.ID |
|
PERSON.FIRST = Travis | Record > First Name |
PERSON.ALIAS = Trey | Record > Preferred Name |
PERSON.MIDDLE = Alan | Record > Middle Name |
What's in this file? On the left side of the page is the data that was included in the | Where will it live in Slate On the right side of the page are the Slate fields that will eventually contain the source values. Technolutions has pre-mapped many of these destinations already. |
Pre-Mapped Destinations
Technolutions has pre-mapped many of the data points sent by Front Rush. These pre-mapped fields may be edited if business processes require non-standard mappings. The Fields configuration page within Upload Dataset is where fields from the incoming Front Rush data is mapped to indicate where data is to be stored:
Do not map any Front Rush data to application-scoped fields. All data points should be mapped to person-scoped fields or sport-scoped fields.
Important
Do not alter the Front Rush Sport ID destinations! While many of the pre-mapped destinations may be edited, do not edit the Front Rush Sport ID destination. The Front Rush Sport ID is mapped to the External ID in Slate.
Source = Field sample value
Destination = Field mapping in Slate
Sport 1 ID = 08152017
Sport > Sport - External ID
Sport 2 ID = 13456256
Sport #2 ID > Sport - External ID
Sport 3 ID = 342764459
Sport #3 ID > Sport - External ID
These mappings ensure that the Front Rush Source Formats will match with the
correct student records.
Best Practice
Do not map any Front Rush data to application-scoped fields. All data points should be mapped to person-scoped fields or sport-scoped fields.
Make custom Sport-Scoped Fields
Schools are familiar with creating fields that are person-scoped (one field associated with the entire person record) and application-scoped (one field for each application on the person record). When creating a sport-scoped field, there is one field for each sport on the person record.
If custom values that exist per sport are to be mapped, custom sport-scoped fields must be made through Database first. For example, make a sport-scoped field to store archive information sent from Front Rush:
To accomplish this, go to the Fields tool in Database and create fields using the following configurations:
Status: Mark as Active.
Dataset: Leave this setting blank.
Scope: Make certain this field is sport-scoped.
ID: The field ID should be in all lowercase letters and with no spaces.
Name: This will be the display name for this field in Slate.
Value: Set this to store value if the value should be text-based. If using prompt values, then select the corresponding prompt list and change the Value option to Store Prompt ID.
Multiple: Store a single value.
Unique for Merging: Do not make this a unique field.
Once custom sport-scoped fields have been created, they appear under the sport destination when configuring the Front Rush destination fields.
Important
Even if Front Rush sends similar data points for sports 1, 2, and 3 for a record, create only one sport-scoped field for each data value in Slate. Slate differentiates between each sport by using the appropriate group numbers, so the information remains associated with the correct sport.
In the example below, all fields are mapping to the same destination (such as Sport > Sport External ID), but they are using different Group numbers (indicated by the #2 and #3 in the Destination column) to separate each individual sport.
Source = Field sample value | Destination = Field mapping in Slate |
|---|---|
Sport 1 ID = 08152017 | Sport > Sport - External ID |
Sport 2 ID = 13456256 | Sport #2 ID > Sport - External ID |
Sport 3 ID = 342764459 | Sport #3 ID > Sport - External ID |
Stage: Value Mappings
Double-check the value mappings on the Value Mappings tab and configure the mappings for newly-created custom field destinations that correspond to prompt lists. Use the Guess Below option to help with this process.
Source Value > Sport | Destination Value > Sport-Sport |
|---|---|
Baseball |
|
Basketball |
|
Football |
|
Hockey |
|
Wrestling |
|
Append Values
Use the Append Values button (seen above) to add all possible field values to complete the mappings. Slate will de-duplicate the list if the list includes previously added values. Add only one value per line.
To obtain a list of all Front Rush values, contact Front Rush and ask them to send the list of possible values for your school. Any appended values must exactly match the values that Front Rush is including in the file.
Use the same process to append values for other Front Rush fields that are missing values so that all appropriate destinations are set for each possible value.
Sport Names
Sport prompts must be added to Slate if they do not already exist. For these, use the prompt key of "sport" and list the Value setting as the name of the sport.
Sport Ratings
Similarly, Sport Rating prompts may need to be added to Slate so values will appear when setting up mappings. For Sport Rating prompts, use the prompt key of "sport_rating." Ratings can be either numeric (such as 1, 2, and 3) or text (such as Tryout Player, Varsity, and JV).
Once Sport Rating prompts have been built in Slate, map the Front Rush source values to the new Slate values:
Source = Field sample value | Destination = Field mapping in Slate |
|---|---|
Sport 1 Name = Wrestling | Sport > Sport - Sport |
Sport 2 Name = Lacrosse (M) | Sport #2 > Sport - Sport |
Sport 3 Name = Baseball | Sport #3 > Sport - Sport |
Sport 1 ID = 08152017 | Sport > Sport - External ID |
Sport 2 ID = 13456256 | Sport #2 > Sport - External ID |
Sport 3 ID = 342764459 | Sport #3 > Sport - External ID |
PERSON.ID |
|
PERSON.FIRST = Travis | Record > First Name |
PERSON.ALIAS = Trey | Record > Preferred Name |
PERSON.MIDDLE = Alan | Record > Middle Name |
Source Value > Sport Rating | Destination Value > Sport-Sport Rating |
|---|---|
Tryout | Tryout Player |
JV | Junior Varsity |
First Year | 1 |
Varsity | Varsity |
Fourth Year | 4 |
Important
Append values! Are more than the 0-4 sport ratings being used? If yes, append additional values so that these prompts may be mapped. Also, be sure to add those additional values as prompts.
Device Types
Front Rush also includes Facebook and Twitter handles. If bringing that data into Slate, create device type prompt values. To do so, configure these prompts in the following way:
Key | Value | Index Value |
|---|---|---|
device_type | Email Address | |
device_type | Evening Address | business |
device_type | ||
device_type | Mobile Phone | mobile |
device_type | Primary Phone | phone |
device_type |
Important
The device Index Values must use the precise case-sensitive value listed).
If bringing in custom device types (such as Facebook), then all the standard device type prompts must be added (such as email address) as well.
Additionally, if Facebook and Twitter handles are not wanted, remove the current mappings for those items in the Fields Stage previously described.
Configuring Interactions
A number of Front Rush source fields may be brought in as Slate interactions. If Slate interactions are desired, remember these basic interaction mapping rules of thumb:
When mapping to an interaction, something must be mapped to Interaction: Code.
It is best practice to also map an interaction date.
If mapping multiple interactions, use group numbers.
Important
Remember to first create any interaction codes needed in the Activities and Interactions section of the Database.
Pre-Read Requested
Use the following configuration to import Pre-Read Requested data:
Source = Field sample value | Destination = Field mapping in Slate |
|---|---|
Sport Pre-Read Requested = Yes | Interaction > Interaction Code |
Since there is not a date specified for this item, the interaction is imported into Slate using the current date. Therefore, it is a good idea to add the Interaction: Prevent Duplication Static Mapping to the Front Rush mappings to prevent this same interaction from being added multiple times (each time the record is included in the import).
Important
Be sure to select the same group number used when the Pre-Read data was mapped.
Overnight Visit
Use the following configurations to import overnight visit data:
Important
Do not map the first three fields. Map the last two fields to Slate interactions. Remember to assign a group number since this is the second set of interactions being imported.
Day Visit
Use the following configurations to import day visit data:
Important
Do not map the first three fields. Map the last two fields to Slate interactions. Remember to assign a group number since this is the third set of interactions being imported.
Origin Source
The Origin Source field will always be “ATH.” The Activity field drills down further to clarify how the data was originally entered into Front Rush: “By Coach,” “By Form,” or “By Import.” (These values may be added as new athletic interactions in Slate.) Since this data is more detailed, use the following mapping configurations:
Important
Map these source fields to Slate interactions. Remember to assign a group number since this is the fourth set of interactions being imported.
Person Status
The Person Status Front Rush field is pre-mapped to the Person Status destination in Slate. Be sure to configure the proper value mappings for this field. Use the following values:
Other Mappings
Consider mapping the following fields to Slate destinations:
Stage: Static Mappings
We have pre-mapped the Front Rush Source Format to use a number of Static Values. Be sure to review those mappings to ensure that settings are configured as needed.
Reviewing in the Test Environment
After all of your mappings are complete, proceed to the Review Stage. Here any potential warnings about incorrect configurations will appear in the Pre-Flight Checks area.
If the remap has already been activated, revisit the Format Definitions for the Front Rush import and map the additional fields. Then, on the right-side of the page select the Retroactive Refresh link. Select the specific field that should be imported/updated for previously uploaded records and select the source files to be refreshed.
Activating the Remap
When Front Rush mappings are complete, go Database and select Source Formats. Locate the Front Rush item and select Edit. Set the Remap Active setting to Active.
Was this article helpful?
