On Mon, 3 Sep 2018 13:54:26 +0100, Martin <
mv...@remove.cam.ac.uk>
wrote:
>
>
>On Mon, 3 Sep 2018, DR de Lacey wrote:
>
>> Could we now turn to other issues in IDOX? I really would like to know
>> what you like and dislike about it -- and any improvements made before
>> SCambs adopts it would also be implemented in the City.
>
>See below for a non-exhaustive list of problems, which make it
>unnecessarily hard to scrutinise applications.
Some of these are criticisms of the planning system itself, rather
than the software.
>Some of these are things that a competent web developer could fix in a few
>days' work fairly easily. In general it feels like IDOX don't care about
>their product, or they are massively understaffed.
One of the problems is that the public website is merely a front-end
to the internal database. That's desirable, for a number of reasons -
it means that the content that the officers see and the public see is
identical, and you never have issues with documents being missing from
one side or the other. But it's also what tends to cause problems with
server capacity.
>2) Critically, the lack of a data feed. This should be an absolute
>requirement for modern local government, and should be part of the
>requirements that South Cambs have for a newly-commissioned system. It
>shouldn't require a project like
>
http://www.planit.org.uk/planarea/Cambridge/
>to fill in the gaps by scraping pages to turn the data into an API that
>projects like Cyclescape can then use.
Realistically, you're not going to get that until the government
mandates it.
>5) The inability for ordinary members of the public to understand what is
>presented. Most of the time, for instance, a "Design and Access Statement"
>is what is most useful to read, but this is hidden amongst 100+ documents
>sometimes. A good, accessible modern approach to displaying planning
>applications would show make things easier to understand.
This is very much an issue with the planning system. As far as the
legality of it, and as far as those who work professionally with the
system are concerned, there is no such thing as a "most useful"
document. Every document is equally important - it wouldn't be on
there if it wasn't. In fact, highlighting certain documents to users
may even be unlawful - the data has to be presented neutrally.
This is, of course, the sort of thing that could be addressed by third
parties if the data was available via an API. A public-friendly
overview of planning applications that summarises it for the
non-technical, but links through to the local authority website for
those who want to take it further, would be beneficial. But, to be
reliable, the data has to be available via an API. So this is maybe
something to take up with your MP.
>8) The search should have search-as-you-type so that people can zoom in on
>the correct address quickly. This would avoid the kind of problem where a
>search for e.g. "102 Mill Road" comes back with results that include "102
>Millington Lane" - autocomplete would get rid of this problem as the user
>would see their intention in the drop-down list as they type.
>
>9) In general, the place search isn't very intelligent. A search with an
>explicit number like "1 York Street" shouldn't include "21 York Street"
>"113 York Street" and many others in it.
The problem is that most users aren't very intelligent, and addresses
are recorded as supplied - they aren't canonicalised to the PAF. So a
lot of times, what people want may well not be what they search for. I
agree that an "exact match" option as well as a default fuzzy match
should be offered, though.
The map view uses OS maps because OS maps are canonical as far as
local government is concerned. It's not as smooth a user experience as
dedicated web maps, such as OSM and Google, but there's not a lot that
the software can do about that.
Again, this is an issue with the planning system, not the software.
Every date is equally important; it's up to the user to find the one
which is relevent to them.
(To answer the question: If you have been directly contacted by the
planning department as you are a neighbour, then the "Neighbour
Consultation Expiry Date" applies. If you have not been directly
contacted, and merely wish to comment as a member of the public, then
the "Standard Consultation Expiry Date" applies).
>14) E-mails in the document list get saved as .eml which I think is an
>Outlook-specific format. I can't read them on my system, except by finding
>the text in a pile of binary characters surrounding it.
Thunderbird opens them as well.
This, again, is more of an issue with the planning system. There's a
general principle (I'm not sure if it's a legal requirement, but it
certainly seems to be near-universal practice) that submitted
docoments are loaded onto the database in the format in which they
were submitted. So you will find Word documents, PDF files, etc. And
emails tend to be loaded as .eml, because that preserves all the
formatting of the original HTML email. The alternative is to save the
email to PDF and then load that onto the system. But that adds an
extra step into the system.
>15) There is no linkage to the meeting where an application is being
>considered. It surely cannot be difficult for a database structure to list
>such an entry. Officer reports are added but not usually agendas/minutes
>of meetings, so finding out what was actually debated on an application
>generally requires some serious google-fu to link them up.
Agendas and minutes directly on the application database wouldn't be
possible, because that adds material which isn't relevent. But a link
to the relevant entry in the meetings database ought to be possible.
Part of the issue, of course, is that they are separate, standalone
systems, and putting a link on the application creates a risk that it
will subsequently rot if the meetings database system ever changes.
Mark