Home› Welcome to the FamilySearch Community!› Ask a Question› Get Involved/Indexing

Slow reviewing

Phyllis Waugh
Phyllis Waugh ✭
August 7, 2021 edited August 23, 2024 in Get Involved/Indexing

I am reviewing a batch that has about 1500 names. It is so slow I can't get it done. Please advise.

0

Best Answers

  • John Empoliti
    John Empoliti ✭✭✭✭✭
    August 7, 2021 edited August 7, 2021 Answer ✓

    Hi Phylliss. Please share your batch. But I’m betting that you are working on the Business Directories Project.

    If you’re working in Table Entry Mode, try switching to Form Entry Mode, using the Ruler to keep your place. I would also turn off autocomplete (auto-suggest) - I find that it gets in my way and can be confusing. And recently it has been disfunctional anyway. Also, I like to put the Entry Form on the right side of the image. Reorder the Fields to the following order: Surname, Given Names, Prefix, Spouse’s Given Names, Spouse’s Surname, Spouse’s Prefix, Directory Place, and then Directory Date. This allows me to read across left to right abd review top to bottom. Very comfortable and efficient (for me anyway).

    Time Saver: Determine the Directory Date and Directory Place and put those values into their appropriate Fields in the first Entry (they are often blank as you know). But whatever they are, for each of those two now-correct Fields in that First Entry use the 6th horizontal toolbar icon from the right, the “copy forward to like Fields” tool to propagate those correct two values to those same two Fields in all the rest of the 1500 Entries. If the Indexer made a mistake on either of those Fields in any Entry, it is now corrected. If not, then it won’t be changed. In either case, you may now focus on checking the other Fields and ignore those two because you know that they are correct or corrected. You’ve just saved 25% (2/8) of your review work. Of course, if you need to add an Entry because the Indexer missed a person, you will need to index those two Fields in the inserted new Entry. Good luck

    0
  • Susan Ann Mullen
    Susan Ann Mullen ✭✭✭✭✭
    August 7, 2021 Answer ✓

    When you first open these directory batches you will see a pop up window. In that window it instructs us to return those batches that slow down or freeze our computers. Most are not that large so you will probably be able to review others but probably will be best to return this one for another to review.

    1

Answers

  • CoffeyJo
    CoffeyJo ✭
    August 9, 2021 edited August 9, 2021

    I have done many of these US Directories with a high number of entries both in indexing and reviewing. I have found that working in the "Row Entry" option of Data Entry that the program does not bog down at all. I was frustrated working in Table Entry and Form Entry as the program would bog down horribly as you got further along in the entries.

    image.png


    2
  • John Empoliti
    John Empoliti ✭✭✭✭✭
    August 9, 2021
    https://community.familysearch.org/en/discussion/comment/273999#Comment_273999

    I nominate this answer by @CoffeyJo to be considered an Accepted Answer. I have suggested but never actually tried Row Entry mode as a workaround for the sluggishness issues with this Project. I'm happy to hear that it is so robust. Maybe it is the BEST workaround. I have not experienced any sluggishness in Form Entry mode with this Project, but I don't dispute it.

    Some may feel that it's gotta be Table Mode or nothing, maybe because it is easy to spot duplicate Indexed names in Table Mode. But consider that the System deletes adjacent identical Entries, and the rare non-adjacent duplicate isn't going to do great harm anyway - certainly not as much harm as use of Table Mode is inflicting. Also, consider that Row Entry mode is just Table Entry Mode on a diet, so you have the look and feel of a Table, but without the negative consequences.

    In fact, I suggest that the splash notification/warning shown when an Indexer or Reviewer brings up a City Directories Batch be revised to include the suggestion to try these alternative Data Entry Modes:

    Current Wording: In some cases, images with hundreds of names may cause the indexing program to slow down significantly or freeze. If this happens to you, please close your internet browser and open it again. Return to the My Indexing page and return the batch. You may want to try another project.

    Suggested Wording (or something like this): In some cases, images with hundreds of names may cause the indexing program to slow down significantly or freeze. If this happens to you, please close your internet browser and open it again. Consider utilizing Row Entry Mode as an alternative to Table Entry Mode. It appears not to suffer from the sluggishness problems that affect Table Entry Mode with large numbers of Entries. If this doesn't help, then return to the My Indexing page and return the batch. You may want to try another project.

    0
  • Susan Ann Mullen
    Susan Ann Mullen ✭✭✭✭✭
    August 9, 2021

    John Empoliti, you might put that suggestion in the Ideas section.

    0
  • John Empoliti
    John Empoliti ✭✭✭✭✭
    August 9, 2021 edited August 10, 2021

    Thanks Anne. Post-lunch and I’ve just settled down with my iPad to do exactly that. Done.

    1
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 42.7K Ask a Question
  • 3.3K General Questions
  • 570 FamilySearch Center
  • 6.7K Get Involved/Indexing
  • 640 FamilySearch Account
  • 6.5K Family Tree
  • 5.2K Search
  • 999 Memories
  • 2 Suggest an Idea
  • 473 Other Languages
  • 62 Community News
  • Groups