Vehicle Database

[Quackdave]

RE: Vehicle Database
I'd actually been thinking of doing something very similar myself! I got myself a web hosting account with MySQL and PHP a few months ago, with exactly that in mind, but haven't got round to doing anything with it yet, except putting a few static fleet lists in place. So, I'd certainly be interested in helping with the programming - as long as it's to be a case of starting from a clean slate rather than working with any sort of pre-written software. I've got a good grounding in database and UI design, SQL, JavaScript and regular expressions from my day job in an IT department; I'm fairly new to PHP but I imagine I'll soon get into it.

Some valid points have been made regarding the differing opinions of those who may edit it. For example, whilst I would agree with Dentonian that things shouldn't be changed based on advance rumours until they have actually happened, I disagree on the other two points : I am far more interested in whether a bus is actually in use, and if so, what depot it is physically operating from, than its status and/or allocation "on paper". A vehicle removed from a list can always be put back in should it be returned to use. (Think Cumfybus, Lewis of Maenclochog, or South Notts of Gotham as examples where a list of vehicles owned is/was far from indicative of the current fleet.) Of course, neither of us is "right" or "wrong" here, it's a case of personal preference, and, whereas a static fleet list must decide upon one approach or the other, a good database can and should enable data to be held in such a way that both viewpoints are supported, and users should be able to choose what statuses to include in a list, and whether to show official or actual allocations, or both.

The idea about allowing moderators to validate entries can be made to work - I believe something similar is in place on the German Wikipedia. Readers can opt to view the latest version, which may include dodgy edits; or the most recent approved version, which has been reviewed by a trusted user. It's not universally popular, as a reviewing backlog can mean that blockages occur when an editor needs to make a change that builds upon one that has not yet been reviewed. The alternative, as used on the English Wikipedia, is to commit all changes immediately but then allow them to be rolled back. This isn't without its drawbacks (good editing can still be at risk of being lost if it's been placed on top of bad and the reverter fails to take it into account) but may be slightly easier to implement.

It might be nice to implement the ability for the system to communicate with other databases, the main ones that spring to mind being DVLA and Bus Lists On The Web.

A final feature suggestion would be something to minimise the hassle caused by marques being changed. For examples, when I'm searching for Darts, I have to remember to select Dennis, TransBus and Alexander Dennis; and when I'm sorting by chassis type, I don't want DAF SB120s at the top of the list and VDL SB120s at the end, with Dennises and Scanias in between. I haven't entirely got it clear in my mind yet how this would work, but I do mean to put more thought into it!