Indexing not in the order of the document
Best Answer
-
As long as all the records are indexed, the order doesn't matter in the end because when someone searches for a particular person that's in the document, his search only looks for that one person. The order in which that person was indexed won't matter at all.
1
Answers
-
Thank you - that makes perfect sense!
0 -
Then if I skip a name in the middle and place it at the end of the list, it's okay? I was told we had to do things in order, including columns.
0 -
Indexers should be indexing in the right order. But if a reviewer gets a batch where the indexer didn't, if he corrected it all or sent it back for reindexing, it would take the batch a lot longer to process. There's no reason for that as long as all the records are indexed. As far as putting a skipped name at the end, it's easy enough for the indexer to insert it where it belongs. With your cursor in the record before the skipped one, go to the add records icon and click on After The Current Entry.
0 -
That contradicts indexing columns. Plus, if it does take longer, at least it's being done correctly. Otherwise why have any rules?
1 -
The reason you do it in order is so the reviewer can check it properly. While reviewing I have added in names that appear to have been skipped and then later found them at the end or some other place in the list. Then you need to go back and delete the name you added in.
Doing them in order makes the review go much smoother!
2 -
I agree, I have done the same, I always check the end now before adding :)
0
