How do you do....it? Thread, Shared folder for students and staff - only see/edit your own work? in Technical; Hello, all..
I've had a trawl on t'interweb for this, and not come up with anything.. Apologies in advance if ...
Shared folder for students and staff - only see/edit your own work?
I've had a trawl on t'interweb for this, and not come up with anything.. Apologies in advance if this sounds laughable, but it's not really my "thing"
One of the more common requests we're getting nowadays is for a shared folder for all (eep) students to be able to write to, so that the pupils can save work there for teachers of that dept to look over etc.
What I'm trying to get my head round is this - can I set up the share so that:
PupilA saves work in the share
PupilB saves work in the share
PupilA cannot see PupilB's work or vice-versa
TeacherA can see and EDIT PupilA's work (when PupilA doesn't have it open, obviously)
PupilA can then go back in and see what TeacherA has changed
Does that make sense?
I know with the default share permissions, I can set it so that Pupils and Staff can write to the share, but it's tweaking the NTFS with the above that I'm hiccuping on.
Any NT gurus out there have any advice?
Oh, and the server would initially be a 2003 box but will be 2008 later on.
The way I got around this was to give each student a "homework" drive (a shared folder that is created and mapped on login) and then gave the teacher permission to view the folder that the individual folders are created in, if that makes sense. So, for example, student Holly Tree logs in, a homework folder "TreeH" is created in the folder 2010, and mapped to her Y drive. The teacher logs in, and the folder 2010 is mapped to their Y drive, which has all the students homework folders in.
This is seperate from their My Documents, but students have been taught that if they want to hand in any work, they must copy it into their Homework drive.
Brownie points for the VERY fast response - it's greatly appreciated.
Your suggestion is nearly what I have in place just now.
My current method:
Teacher provides a list of user's names and login IDs.
The shares are created with a quick script which reads in a TAB delimited file of their name and their login ID.. I could have done a read of AD, but I was feeling lazy and it depended on the teachers providing a (correct!!) list of user IDs whereas asking for both means I have a 50/50 chance of finding the correct details
The script creates the folder like:
Pupil I drives
Mark Hamill (HamillM)
Anthony Daniels (DanielsA1)
Harrison Ford (FordH)
Staff see the very top level (Pupil I drives), while pupils see \\server\userid$
That works very nicely here, but one of the other schools has indicated that this method isn't suitable (I refrain from commenting further).
So I'm now looking at this largely theoretical NTFS idea now. Harrumph..
Last edited by gerardsweeney; 10th March 2011 at 04:08 PM.
Reason: Realised your method was slightly different from my current one :)
Then the only way I could see how it might work is to mess around with the CREATOR OWNER permission. So, perhaps, give the Student group Write and Traverse access to the folder, but not read, and the Creator owner Read, write and modify? That way the student can create a file, and thus become the creator owner of said file allowing them to change theirs, but they wouldn't be able to read anybody else's.
Purely theoretical, but it could work. Seems a bit of a phaff though!