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

JUNK INDEXER

Options
  • Mute
Terry Stock_1
Terry Stock_1 ✭
September 14, 2021 edited August 20, 2024 in Get Involved/Indexing

The junk indexer is back.

Am reviewing entries for a New Zealand electoral roll. I can't now find how to contact indexing administration to draw attention to the bogus indexer so that something can be done to remove the person from those eligible to index.

So I am venting here. To illustarte what I mean by "junk indexer", the first entry is:

Surname: ghj.ld Fndhrd

Given names: Hgfd Nhl.;df

Sex: M (even that isn't valid!)

So if an administrator is viewing this, it is Auckland East Supplementary Roll page 12 starting with No 12201 surname Cuthbert (can't tell what year)

0

Best Answer

  • genthusiast
    genthusiast ✭✭✭✭✭
    September 14, 2021 edited September 14, 2021 Answer ✓

    @Terry Stock_1 I think you are looking to 'Reindex Batch' with reason User malicious. Here is the previous admin/moderator thread reference

    To do so:

    1. In the batch enable Reindex with reason - under the Help> Labs option
    2. return to the batch and refresh the page
    3. Select Batch> Reindex Batch and then you will see the dialogue you are after. User entered junk data
    ReindexBatchReason.JPG


    0

Answers

  • Terry Stock_1
    Terry Stock_1 ✭
    September 14, 2021

    I'll have to see if I can remember next time. The facility is pretty obscure.

    0
  • Melissa S Himes
    Melissa S Himes ✭✭✭✭✭
    September 14, 2021

    I just want to mention that this might not be malicious, but, it should be reported. There are some individuals who use 3rd party keyboards. This junk data is also a known issue with notebooks. When the language gets inadvertently switched from its original language to a different one, the letters and numbers will be different than they appear on the screen. This was continually happening on a different English transcription site I work with. Once the technicians got in touch with the transcriber, located in Egypt, they were able to work with him to solve the problem. Sometimes it isn't what it appears to be as we found out in that case.

    0
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 43.3K Ask a Question
  • 3.5K General Questions
  • 577 FamilySearch Center
  • 6.8K Get Involved/Indexing
  • 652 FamilySearch Account
  • 6.6K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 480 Other Languages
  • 62 Community News
  • Groups