"Mizter T" wrote in message

On May 16, 11:47 am, "Recliner" wrote:

"Colum Mylod" wrote:

On Fri, 8 May 2009 15:45:12 +0100, "Recliner"
wrote:

[snip]

As a matter of interest, is there anyone whose on-line Oyster
journey history contains no omissions at all?

Mine was pretty good (not noticing omissions) up to March. Delayed
maybe: from yesterday to perhaps 2 weeks delay in showing up. It
turns out that my card's balance is correct, but Bank has indeed
gone missing from the JH.

TFL are missing another trick he there's no point worrying all of
us when a simple professional status web page would suffice. It
would cause fewer calls to their call centre.

I had the opportunity to check my journey history on a ticket machine
yesterday, and as expected, all was correct. More surprisingly, the
on-line history is now also correct. I don't know if that's as a
result of my ticket machine check which perhaps caused some
corrupted data buffer to be re-set, or just that they've fixed the
system for everyone.


The latter. The issue here is not some fundamental problem with the
underlying central Oyster database, but the presentation of journey
history data in the Oyster online account system (i.e. what you see
via your web account). I've no idea on the specifics of how the online
journey history system sources its data from the central Oyster
database (could it happen on the fly? I'm not so sure that's how it
would work), but the problem is some sort of disconnect between the
definitive central Oyster database and the system that prepares the
online journey history - this may have only affected some as opposed
to all the online accounts.

If there was some sort of problem with the central Oyster database
then all head would have broken loose a long time back! The central
Oyster database system basically needs to have quasi-bank like
reliability - it's unlikely something would go wrong with it. This
online journey history problem is all about the mangled presentation
of that data - or more to the point only some of it - as opposed to
the underlying data being mangled.

Yes, I know the underlying system isn't broken, but the Web reporting
had lots of gaps. All of a sudden, it no longer has for me.

I was wondering if this meant that the Web system is now properly hooked
up for everyone, or if my checking on a ticket machine restored the
connection for my account? If that's the case, then anyone else
reporting incorrect Web reporting may have an easy way to fix the
problem -- just check the journey history on a ticket machine. Not only
will this be correct, but it should also reset any Web reporting
problems.