Meeting resources in Woolf's Academic Management System (AMS) are live, recorded sessions that play a vital role in tracking student engagement, ensuring compliance, and contributing to course progress.
Below are comprehensive guidelines for creating, managing, and tracking meeting resources in Woolf AMS, along with compliance requirements and best practices.
Understanding Meeting Resources
In Woolf AMS, a meeting is defined as any live session where attendance is possible. Examples include:
-
Lectures: Virtual or hybrid sessions.
-
Instructor-Led Discussions: Formal or informal discussions between students and instructors.
-
Group Check-Ins: Team meetings to discuss project progress.
-
One-on-One Interactions: Personalized student-instructor sessions.
💡 Tip: If a live session is used solely for assignment submission, it should be categorized as an assignment resource, not a meeting resource. This ensures clarity and compliance with academic standards.
Meeting Resources Creation
Meeting resources in Woolf AMS can be created using the following methods:
CSV Import
Use the Import Meeting feature to upload meeting recordings and create meeting resources simultaneously. Include details of the recording in the CSV file, such as resource ID, recording URL, and course ID.
Refer to How to Import Meeting Recordings and Attendance in CSV for step-by-step instructions.
API Automation
Automate the creation of meeting resources and upload recordings using Woolf’s API. This method is ideal for colleges with high volumes of meetings or requiring streamlined operations.
Refer to Woolf’s API Documentation for integration details.
Manual Creation
This method is ideal for colleges with smaller operations or infrequent use cases.
- Navigate to the Resources page in Woolf AMS.
- Create a new resource and select the "Meeting" resource kind.
- Attach the meeting recording as an asset (MP4 format recommended).
- Add details such as resource name, course association, external ID, and description.
LMS Resource Synchronisation
This workflow applies to all LMS platforms:
-
Upload Recordings in Your LMS: Add meeting recordings as resources. For example:
-
Canvas: Use pages or ungraded discussions for recording access.
-
Other LMS Platforms: Use equivalent options, such as assignments or resources.
-
Categorization in Woolf AMS:
-
Woolf AMS initially categorizes these resources as general material.
-
Log in to Woolf AMS, navigate to the resource, and update its kind to "Meeting" for accurate tracking.
This workflow allows colleges to also share recordings within their LMS for asynchronous student engagement while ensuring accurate tracking of meeting activity and contributions to student progress in Woolf AMS.
💡 Note: Meeting resources are processed automatically when a recording in MP4 format is uploaded as a meeting resource asset. Woolf AMS reviews and verifies recordings automatically, eliminating the need for manual resource submission.
Woolf's Compliance Requirements for Meeting Resources
Each course has a predefined number of meetings required as part of its requirements. These requirements are configured during course setup and directly influence the course's total workload.
To be recognized as a valid meeting resource in Woolf AMS, a college must ensure the following:
Recording Requirements
Live session recordings are mandatory for meetings to contribute to course progress and compliance. The duration of each meeting recording is converted into workload hours and contributes to the course’s declared workload. In cases where a recording is unavailable, alternative forms of evidence such as transcripts may be accepted upon consultation with Woolf.
Following the addition of a recording, the update adjusts the activity’s workload and attendance, and counts it towards the student's course progress.
Colleges can upload recordings directly to Woolf AMS or share them via their LMS (e.g., Canvas). Refer to How to Import Meeting Recordings in CSV and Sharing Meeting Recordings with Students for more information.
Key Guidelines:
- Only live session recordings qualify. Pre-recorded lectures or static materials do not count.
- Recordings must be uploaded in MP4 format or as a downloadable URL.
- Multiple recordings for the same meeting are supported but may delay verification.
- Zoom cloud recordings are not supported. Use downloadable links from cloud storage platforms (e.g., Google Drive, AWS) for uploading meeting recordings to Woolf AMS.
Live Attendance Synchronisation
Tracking attendance for live sessions is critical for compliance. Student attendance, once synced with Woolf, generates an activity record. This record holds zero workload and remains pending until a recording is added to the meeting resource. Woolf offers two methods for synchronizing attendance:
-
CSV Import
- Prepare a CSV file with fields like:
-
resource_id (unique identifier).
-
student_id (e.g., Woolf ID, email).
-
timestamp (when the student attended).
- Upload the CSV using the Import Meeting feature. For step-by-step instruction, refer to Import Meeting Attendance in CSV.
-
API Automation
- Automate attendance submission using Woolf’s API for efficient data management and streamlined operations.
- This method ensures accurate timestamps for each student with minimal manual effort.
Live Attendance Tracking Tips:
-
Use a Quiz Resource: Create a quiz to confirm student attendance and understanding. Share the quiz link during the live session to streamline attendance tracking.
-
Verify Engagement: Include optional questions to assess student understanding or participation during the session.
-
Set Deadlines: Assign the quiz to a specific cohort with a submission deadline (e.g., 14 days after the session) to accommodate asynchronous engagement.
💡
Note: Asynchronous consumption (students reviewing recordings later) does not replace live attendance but is tracked as passive activity.
Contact Time
Contact time refers to the hours a student spends in live sessions under the direction and supervision of a verified instructor. These sessions are critical for meeting academic standards and ensuring compliance with Woolf’s accreditation requirements.
-
Compliance Requirements
-
Teacher Presence: For a meeting to count as contact time, an instructor must be present during the session.
-
Teacher ID Submission: When submitting live recording and attendance records via CSV or API, include the teacher's ID. This is important for tracking contact time accurately and will be enforced in future updates.
-
Impact on Learning Hours
- At least 20% of the total learning hours must consist of contact time. Meetings without a teacher still contribute to student progress but are not classified as contact hours.
-
Recording and Verification
- Meeting recordings must be uploaded and verified in Woolf AMS for the contact hours to be reflected in course progress.
- Accurate attendance tracking and teacher ID submission ensure compliance and proper calculation of contact time.
💡
Note:
- Contact time is tracked at the college level to ensure compliance with academic regulations.
- While it is currently optional to submit teacher IDs, it is strongly recommended to prepare for future mandatory requirements.
Managing Asynchronous Engagement
Students unable to attend live sessions can engage asynchronously by reviewing live meeting recordings.
How to Organise Asynchronous Engagement
-
Sharing Recordings in LMS:
-
Canvas Colleges:
- Upload recordings as pages or ungraded discussions for student access.
-
Airlock Colleges (Other LMS Platforms):
- Share recordings as equivalent resources in the LMS (e.g., pages or assignments).
-
Syncing Resources with AMS:
- Update the resource kind in Woolf AMS to "Meeting" to ensure recordings are categorized correctly and tracked.
-
Automatic Tracking:
- Woolf AMS tracks student engagement with recordings as passive consumption activity and logs it under meeting resources.
💡
Key Notes:
- Passive consumption does not replace live attendance but contributes to course progress.
- Sharing options are not limited to Canvas. Any LMS can facilitate asynchronous engagement by following the same process.
FAQs
How often should meetings be submitted?
Colleges can decide their submission cadence (e.g., weekly, bi-weekly, monthly). Timely submission ensures accurate progress tracking and compliance. Learn more about submission guidelines here.
Can asynchronous engagement replace live attendance?
No. Asynchronous engagement is logged as resource consumption and contributes to progress but does not replace live attendance for compliance. For details, see Managing Asynchronous Engagement.
Is contact time mandatory?
While currently optional, submitting teacher IDs for contact time will become mandatory in future updates. Read more about Contact Time requirements.
What if a meeting lacks a recording?
Alternative evidence, such as transcripts, may be accepted upon consultation with Woolf’s support team. See Recording Requirements for more information.
How can colleges using Zoom and Canvas manage live sessions and recordings?
Colleges utilizing Zoom and Canvas LTI integration can manage live sessions and recordings in Canvas. However, these recordings will not be automatically tracked in Woolf AMS unless uploaded and categorized correctly. Learn about Canvas Resource Synchronization.
Is the Canvas calendar linked to Woolf AMS tracking?
No. The Canvas calendar feature can help students manage their schedules but is unrelated to Woolf AMS tracking.
How does Woolf handle breakout room activities in meeting workloads?
Woolf applies a 1.5x multiplier to meeting workloads to account for breakout room activities (30% of a meeting spent in breakout rooms). If the multiplier does not accurately reflect your workload, Woolf will adjust it manually to ensure correctness.
Related Links