Henk,
Thanks for your message. We have a central admin team who control all of our Bb admin processes.
However if we stay with a certain amount of manual admin it is possible that we could nominate course admins in Schools in order to distribute some the admin tasks. In that case your comment highlights the problems to which this could give rise.
However if we go with a Snapshot process all of this will be done centrally.
It strike me though that Bb should consider publishing a list of admin scenarios that would collate the potential problems that have been identified in this thread.
regards,
Arthur
>>> [log in to unmask] 02/02/06 18:59 PM >>>
>Hi Athur,
>
>sure that's possible (although I don't know if you can do it with
>snapshot, we still don't use snapshot).
>But the question is who should do that? You can delete users using
>f.i. a batch file, but these folders should be removed one by one
>and, since they're not directly related to the username on filelevel
>on the server, also in the CS user interface. For as far as I know
>only a system admin is able to see and delete all userfolders, so
>he/she should do the job?
>In our situation I can imagine that it could be done that way,
>because user management (creation of useraccount) is done centrally
>by the system admin as well.
>For courses it might be a different thing. There we have course
>admins with the rights to create and delete courses, but do they (or
>should they) have the right to delete course folders in CS as well?
>
>When it should be possible to do the job with snapshot it would be
>wonderful and we would start using is asap.
>
>Henk
>
>
>Question At 11:11 2-2-2006, you wrote:
>>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
>>
>>
>>
>>
>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Dr. Arthur J. Loughran
>>Senior Lecturer
>>Centre for Learning and Teaching
>>University of Paisley
>>Paisley PA1 2BE
>>tele: +44-(0)141-848-3558
>>fax: +44-(0)141-848-3822
>>email: [log in to unmask]
>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>
>> >>> [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
>>
>>
>> >Hi All,
>> >
>> >Firstly is there a more appropriate place to discuss the blackboard
>> >CMS or as there have been a few threads on it lately is here as good
>> >as anywhere?
>> >
>> >When we had our CMS installed and the training it was advised to
>> >turn off course content mainly because of the orphaning problems.
>> >This seemed a bit cart driving the horse but is what we did as we
>> >could not see a requirement then. I was wondering what others felt,
>> >do you use course content section and if so how?
>> >
>> >I get a lot of feedback from our students who use groups extensively
>> >and because they are often working offsite love the file exchange
>> >but are frustrated by it's flat, chronological structure. I thought
>> >that "course content" folders with course and group level
>> >permissions would be a good way to manage that rather than deeply
>> >nested institutional content and lots of specific permissions.
>> >Before going too far down that road can I ask have others done this
>> >and was it successful?
>> >
>> >Peter
>> >
>> >--
>> >Peter Harrison
>> >Teaching and Learning Systems - Bldg 62
>> >School of Industrial and Manufacturing Science
>> >Cranfield University - Bedford - MK43 0AL
>> >Tel: 01234 75 4097
>> >
>> >This communication is sent in confidence to the named recipient
>> >only. If you are not the named recipient, any use, disclosure or
>> >copying of this communication is prohibited. If you have received
>> >this communication in error, please notify the sender immediately by
>> >telephone or email. The opinions expressed do not necessarily
>> >represent the corporate views of <?XML:NAMESPACE PREFIX = U1
>> >/><?xml:namespace prefix = st1 ns =
>> >"urn:schemas-microsoft-com:office:smarttags" />Cranfield
>> >University. Cranfield University accepts no liability for the
>> >content of this email or the consequences of any actions taken on
>> >the basis of the information provided.<?xml:namespace prefix = o ns
>> >= "urn:schemas-microsoft-com:office:office" />
>> >
>>
>>
>>
>>Legal disclaimer
>>--------------------------
>>
>>The information transmitted is the property of the University of
>>Paisley and is intended only for the person or entity
>>to which it is addressed and may contain confidential and/or
>>privileged material. Statements and opinions expressed in this
>>e-mail may not represent those of the company. Any review,
>>retransmission, dissemination and other use of, or taking
>>of any action in reliance upon, this information by persons or
>>entities other than the intended recipient is prohibited.
>>If you received this in error, please contact the sender
>>immediately and delete the material from any computer.
>>
>>--------------------------
Legal disclaimer
--------------------------
The information transmitted is the property of the University of Paisley and is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged material. Statements and opinions expressed in this
e-mail may not represent those of the company. Any review, retransmission, dissemination and other use of, or taking
of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.
If you received this in error, please contact the sender immediately and delete the material from any computer.
--------------------------
|