Please excuse the cross-posting.
We are in our second year of using Rubicon Atlas for curriculum mapping,
and I have some questions regarding set-up for those of you using it.
Rubicon allows you to create two types of courses - a general course,
which "belongs" to one teacher, and a collaborative course, to which
multiple teachers can be assigned. It seems to me that from a data
standpoint it makes sense to use collaborative courses across the board
since the course then exists (is an entity, if you will) whether or not
someone is currently assigned to it, while a general course can only exist
as an attribute of a user. Thus, if a teacher leaves, the course must be
transferred to the new teacher as opposed to simply removing one teacher
and adding another.
The main question I have is whether or not a general course that belongs
to a single teacher is the functional equivalent of a collaborative course
with only one teacher assigned to it. Is there any disadvantage to setting
up all courses as collaborative? Can you still generate all the same
reports and do the same analysis? Is there anything I'm missing here?
Thanks in advance for your thoughts and suggestions.
Best regards,
Bill
~~~~~~~~~~~~~~~~~~~~~~~
Bill Knauer
Director of Technology
Packer Collegiate Institute
170 Joralemon Street
Brooklyn, NY 11201
718.250.0273
bknauer@packer.edu
[ For info on ISED-L see http://www.gds.org/ISED-L ]
Submissions to ISED-L are released under a Creative Commons license.
