[LON-CAPA-cvs] cvs: loncom /html/adm/help/tex Creating_Groups.tex /interface loncoursegroups.pm

[raeburn]

raeburn		Fri Aug 18 21:24:12 2006 EDT

  Added files:                 
    /loncom/html/adm/help/tex	Creating_Groups.tex 

  Modified files:              
    /loncom/interface	loncoursegroups.pm 
  Log:
  Documentation for course groups, including creation/modification information.
  
  
Index: loncom/interface/loncoursegroups.pm
diff -u loncom/interface/loncoursegroups.pm:1.60 loncom/interface/loncoursegroups.pm:1.61
--- loncom/interface/loncoursegroups.pm:1.60	Thu Aug 17 19:36:05 2006
+++ loncom/interface/loncoursegroups.pm	Fri Aug 18 21:24:08 2006
@@ -1,6 +1,6 @@
 # The LearningOnline Network with CAPA
 #
-# $Id: loncoursegroups.pm,v 1.60 2006/08/17 23:36:05 raeburn Exp $
+# $Id: loncoursegroups.pm,v 1.61 2006/08/19 01:24:08 raeburn Exp $
 #
 # Copyright Michigan State University Board of Trustees
 #
@@ -891,7 +891,7 @@
                 &Apache::lonhtmlcommon::add_breadcrumb(
                    {text=>"$trail{$action}{$state}"});
                 $r->print(&Apache::lonhtmlcommon::breadcrumbs
-			  ("Groups Manager"));
+			  ("Groups Manager","Creating_Groups"));
                 &display_control($r,$cdom,$cnum,$action,$state,$page,
                        \%sectioncount,$groupname,$description,$functions,
                        \@tools,$toolprivs,$fixedprivs,$startdate,$enddate,

Index: loncom/html/adm/help/tex/Creating_Groups.tex
+++ loncom/html/adm/help/tex/Creating_Groups.tex
\label{Groups}

Groups within LON-CAPA courses support two main modes of use, described
below. When a group is first created, members can be assigned, or
they can be added later. It is also possible to configure a group
so that when a specified \emph{change} in a user's role and/or section
occurs, membership of the group is initiated or terminated for that
user. 


\paragraph{Modes of use: \emph{(a)} Section-like}

Groups can be collections of different users, e.g., for whom common
parameters are to be set, or data for display are to be filtered (e.g.,
CHRT). An example might be the case where a class has multiple sections,
some of which meet on Monday, some on Tuesday etc.. Students from
all Monday sections could be assigned to a group (e.g., named {}``monday'')
and then open date, due date and answer date parameters could be assigned
for the group. In the cascading parameter scheme employed in LON-CAPA,
group settings take precedence over section settings. An individual
student may be a member of more than one group (unlike a section -
where students are restricted to a single section, or no section).
If a particular parameter has been set for an individual student in
a number of groups, the parameter which takes precedence is the one
which is most specific (e.g., a resource-based group setting takes
precedence over a folder-based group setting, which in turn takes
precedence over a general group setting). For this mode of use, there
is no need to select any group tools when creating a group, as described
in (b).


\paragraph{Modes of use: \emph{(b)} Collaborative teams}

Groups can also be teams of users requiring access to collaborative
tools, e.g., to facilitate group project work. To support this mode
of use, a selection of collaborative tools are available for selection
when creating a group. Some or all of the tools selected for the group
can be assigned to group members. Each tool has one or more core privileges.
Most tools also have optional privileges. Tools currently available
are: Group chat, Group discussion boards, Group portfolio, Group mail,
Group roster and a Group homepage. 

When creating a group ... 

The creator defines the set of tools which are to be available in
the group. The group can be configured so all members have access
to this complete set of available tools. Alternatively, different
members can be assigned access to subsets of this complete toolset.

The group can be configured so all members receive identical privileges
for any tools they are assigned. This set of privileges comprises
the core privileges plus the default set of optional privileges. The
default set is specified when the course is created.

Alternatively, individual members can be assigned different privileges
for the particular tools assigned to them. In this case the privileges
will be the core privileges plus any specific optional privileges
granted for the tools assigned to them.

When group members are added automatically as a result of membership
triggered by specified role/section changes, those members receive
access to the complete set of tools available in the group, with the
corresponding core privileges plus default optional privileges. The
group access start and end dates members receive are the defaults
set for the group. If these defaults are changed in a group which
already has members then the start and end times for existing members
remain unchanged. However, existing members can be expired from the
group (if access is active), activated (if access starts in the future),
re-enabled (if access has already ended), and deleted from the group. 

If access to certain tools needs to be added or removed for specific
members, then the group settings for assignment of tools must be set
to \char`\"{}different members have different tools\char`\"{} before
attempting to modify user settings. This may require modifying the
group settings first from the \char`\"{}Modify default group setting\char`\"{}
menu.

The same is true if different privileges are to be assigned to different
members. In this case the \char`\"{}different members have different
privileges\char`\"{} setting must be modified if not already set,
before modifying user settings.

Course Coordinators receive the \char`\"{}Modify/Edit groups\char`\"{}
course-level privilege. This allows them to create and modify groups
in the course, and also to access all group tools available in any
group in the course. 

Instructors receive the \char`\"{}View course groups\char`\"{} course-level
privilege. This allows then to access all group tools available in
any group in the course. This type of access is not currently limited
by section affiliation, although this could be implemented in the
future.