Resources Management

Resources can be created through manual entry in Woolf AMS, automatic synchronization with Canvas, or integration via API. The method depends on your LMS and course setup:

• Canvas Integration: Resources created in Canvas (e.g., assignments, quizzes, pages, files) automatically sync with Woolf AMS. For more, see Managing Resources in Canvas.
  
• API-Based Resource Management: Use Woolf’s Airlock API to fetch, submit, and update resources for non-Canvas LMS. See API-Based Resource Management.
• Manual Entry: Resources like meetings, publications, and general materials can be added directly in AMS using the Create Resource option. For detailed instructions, see Resource Submission Process.
  

To ensure resources contribute to compliance, they must be submitted for verification by Woolf’s Academic Team.

• Submission Process: Review resource details, ensure completeness, and submit for verification.
  
  
• Bulk Submission: Submit multiple resources simultaneously to save time.
  
• For detailed instructions, see Resource Submission Process.

• Workloads: Workloads represent the estimated time students need to engage with a resource.
  • Default Workloads: Pre-configured during course setup and applied automatically.
  • Manual Adjustments: Tailor workloads to align with the actual complexity of a resource.
  • For more details, see Workload and Compliance.
• Resource Kinds: Automatically assigned during synchronization but can be manually updated for accuracy.
  • For example, adjust a Publication to a Peer-Reviewed Publication if it meets PRL standards.
  • For guidelines, see Submission Guidelines by Resource Type.

Meetings require separate handling in Woolf AMS. Attendance and recordings must be uploaded manually or via API to reflect compliance metrics.

• Methods: CSV Import or API Automation.
• Student Progress: Only verified meetings with attendance and recordings count toward compliance.
• For detailed instructions, see Managing Meeting Resources.
  

Submitted resources undergo review by Woolf’s Accreditation Team.

• Statuses: Draft → Submitted → Verified (or Rejected). Check, Resource Statuses.
• Corrections: Resources can be resubmitted after addressing rejection reasons.
• For more on verification, see Resource Submission Process.

• Modifying Resources
  • Update resource details, such as workload, kind, or attachments, as needed.
  • Verified resources revert to "Submitted" status if modified and require re-verification.
    
• Archiving Resources
  • Outdated resources can be archived to remove them from active compliance metrics.
  • Impact: Verified resources retain their contribution to progress even after archiving.
    
• For details, see Resources Basics.

Woolf AMS provides tools to monitor compliance through resource statuses and workload counters:

• Resource Statuses: Ensure all required resources are submitted and verified.
• Workload Monitoring: Verify that the course workload meets minimum accreditation requirements.
• For guidance, see Workload and Compliance.

Unverified resources remain inactive and do not contribute to compliance or progress. Once verified, workloads apply retroactively.

Only verified resources retain their compliance impact after archiving. Unverified resources hold no weight.

Meetings must be manually uploaded with attendance and recordings via CSV or API. For more, see Managing Meeting Resources.

Yes, workloads can be customized in AMS to align with the resource’s complexity. See Workload and Compliance.

No. Group assignments are unsupported. Ensure individual submissions are enabled. For more, see Managing Resources in Canvas.