Open GoogleCodeExporter opened 9 years ago
[deleted comment]
[deleted comment]
We need to discuss the idea of "Publishing" a course. Once it is published, it
is
locked and must be checked-out by an authorized course developer or course
owner or
their designee in order to make a change. The updated course may then be
"checked-
in" and will be usable by faclitators for creating classes. We do not want to
have
a scenario where a developer is working on a live course, making changes that
could
affect an in-progress class. Once a class is in progress, the course cannot be
modified -- the class will run with this course unless major problems exist
with it.
Commercial Document Management systems support this type of publishing, along
with
versioning for changes. We should view publishing as a process (moving the
course
with all media and other externals) to a read-only directory (or the like).
This
will prevent subsequent changes from becoming surprises to the facilitator,
students, and others. We must also allow similar states for a course that will
allow them to be reviewed and changed by others, along with "Beta" courses.
Before
a course is published, we should require approvals from several individuals,
who
have been determined BEFORE the course development begins. These individuals
will
probably include all of the course developers, the responsible curriculum
director,
the irresponsible curriculum director (waldo), the Academic Dean, Provost, etc.
The point is, however, that we must maintain the integrity of our courses.
Original comment by don...@gmail.com
on 27 Feb 2008 at 10:25
Original issue reported on code.google.com by
jlb1...@gmail.com
on 22 Feb 2008 at 1:08