You are not logged in — you will only see demo pages if you click on a button.
| ID | Name | Views | Rating | Last Modified | Created | Type | Published | Description |
|---|
TODO...
CREATE
(1) Create new course (database entry & file system location)
(2) Create new item: standalone | part of a course
READ
(3) List of your courses. Courses are frames containing descriptions, metadata, and items.
Courses are full courses (fuzzy, but a 30sec clip is NOT a course, a 1hr course that
completely covers a larger topic is), or they are courselets. Courselets are small
courses, too small to be called a course (think like this: could it be sold in a box
to a content consumer?), but more than a mere "item". Courses consist of courselets
and items. Courselets are/can be shown "standalone", like courses. Items are never
shown standalone (to end-users). A courselet can be just an "item", e.g. a Flash file,
but unlike an item it also has a course framework so that it can be watched standalone.
(4) List of your items. Items belong to courses or are "standalone". Items in courses as well
as standalone ones can be re-used in other courses, and/or by other users, if the
owner permits it. Items are individual files.
UPDATE
(5) Edit course (database entry, description (HTML) file
(6) Edit item (database entry, file)
- Check:
Keep old versions?
a - owner asks for it?
b - are others (re)using this course/item, and are they asking for it?
DELETE
(7) Delete course (database entry, files)
(8) Delete item (database entry, file)
- Check:
Keep old versions?
a - are others (re)using this course/item? since the user permitted this when
creating the course or item, he cannot simply delete it now. keep for those
already using it, and only keep hidden for anyone not yet using it.
- Keep the course/item ID and ask owner for reason for deletion - keep this in the
records for this ID.