Arthur,
That would seem to be sensible especially if I could run a report of
who/what was linked to the "about to be deleted" content.
Caveat: I could easily be totally wrong!
I am thinking of content that exists in an instructor's personal area
(or Course Content) and is linked into several courses. They leave and
in our situation would be disabled after 28 days grace normally. Fine I
still have the content but my understanding is that when the user is
deleted the content is still there and accessible via the link or
searching but I can no longer get to it to move it to a better location.
On a practical level for us it should not be an issue other than
filespace as currently we keep disabled courses and users for 3 years
and in theory a username cannot be reused. But you know how it goes :-(
Peter
-----Original Message-----
Henk,
Possibly I am missing something here but in order to overcome the orphan
files effect can we not simply delete the contents of the CS course and
personal folder before deleteing courses or people.
Can this be automated via a snapshot process?
thanks,
Arthur Loughran
>>> [log in to unmask] 01/02/2006 6:31:23 pm >>>
Hi Peter,
there's a CS mailing list hosted at Princeton university.
More information you can find here: http://kb.princeton.edu/9277
We've disabled the course content feature in CS as well, indeed because
of the poor integration between CS and LS. Once a course has been
removed from LS the according folder in CS isn't visible anymore, but
all content is still on the server.
We have noticed that the same is valid for user content as well: when a
user has been removed from the system, the folder isn't visible anymore,
but it still remains on the server. Be careful for this when you recycle
usernames.
Henk van Rijssen
ROC Midden Nederland
|