Home› Welcome to the FamilySearch Community!› Suggest an Idea

Useful enhancement to functions involving calendar dates

Call, Jerry Max
Call, Jerry Max ✭
November 24, 2021 in Suggest an Idea

I just finished reviewing a batch of military records in which the date at the top read--

February (hole punch destroyed the day) 1922.

The indexer assumed (probably correctly with these particular records) that the obliterated date was the last day of the month. So far so good. Unfortunately, they listed all the dates as February 31, 1922. 1922 was not a "presidential" year, so the 28th was the last day of February that year. The indexer did excellent work otherwise in the entries; didn't find any other errors. But I suggest it would be a good idea if you added some additional functionality to the program so it won't let indexers enter a nonexistent date. In this case when an indexer entered Feb in the first cell, 31 in the second, and 1922 in the third, they'd get an error message: "Non-valid date" or something like that.

Tagged:
  • New
2
2
Up Down
2 votes

New · Last Updated November 24, 2021

Clear
No Groups Found

Categories

  • 28.5K All Categories
  • 22.9K FamilySearch Help
  • 114 Get Involved
  • 2.6K General Questions
  • 423 FamilySearch Center
  • 432 FamilySearch Account
  • 4.2K Family Tree
  • 3.2K Search
  • 4.5K Indexing
  • 592 Memories
  • 6.1K Temple
  • 309 Other Languages
  • 34 Community News
  • 6.4K Suggest an Idea
  • Groups