Attendance generation
Attendance records are records that indicate an individual's or an asset’s inclusion in a particular session, most typically this is a class session. Whereby for example there might be 20 students, a teacher and a classroom. Each of these attendance records are records in the Salesforce events object. These are the record types per attendance record type:
Students = session student
Staff = session staff
Locations = session location
Resources = session resource.
Notes that both locations and resources are types of assets
In the previous example of 20 students, a staff member and a location, these details are retrieved by looking at the cohort associated with the session. (via the cohort session object).
The 20 students are identified by the fact that they have cohort member records of record type = student linked to the cohort. For each of these we create a session student event record and link it to the respective cohort member and session.
For staff location and resources it depends on whether the timetable is managed internally or not for that particular cohort. If it is managed externally (e.g. via Ed Val Daily), then the Publish daily data and publish daily Delta processes are responsible for associating each of the student and location records with the session by creating the respective session staff and session location event records.
If timetable is not managed externally, then the system looks at the cohort Schedule record associated with the session via the cohort session record and identifies any related cohort schedule connection records. These records identify the staff locations and resources to be associated with the corresponding sessions. Once that has been done, event records of record types, Session staff, session location and session resources will be created as a result.
Attendance generation can be executed either through the generate attendance button on the session window or, more commonly through the nightly generate attendance batch process that typically generates Attendance event records for all sessions for a specific period in advance.
See the Generate attendance batch component documentation for further details.
Once a session’s attendance details have been created they can be maintained to meet a variety of requirements. For example, if a session has a replacement teacher then the edit session window will cause a new Session staff record to be created for the replacing teacher and it will update the corresponding session staff record for the teacher being replaced to reflect this.
So to the add student button on the Mark roll screen will create a session student record for that student in the particular session and automatically mark them as present.