There is an ERROR in the Batch Retrieval System
"Keep in mind that the due date is midnight Greenwich Mean Time (GMT). It's now 12:27 am GMT and I live in Illinois, which is 5 hours behind, making the due date at 7:00 pm the day before."
This is the official answer on this board and from an email I received today. IT IS INCORRECT! I live in the EST time zone so there is a 5 hour difference, got it. But by whose calculation, does 1500 EST = Midnight GMT??
I have had multiple batches that I was in the middle of working on, pulled back without being able to complete them. I agree midnight GMT is a good deadline, BUT ONLY if it actually is fact and indeed working and it is not! I have asked that the code be checked and fixed but keep getting a message that the data is not lost; yes, I understand that. I also understand all of the hard work I put in, trying to decipher 180+ year old handwriting, just went down the tubes. I just want to see the problem a) acknowledged, and b) fixed. Thanks.
Best Answer
-
Batches can be pulled for other reasons. Instructions need to be clarified, batches need to be pulled/added to the project, fields needed to be added/removed. I've worked on projects where batches were pulled and I simply moved on to other projects. The project admins know what they're doing when they pull batches back.
0
Answers
-
This was my response to a question, and yes, it is correct. We are still in Daylight Saving Time, which puts Eastern Time 4 hours behind GMT. DST does not end until November 6th, will then make it five hours behind. 1500 military time is 3:00 pm. GMT is now 4:20 am, making EDT 12:20 am. Batches are due at midnight GMT, making them due at 8:00 pm EDT the day before. Once batches are pulled on the due date, they go back into circulation for another indexer to work on.
You can find the time conversion here or any other another world clock site.
1 -
But the code that governs when a batch exceeds midnight GMT does NOT work correctly. Somehow, no one seems to comprehend that simple fact.
The batches are NOT being pulled back at midnight GMT! This has happened to me multiple times. I know 1500 is 3pm but no one has shown me how 3pm EST has ever, will ever, be midnight GMT. It can't be done.
Therefore the conversion to GMT is not working correctly and needs to be fixed. It's really that simple.
That said, I appreciate you taking the time to respond. I just wish someone was willing to check and fix the erroneous code.
0