Please don't pull the rug out from under your indexers/reviewers
I found a batch today of a record from UK Middlesex Part B (1500s to 1988). The screen indicated 99 percent of all the batches were already done with 4 - 6 batches left. I picked up one of those remaining batches which was partially indexed. It covered the period October 1678 to March 1679. I found many errors in what was done and added substanial new entries. I completed the batches entries and began a complete review to catch any errors I might have made. I had reviewed some 40 entries of approximately 99 in the batch, when suddenly the screen had a pink warning block that stated that the batch was no longer available. It was pulled back so abruptly, without warning, that I cannot tell you the exact batch number. I had not exceeded, by any stretch, the one week I should have had to complete this. In my estimation, it is unconscionable to do that to any indexer or reviewer. If I can check a batch out, I should be able to finish it, especially when I am processing it in a timely manner. Since I did the batch, I should have the satisfaction of being credited with doing it. The system should enable Family Search to see someone is currently working on a project and not so, may I say, rudely retrieve it.
Answers
-
Attention: @Melissa S Himes & @John Empoliti (FYI - Indexing. Just thought that you may like to 'Comment')
0 -
Once a batch is expired or 'recalled' there is little a reviewer can do. I guess hope someone from the Project Administration will see this report on Community and respond? I don't know if Project Admins just pulled it to finish the last few batches internally - Maybe they were going to do the 20% review since many changes were made? Yes, if allowed to select for review the allotted time should be allowed. Maybe they are under Project time constraints - but I bet they just pulled it to complete internally.
0 -
I don't know about this particular batch, but, I do know that when a project gets down to 98-99% reviewed, the expiration times are shortened. For example, I just pulled up one of the Land Records that is 98% indexed and reviewed and the expiration date is Feb 10th. So I know that 4 days from now, at 7 pm EST this batch will expire, since the batches expire as midnight GMT.
So, when you are working on those projects that are closing, be very aware of the expiration dates.
1 -
I echo @Melissa S Himes 's comment. It can happen for reasons other than expiration - e.g., they pull a project to fix something - but expiration is a common reason. That it appears to have happened on the day you checked out the batch puzzles me.
1 -
I notice the message has been edited. I didn't get the impression that the batch was just downloaded today when I wrote my message. If that is indeed the case, and it wasn't already in the cache, it doesn't make a lot of sense why it would just disappear on the same day. The other weirdness my friends and I experienced in desktop was that at the end of a project there was a loop and the projects kept endlessly going back and forth between the indexing and arbitration. But, I don't know if that would happen in web-indexing. But, there could be quirks.
0 -
Amen to the original post. That happened to me last night. I was working on reviewing a batch in a project that was almost done, and suddenly the batch disappeared and that message that I didn't have rights to open the batch appeared.
Please tell your computer to leave it alone until it is finished.
0
