Restricted Access

Use

This model tracks the configured swipe stations for Restricted Access scanners.  It is recommended to have a Restriced Access model configured for each location you wish to admin students through.  You can setup multiple swipe stations from each Restricted Access model: e.g. you can setup one for the "Cafeteria" and then have three swipe stations active all using that Restricted Access models simultaneously.

Fields

• Name
• Type of Access
  • Currently this has a single option:
    • Period / Cycle Checker
      • This configured the restricted access station to acces a period and a cycle, and return valid if and only if the student does not have a conflicting class during the period / cycle in question.
      • More are coming soon!
• Generate Log
  • This is a flag, if checked, a log will be autogenerated according to the other settings configured for this model, if false, no log will be generated.
• Log On Action
  • A dropdown choice field that controls when a log is generated.  It has the following options:
    • On Approved Only
    • On Denied Only
    • On Both
• Log Type
  • The type of the generated Saga log, please see the Saga documentation for more information.
• Sub Log Type
  • The sub-type of the generated Saga log, please see the Saga documentation for more information.
• Body
  • The body of the generated log.
• Priority
  • The priority of the generated log, please see the Saga documentation for more information.

Restricted Access Log

Use

This is an internal model used to track swiped at a Restricted Access station -- these are downloadable, please see the Attendance Flows page for more information.

Fields

• Student
• Restricted Access
  • The Restricted Access model that this swipe concerns
• Period
  • The period of the restricted access checker at the time of the swipe
• Cycle
  • The cycle of the restricted access checker at the time of the swipe
• Timestamp
• Action
  • This is one of two values:
    • Admitted
    • Denied Admittance
  • This tracks the action taken by the Restricted Access station

Attendance Object

Use

This model tracks a student-taken attendance object.

Fields

• Student
• Section
  • The course section this attendance concerns
• User
  • The user who took this attendance (if the student took their own attendance, this will match the user referred to by the student field)
• Status
  • One of four options:
    • Unknown
    • Present
    • Tardy
    • Absent
  • These can be configured by time, please consult the Attendance Settings and Permissions for more information.
• School Year / Term
  • All attendance data is localized to a specific year and term, this is the field that stores this information.

Engagement

Use

This model tracks weekly engagement instances.

Fields

• Student
• Section
  • The course section this attendance concerns
• User
  • The user who took this attendance (usually a teacher of the related course section)
• Status
  • One of two options:
    • Engaged
    • Not Engaged
  • These are indicated via a checkbox on the engagement taking page, please consult the Attendance Flows page for more information.
• Year / Week
  • The year and week this attendance concerns -- note since this is weekly, the term can be intuited by the week.