Visitor Aware can consume your OneRoster or direct data using SFTP, with the following restrictions:
- If using a OneRoster connection, Visitor Aware only allows files to be sent via SFTP that contain data that is not part of the OneRoster specification. Specifically:
- Cannot Pickup
- Location Destinations
- Volunteers
- Volunteer Opportunities
- Court Orders
- Employees
- Deactivated Employees
- Bussing Information
- If using an SFTP connection, Visitor Aware will not supplement data from a OneRoster connection, and will only consume files listed on the Import Resources page. If you still need to send OneRoster data, you may do so via SFTP by referencing the OneRoster.zip file, however...
- If sending OneRoster.zip, we do not accept any other student, visitor, or user files as they conflict with the OneRoster data sets.
Why Can't I Use Both?
Due to data override issues between data-sets and formats, we do not support both SFTP and OneRoster API connections concurrently as it applies to any OneRoster compatible data, and introduces a lengthly list of issues and reduces the integrity of your data.
For example
- Consuming a OneRoster API that has students, AND a visitors.csv (or any visitor import template) file that references student relationships and/or can/cannot pickup information results in the following:
- The OneRoster API data set will always take precedence
- All guardians will be flagged as an approved pickup (regardless of what the SFTP file says)
- Any guardian relationships that are present in the OneRoster API but are not present in the SFTP file are removed
- Consuming a users.csv via SFTP, AND a OneRoster API connection that has users present, the following will occur:
- Any user that is present in both the csv, and the OneRoster API will be modified by the data set retrieved most recently
- Any user in the csv that is (for example) an Administrator but is a Teacher in the OneRoster API will end up as a teacher, and will not be able to access administrative functionality within Visitor Aware
- Any deactivated users in the users.csv that are marked as active in the OneRoster API will end up as active users, and vice versa
What if I use both?
Either contact your SIS administrator to properly provision your OneRoster API data sets, or contact your SIS administrator to generate full data sets based on our SFTP import templates.