Log of /branches/gage_dev/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
Parent Directory
Revision
6655 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Tue Dec 28 17:49:32 2010 UTC (2 years, 4 months ago) by
gage
File length: 37425 byte(s)
Diff to
previous 6333
changed all occurences of "published" to "visible" and of "unpublished" to "hidden"
also modified database.conf.dist so that visible is aliased to "published".
thus the database reference remains "published" but everything else is changed.
Next project: create an easy automatic upgrade of tables to change field name from
"published" to "visible" and then change back the database.conf.dist
Revision
5029 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Mon Jun 25 12:10:49 2007 UTC (5 years, 10 months ago) by
gage
Original Path:
trunk/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
File length: 36151 byte(s)
Diff to
previous 4842
Changes to make unarchiving possible with a choice names for the unarchived files.
To do: Provide updating of the database. Currently there may be difficulties if the database is upgradedbetween the time the course is archived and the course is unarchived.
The behavior with sql_moodle data schemas has not been tested.
Revision
4539 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Fri Sep 29 19:39:55 2006 UTC (6 years, 7 months ago) by
sh002i
Original Path:
trunk/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
File length: 33697 byte(s)
Diff to
previous 4535
use $db->rename_tables for course renaming, remove addCourseHelper,
deleteCourseHelper, copyCourseDataHelper and associated infrastructure.
still have to do something about archive/unarchive -- they are not only
mysql specific, but they rely on the database being local, on the
default port, and named "webwork". :P
Revision
4535 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Fri Sep 29 16:52:23 2006 UTC (6 years, 7 months ago) by
sh002i
Original Path:
trunk/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
File length: 36332 byte(s)
Diff to
previous 4527
use $db->create_tables and $db->delete_tables, check for dblayout
existence even if we're using the default dblayoutname, make regex and
error message match for course id checking, removal of "sql" specific
information from POD, formatting fixes, additional warnings about bad
course existence checking code.
Revision
4129 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Thu Jun 15 14:48:19 2006 UTC (6 years, 11 months ago) by
gage
Original Path:
trunk/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
File length: 38204 byte(s)
Diff to
previous 4083
Implemented unarchiving function to complement archiving function.
Archive exports the course database to courseName/DATA and then tas and gzips the directory courseName to
courseDirectory/courseName.tar.gz
Unarchive allows one to choose files of the type courseDirectory/courseName.tar.gz and then
ungzip, untar them to courseDirectory/courseName -- the database record in courseName/DATA is
then loaded into the webwork database.
So far there is only minimal error checking about whether all or part of the course exists when unarchiving.
There are not yet features for archiving and then deleting a course -- these two operations have to be done
separately for now.
Revision
4083 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Thu May 18 19:32:41 2006 UTC (7 years ago) by
sh002i
Original Path:
trunk/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
File length: 35227 byte(s)
Diff to
previous 3975
modifications necessary to support moodle tables:
* respect non_native flag in dbLayout
* don't attempt to add users if user table is non_native
* rather than checking for the string "sql_single" in renameCourse and
archiveCourse, and erroring out otherwise, we check to see if there is
a copyCourseDataHelper or archiveCourseHelper implementation
(respectively). new getHelperRef subroutine helps with this.
With these changes, courses with the sql_moodle dbLayout can be created,
deleted, renamed, and archived using the WeBWorK course management
tools.
Revision
3975 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Thu Jan 26 21:45:42 2006 UTC (7 years, 3 months ago) by
sh002i
Original Path:
trunk/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
File length: 34751 byte(s)
Diff to
previous 3973
forward-port from rel-2-2-patches: (make addCourse, deleteCourse more
robust.
- pre-check permissions before trying to mkdir/rmtree
- treat creation errors on directories other than the root as warnings
- treat deletion errors on all directories as warnings
- treat sql_single "drop table" errors as warnings
- supress DBI's error reporting for command-line addcourse/delcourse)
Revision
3892 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Mon Jan 9 23:57:28 2006 UTC (7 years, 4 months ago) by
sh002i
Original Path:
trunk/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
File length: 31119 byte(s)
Diff to
previous 3823
I've modified the renameCourse code to simply issue a warning when a
course directory (other than the course root dir) is not movable. I've
also added error checking for some of the more common reasons for
directories to not be movable, so that the warning message is more
informative.
Resolves bug #943.
Originally committed to branch rel-2-2-dev.
Forward-ported without modification to HEAD.
Revision
3528 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Sun Aug 14 16:52:11 2005 UTC (7 years, 9 months ago) by
gage
Original Path:
trunk/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
File length: 30937 byte(s)
Diff to
previous 3453
Add the beginnings of a facility for archiving a course. This method uses mysqldump
and therefore will work only with a mysql database. Many things are still hardwired
In particular mysqldump is hardwired.
The database name is hardwired to "webwork"
Archiving consists of dumping the tables associated to the course to a file
$courseID/DATA/$courseID_mysql.database (this file can be used
to created a new database for the course. it will not overwrite existing
tables however.)
Then the entire course directory is tarred and gzipped and placed
in the courses directory with the naem $courseID.tar.gz
Currently nothing is deleted from the database and no directories are deleted.
So the implementation is fairly safe, but not yet very useful for course management.
There is not yet a facility for automatically importing the archived course.
Revision
3377 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Thu Jul 14 13:15:27 2005 UTC (7 years, 10 months ago) by
glarose
Original Path:
trunk/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
File length: 26259 byte(s)
Diff to
previous 3059
Preliminary commit of changes to add Gateway module.
This adds to WeBWorK
- the ability to create versioned, timed problem sets ("gateway tests")
for which all problems are displayed on a single page ("versioned"
means that students can get multiple versions of the problem set),
- the ability to create sets that draw problems from groups of
problems, and
- the ability to create sets that require a proctor login to start
and grade.
Sets can be defined as gateway tests or proctored gateway tests from
the ProblemSetDetail page.
Not quite bug-free yet. Known bugs include handling of problem values
on the Student Progress page (I think this may be a problem with
changing from sql database format where all entries were 'text' to
sql_single in ver 2.1, where they are integer), and a division by zero
error on the grades page (which may be the same problem).
Tests with a number of attempts per version greater than one haven't
been carefully tested, nor has scoring of gateway tests.
Revision
3059 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Modified
Tue Dec 21 04:41:03 2004 UTC (8 years, 5 months ago) by
sh002i
Original Path:
trunk/webwork2/lib/WeBWorK/Utils/CourseManagement.pm
File length: 26259 byte(s)
Diff to
previous 2835
Added course renaming to CourseManagement, CourseAdmin.
It works like this:
- move the course directory
- move any course subdirectories that are still at their old locations
(like if they were outside the course directory)
- create a new database using addCourseHelper()
- copy the course data into the new course database using
copyCourseDataHelper() (INSERT INTO $new SELECT * FROM $old)
- delete the old course database using deleteCourseHelper()
TODO:
* write helpers for gdbm and sql layouts
* write command-line script
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
enter a numeric revision.
