My batch expired today and was pulled before noon. Can we get expire time as well as date?
I am working Irish church records, taking my time and being very careful. I had 45 of about 60 records completed and sat down to finish this afternoon only to discover my batch had already been pulled. Since time of day is critical shouldn't we be given time and date, not just date. Further- the system tracks what I am doing by keystroke, surely it knows how many records are completed... and that I have been making progress on the batch. Can't we get a way to ask for an extension, a prompt to ask if we need an extension, etc. If we don't respond to the prompt the system could then pull the batch with a reasonable assumption of in activity.
Best Answer
-
Hi Douglas
i and others have experienced this too.
You may want to support this suggestion below with your upvote to help get the attention of the development folks and raise the priority of addressing this pretty common issue. Batches expire at Midnight GMT on the Date specified. You’ll need to localize that for your time zone, and maybe out a reminder post-it on your monitor.
1
Answers
-
What was the name of the project?
0 -
I am not connected with FamilySearch
I have read that the expiry time for the batches is related to Greenwich Mean Time, midnight I think, so depending on your time zone, the batches may expire in the morning, but they should expire at a consistent time.
(Edited for typo)
0 -
The system does save your work with in a couple minutes of completing the work, so the indexing you completed was saved by the sytem. When another indexer downloads that batch, they will see what you have already completed. Your work was not lost.
Thank you for the indexing you are doing.
0 -
I was working on County Down Church Records. I understand the work is not lost and now I know it is based on GMT. My question was submitted for the benefit of systems designers/engineers who could refine and improve these interface features.
0
