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

Duplicate Image, except for death month?

PatrickCox6
PatrickCox6 ✭✭
March 14, 2022 edited August 16, 2024 in Get Involved/Indexing

Hi, I'm indexing Sierra Leone—Birth and Death Registrations, 1858–2016 [Part D][M3NJ-Y7L] and the first 2 images are identical, except for the death month. Do I just index this once or do 2 entries? Thanks!

https://www.familysearch.org/indexing/batch/f2237656-ba12-4303-887c-d988f422cde0

0

Best Answer

  • genthusiast
    genthusiast ✭✭✭✭✭
    March 14, 2022 Answer ✓

    You are correct. The images are largely duplicates - but because the month is different I would probably index both (that makes it a separate death record rather than a strict duplicate). You will probably get other opinions.

    2

Answers

  • PatrickCox6
    PatrickCox6 ✭✭
    March 14, 2022

    Thanks @genthusiast for you speedy response! I thought there'd be no harm in indexing both. Cheers!

    1
  • Ksalers
    Ksalers ✭✭✭
    March 14, 2022

    I agree with gnethusiast. Definitely index both.

    0
  • barbaragailsmith1
    barbaragailsmith1 ✭✭✭✭✭
    March 14, 2022

    A Duplicate Image would be one that's simply another photograph of the same document in a batch. So if there are any differences, it's not a Duplicate Image. https://www.familysearch.org/en/help/helpcenter/article/how-do-i-index-duplicate-images

    1
  • PatrickCox6
    PatrickCox6 ✭✭
    March 14, 2022

    Thanks so much for your comments. Yes, there are 2 death certificates for the same person but dates of death are a month apart, so I'll index both. Not sure how that would have happened! 😎

    0
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 42.9K Ask a Question
  • 3.4K General Questions
  • 571 FamilySearch Center
  • 6.8K Get Involved/Indexing
  • 644 FamilySearch Account
  • 6.5K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 476 Other Languages
  • 62 Community News
  • Groups