Menu
▾
▴
Re: [Bodington-developers] Questionnaire Functionality
|
From: BRIAN C. <bri...@bt...> - 2006-03-04 11:32:43
|
A solution that would mimimise the height of the hackles on the back of the neck of a person such as I would be automated electronic badgering. It's clear that there has to be some sort of deadline, even if it is ultimately related to graduation day, in the same way that you don't get your degree if you haven't paid your library fines. Like Jon, I'd be interested to see the content of these compulsory questionnaires. I'd also like to see someone getting failed on a module or being prevented from proceeding due to failure to submit an answer to questions like, "Did you find the library staff helpful...." A university really only has one sanction - you don't pass - so you've got to watch about making anything compulsory. In the normal course of events the deadline would be a week or so before the meeting of the committee that is charged with monitoring the results. The owner of the questionnaire can get percentage completion figures at any time and even interim results. Meanwhile, one week (or whatever) to the deadline, the software sends out a polite email/sms reminder. This is an automatically generated message blah, blah .. This is a reminder that.... You are also reminded that the completion of this .... is mandatory (pe-tuh!)... 24 hours to the deadline an email with slightly stronger wording is sent out. A record of the emails sent would be kept in a secure place. When the deadline passes, the students lose their rights of anonymity due to the need for sanctions and the potential application of a visual diff on results before and after the deadline - I don't go so far as to suggest that the software should automatically debag someone. Or.... the computer could arrange a confidential meeting between a student who has missed the deadline and a holy person such as a minister, priest, rabbi or immam and the sinner would answer questions verbally. The holy person would then.... No, I think I'm getting a bit fanciful now. If a student hasn't got an email account then TT for him or her. I don't know the provenance of all this, but a pound to a penny I bet it's some quality committee somewhere that can only think of quality assurance in terms of paper trails. What if no-one fills in our questionnaire? Gasp!! What if no-one comes to the party? We'll lose a point in the next QAA inspection. Can't have that - make them compulsory! Petty gauleiters, as Jack Maclean in the Glasgow Herald would say. In this respect, I might be wrong... It might be a Health and Safety issue! In which case I might have to retract all I've said. The students' anonymity about reading a COSHH assessment must be protected at all costs, of course. Or perhaps their dietary requirements at the graduation reception? Brian Selwyn Lloyd <sel...@ph...> wrote: This might be slightly off the wall... So I will keep it simple. calling on experience of a similar scenario where users were required to fill in a form I believe you can keep the anonymous aspect of a mandatory form process and enforce compliance what we did was stop access to a given piece of an application until the mandatory form had been completed, only the user knew if they still had access and soon got access after completing the form required. We explained to the user that they must fill in the form or they could no longer do X I think this maps well to your requirement as you can be granular and choose what they cannot access any further... I think it maps well to a course of modules which need to be done sequentially. Your could make it time and % based, but if it really is mandatory then you can make it so... All the questionaire monitor needs to know at anyoone point is percentages... of course it may become quite embarrasing an apparant if a student cannot continue to do their work. You may want to add some bells and whistles such as informing the student that they must complete the questionaire and while the system knows they haven't done so yet, the other party does not, nevertheless they cannot continue using X until they have completed the questionaire... Well its a fine day today and why I'm looking at this... who knows Have a good weekend Cheers Sel Brian Peter Clark wrote: >> >> >>>One of the main points of knowing who hasn't filled in a Questionnaire is >>> >>> >>so >> >> >>>that they can be targeted for badgering to go away and do so. If you only >>>know who hasn't filled in the Questionnaire after the closing date this >>>destroys the logic of the functionality!!! >>> >>> >>I was a student once and I spit on any help given to a university to >>badger students. A student should have the right not to fill in a >>questionnaire and not to be sought out and badgered for doing so. >>You might even make it clear that an abstention is a tacit >>declaration of contentedness. The course owner can get a >>percentage figure any time but no names, no pack drills, and no >>badgers. >> >>No Brian, you miss the point >> >> > >I don't think I miss the point - the right of a student not to be >badgered. If, indeed, the questionnaire is obligatory, then the >student still has the right not to fill it in and accept the sanctions. > >Now there is another point about who made up the blinkin >regulation in the first place. > >Regards, > >Brian > > >>This functionality is being devised because students HAVE to fill in the >>form in order to comply with regulations. With current functionality Bod >>can't be used. We have other types of Questionnaire which students aren't >>compelled to fill in. >>Paul >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by xPML, a groundbreaking scripting language >>that extends applications into web and mobile media. Attend the live webcast >>and join the prime developer group breaking into this new coding territory! >>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>_______________________________________________ >>Bodington-developers mailing list >>Bod...@li... >>https://lists.sourceforge.net/lists/listinfo/bodington-developers >> >> >> > > > > >------------------------------------------------------- >This SF.Net email is sponsored by xPML, a groundbreaking scripting language >that extends applications into web and mobile media. Attend the live webcast >and join the prime developer group breaking into this new coding territory! >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >_______________________________________________ >Bodington-developers mailing list >Bod...@li... >https://lists.sourceforge.net/lists/listinfo/bodington-developers > > > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bodington-developers mailing list Bod...@li... https://lists.sourceforge.net/lists/listinfo/bodington-developers |
