Best practice forum (Archived)

F2F Setup - best practice

 
Grant Beevers
F2F Setup - best practice
by Grant Beevers - Sunday, 16 March 2014, 4:39 PM
 

Hi folks,

I am looking at how other organisations setup F2F activities and sessions in Totara. As F2F is an activity, ikt must reside within a course. For a learner to successfully signup for a F2F, they must be enroleld in the courses which contains the F2F activity. Do organisations have one single course where they setup ALL of their F2F sessions, and have all employees enrolled in thhat course via an audience or similar, or do other organisatiosn setup F2F activities and sessions in numerous courses and just ensure that the audience which needs to sign up for that course is enrolled into the course. The latter seems more problematic, especially for those F2F activities which you want the whole company to enrol into.

Ideas? Comments?

Regards

Grant

Christopher Mandel
Re: F2F Setup - best practice
by Christopher Mandel - Wednesday, 19 March 2014, 2:13 PM
 

Hi, 

For each course/subject we set up a course and have a single F2F activity in it which contains available sessions. We actually created a single "template" course with the activity built out, and just restore that saved course as a new course each time we want to build a new course. It has saved us a lot of time and ensures settings and completion criteria are consistent across various courses.  


We have encountered the issue where we want to dedicate a session to a specific team or department, but the other sessions are open to a wider audience. For this scenario we ended up setting the session capacity to 1 and manually enrolling the learners for the session so learners from other departments could not enroll. 

Ability to control audience access on the session level would definitely be a great addition. 

-Chris

Rob Bloor
Re: F2F Setup - best practice
by Rob Bloor - Wednesday, 19 March 2014, 2:21 PM
 

Hi 

Similar to Chris.  However we've set up a custom field for department so we can run reports and break down stats etc.  Also had to lock down the ability to delete a f2f instance (see my post about this).

Rob