Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display different text depending upon category selected #42

Closed
Deborah-mySoc opened this issue Jan 13, 2011 · 5 comments
Closed

Display different text depending upon category selected #42

Deborah-mySoc opened this issue Jan 13, 2011 · 5 comments

Comments

@Deborah-mySoc
Copy link

So that we can give specific prompts (e.g., if street lighting is picked then it could ask the user to find the light number) rather than generic hints.

Related to this: add in categories for reports which we DON'T want (e.g. noise, ASB, speeding, bins, etc.) and filter the user elsewhere if they are selected.

@MyfanwyNixon
Copy link
Member

+1 from a county council [email 14.1.13]:

The column number is not a mandatory piece of information, but it does pinpoint any faults down to individual assets and we will always ask customers if they have this information available whether they are calling us or reporting issues via our website. I would ask that you include this information on your own site but make it non mandatory.

@andrewblack
Copy link
Collaborator

I have been looking at this issue with Dave and Louise.

@davewhiteland
Copy link
Contributor

Just to clarify one reason why this issue isn't simply a matter of adding a text for "Potholes" -- FMS doesn't have a 'categories' table; that is, 'categories' are not normalised across the whole installation. Instead, categories available for selection are really the category fields of those contacts that are available at this (point) location. There is no requirement for those to be consistent across bodies (and in the UK, they are not; it's not something we could impose on all councils anyway even if we wanted to).

@MyfanwyNixon
Copy link
Member

Feedback from a user (related):

Taking http://www.fixmystreet.com/report/417879 as an example, nearly every pothole report simply gives a subjective judgement of "dangerous" and may list a threat to wheel rims. Often, like this one, they describe a general problem, not a specifically identifiable pothole.

 My guess is that councils give very low priority to such reports, as they are subjective, and probably describe nearly every road in the country, but will act if they are told about specific potholes which meet their intervention criteria (typically 40mm deep and 250mm or 1 foot across, giving priority to one that exceed this size).

 Their own forms, the FixIt one, and CTC one will typically try  to extract this information.

 Whilst it may be a policy decision of yours to only take free text input, to avoid scaring people off, I think some
 additional guidance notes really need to be displayed when  someone tries to report a pothole.

 Maybe: "Reports of potholes through this site work best if you
 identify individual pot holes, rather than a general problem.
 Councils decide whether to repair and how quickly to repair,
 based on the size and depth of the pothole, rather than on
 subjective judgements about the risk, so numbers are more
 important than whether or not you think the pothole is
 dangerous."

@dracos
Copy link
Member

dracos commented Aug 18, 2020

The admin interface lets you add extra notices per category which are shown, and disable form per category, so I think this can be considered done in the general case.

@dracos dracos closed this as completed Aug 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

5 participants