...
SARS Anywhere Admin is used to create the foundation for a SARS location and the relevant appointments, including:
SARS Admin settings maintained by EDAS:
GRID Settings, such as Time Increment (of appointments), Start Time and Stop Time (this is when do you “turn on and off the lights,” not when you start and stop seeing students)
Schedules Codes, such as Open, Group, Prep, or Staff Meeting
Reason Codes, such as General Advising, Tutoring, or Peer Coaching
Confirmation Settings, such as emails and/or texts for booked, moved or cancelled appointments done by a SARS user in SARS Anywhere.
Excluded Dates, such as US and UA holidays
Additional Information, such as Preferred Names, Preferred Pronouns, College, or Major
Access Codes, such as Scheduler, Advisor, Student Worker, or SARS Admin
SARS Admin settings maintained by the SARS location’s admin:
Short Names, needed by only SARS users who meet with students
User Names, every SARS user needs a User Name
SARS Anywhere is used by the SARS location’s admin and/or, depending on the access granted to users, to configure the schedule for users who meet with students on THE GRID using a Master Schedule with the location’s Schedule Codes.
SARS Messages is configured by a member of the EDAS SARS Support Team and/or the SARS location’s admin to send emails and/or texts to students, including:
Appointment Reminders which can be linked to Schedule Codes.
Reminders for Zoom appointments cannot include the Zoom link; however, it can walk the student through the steps of logging in to eSARS to join the Zoom meeting.
Appointment Missed which is sent when the student’s attendance is “Marked No” in SARS Anywhere
Appointment Follow up which is sent when the student’s attendance is “Marked Yes” in SARS Anywhere. It can include a link to a Qualtrics or other survey.
NOTE: If you are a location’s SARS admin and are unable to login to SARS Messages, please send an email to itsd@ua.edu and cc: gdykeman@ua.edu
TRAK-Admin is configured by a member of the EDAS SARS Support Team and/or the SARS location’s admin to create the interface students see when they enter a building and/or room. The interface is configured as an “application,” which can be, but is not necessarily, synonymous with a SARS location. A kiosk can run only a single TRAK application.
Examples:
If one TRAK kiosk is used by several SARS locations as the entry point for students, the application can have multiple buttons and each button can be linked to a different SARS locations, i.e. Advising, Tutoring, and Coaching.
If a SARS location has multiple physical locations, i.e., on different floors or in different buildings, a TRAK-Admin application can be set up for each physical location; this is helpful if different physical locations offer different services, such as Advising on the 1st floor, and Tutoring and Coaching on the 2nd floor.
NOTE: If you are a location’s SARS admin and are unable to login to TRAK-Admin, please send an email to itsd@ua.edu and cc: gdykeman@ua.edu
TRAK-Enter is the application running on the kiosk tablet, laptop, etc., which allows students to enter their CWID and, depending on the configuration in TRAK-Admin,
check in/out
drop in
eSARS_Config is used to configure the location’s online portal including which Schedule Codes, Reason Codes, etc., the student has the option to choose. It is also where confirmation emails for appointments BOOKED by the student in eSARS is configured. This can be done by your location’s SARS admin or by a member of the EDAS SARS Support Team.
SARS-Zoom API (interface) is used to generate links to Zoom appointments and add them to the SARS appointment in SARS Anywhere. It also used to send the confirmation email to students – and Bcc the SARS user meeting with the student – no matter how the appointment is booked – by the student in eSARS or by a SARS user in SARS Anywhere. It is configured by a member of the EDAS SARS Support Team.
...