I wouldn't really call that common enough to warrant access, and it seems to me that its more a failing in the way that the group work is being taught, or in the way that user areas are set up (why don't they have a general group work area?) than it is an excuse to allow permanent read access to a student's entire user area.When children work on one project in a team, but the child who's saved the work is off. The teacher needs to go into that child's folder to retrieve it.
Editing can also be done just as effectively, and with no trace or auditing. If a teacher had it in for a child, or thought one needed a little boost, what's to stop them? As someone who was a victim of the former at school I am very, very glad that the teacher in question did not have any untraceable way to edit my work.Good example. Didn't think of that one. We call complain about how much printing goes on - office contains useful tools annotations and feedback. Yes, this can be achieved with departmental folders, but really work should be attached to the child.
As for departmental folders, why not flip the perspective. Individual submission folders where a child can save work for review, in their own user area, and with appropriate permissions assigned to the teacher.
So why not just look at the child's screen and insist they show you the work?Also, a teacher might want to quickly see what a child has achieved in a lesson before it's formally submitted for assessment. They may want to check up on a child who was pissing about all lesson or they may want to gaugue the level of achievement so they can plan their next steps in learning. (I do this with my kids' ICT work, sometimes!) With written work they can have a quick flick through the pile of text books but when work is locked in private folders this isn't possible.
How's about, as a compromise:Not too bad, but doesn't really agree with the least privilege principle. Its a start though. I'd prefer for it to be a single folder which the staff member does have access to rather than a single folder that they don't.* Pupils have a folder for personal/out of school work that has restricted access (that covers people's privacy fears.)
* Staff have read access to folders (except their private folder).
* A basic directory structure is created for the child (e.g. subject headings) with read only access to the root of the my docs. Children are taught and expected to save their work correctly.
* Staff can create new files in a folder and edit these - however they can not modify/delete work that the child has created. This would prevent accidential deletion/adjusting coursework fears but would allow the teacher to create a duplicate copy of the work which could be annotated for marking/feedback.
* Staff have folders with shortcuts to pupils work whom they teach. This could be created fairly easily with a script and a exported file from SIMS. This would allow them to more easily access the work of the chidren they teach.
Here each teacher has a "drop in box". All kids can see all the teachers drop in boxes, and have write access but no read or modify rights (its actually less than write access, kids can only paste files into the box). When a kid has finished their work, they save it into their folder, copy it and paste it into the drop in box - they can see the subfolders if a teacher has made folders for different classes tasks. If a kid hasn't submitted their work through the drop in box, bad luck, no-one's going to go looking for it.
Each teacher can see all the other drop in boxes, but only have full access to their own. We have tried to implement a file naming protocol so if a file appears in a wrong box the teacher knows where it should go.
There are currently 1 users browsing this thread. (0 members and 1 guests)