Visitor Aware | Singlewire Software

SourcedIds
Each user (this data comes from the OneRoster /users endpoint) in your SIS data will have a unique SourcedId. This SourcedId is the primary key for each user and is used for updating and deleting the user.

If the same person exists in your SIS multiple times, Visitor Aware will see this as multiple different users. This is because each user has a different SourcedId. This will cause issues downstream because only one profile/user can exist in Visitor Aware.

Below is an example of the same person listed in SIS data multiple times. For best results, this should be cleaned up (NULLs removed, etc.) before sending your data to Visitor Aware.




Student Guardian Relationships
A relationship between a student and a guardian is tied together by an agentSourcedId (the classic primary key/ foreign key relationship).

The student record has a column called "agents." The value in the "agents" column is a comma-separated list of sourcedIds. Each sourcedId belongs to a guardian of the student.

Example Student Record

The inverse is true for the guardian (parent) record. The guardian record has a column called "agents." The value in the "agents" column is a comma-separated list of sourcedIds. Each sourcedId belongs to a student of the guardian.

Role mappings between OneRoster and Visitor Aware

Below is an example of how the roles in OneRoster are mapped to the roles in Visitor Aware.

Role in OneRoster => Role in Visitor Aware

districtadministrator => administrator

systemadministrator => administrator

tenant administrator => administrator

administrator => site administrator

siteadministrator => site administrator

aide => operator

proctor => operator

teacher => teacher

Locations need to be active and be matched to the correct orgSourcedId

Student data is only synced when a Location is active and has been mapped to the matching orgSourcedId.

SIS (OneRoster) Org Data Sample

Example of Visitor Aware Location Mapping

Click here for more information on Location Mapping (see the heading: Mapping Your Data to the Correct Locations)