Add text to describe correct behaviour of JULES code access form

[maggiehendry]

jules-support receive many emails reporting that the form didn’t work and then describing what the form is designed to do. This tickets adds a description of the intended behaviour so the applicant knows what to expect to hopefully reduce jules-support admin overheads.

[yaswant]

@maggiehendry I am looking at your changes, and it looks like the form can be tidied up a fair bit. Also I understand that the only way this form submitted is via email. So I've made some changes to make a few things clear (see the screenshot) - if that is acceptable, I can push my changes to your branch for review.

@jennyhickson If the form feed is only inspected by humans will there be any objection if I change the <form enctype="text/plain">?

[maggiehendry]

Thanks for having a look. I'd rather users didn't just send the details in the form as this leads to a lot of copying and pasting. I have an email template that I send to people that are having difficulty so that the info is in the right format for the ticket. This is then one copy & paste directly into the ticket. It also has a statement that they have to complete to say that they agree to the T&Cs. This is required under the current licence. Users think that the string that is created in the email that opens means that something has gone wrong in the process, then send emails to describe what has happened, which is the expected behaviour. This is why I had added what it is supposed to look like so they know what to expect. It does look like a scam or something. Or that is has been hacked... Really it'd be better just to have a completely different form... I have a script that I run on the string that reformats the information into something I can just copy into the MOSRS admin ticket for an account.

[yaswant]

I agree with not offering the duplicate approach, but in the absence of a mail client, how do you propose the user to check the form fields following the post method? In its current form, it expects a mailto protocol handler to proceed with submission.

I am not sure I fully understand the problem. Also I don't know what we do with the email contents. Are they stored in a central database somewhere?