This evening there are two separate sets of WTTs in the Data Bucket, though the second set of links (with “pub” included in the path) do not work.
So, taking the set that does work, mostly carrying the date of 13th January, how does it look?
Not tidy. Not lush. I am afraid the only word I can use is “grim”. Outdated schedules have crept in for an alarmingly large number of routes. List (1) below is where all or most of the current WTTs have been overwritten. List (2) shows those where some (but not mpst) curretn WTTs have been overwritten. List (3) is similar but the wrong version for the right SCN is now present.
I am struggling as to how this can come about and quite how overwriting with test data can be the cause but if that is what you are being told I suppose it must be right.
I can identify dodgy files very quickly after downloading with relatively unsophisticated techniques. The only slightly clever thing I have to do is access the title property (which includes the Service Change Number) of each file and check that the title does not match anything that had previously been loaded. I can see that a check of that nature is not much good if the publication process is not faithfully picking up a new and correctly created set of files.
Oh, and there has been no improvement for the routes for which WTTs are missing altogether.
(1) All (or at any rate most) schedules incorrectly overwritten.
You will note that some of these are serial offenders.
(2) one or two schedules incorrectly overwritten
47 (sFr sMT)
349 (Fr MT)
N36 (sMTNt sMFNt sSuNt)
(3) Wrong version has overwritten later version (for same SCN)
N47 (sFrNt sMTNt)