Home› Groups› Improved Merge Experience

Improved Merge Experience

Join

Birth date inconsistencies

SteveLinke
SteveLinke ✭✭✭
March 10 edited June 4 in Social Groups

This inconsistency appears too frequently. For example, when there are just years, and they are within three years of each other, that is very common if the two PIDs were each made from a different census. Another example is when an estimated year from a census (e.g., 1885) is considered inconsistent with a more precise date from many other sources (e.g., 12 Nov 1884).

0

Comments

  • Gordon Collett
    Gordon Collett ✭✭✭✭✭
    March 10

    Is the inconsistency blocking the merge? There's nothing wrong or particularly annoying with the difference being pointed out, noted, explained, ignored and proceeding with the merge. And it is always good to take a second and make sure there are not other inconsistencies to suggest those to different census records that were used to create the profiles were not actually for two different people.

    0
  • SteveLinke
    SteveLinke ✭✭✭
    March 11

    It is not blocking the merge. It is just requiring manually typing something like: "The birth years vary by only one/two years due to being derived from different censuses, but all other data is consistent." I don't want to have to manually type that dozens of times per day. Now, if one PID had 12 Nov 1884 and the other was 18 Mar 1883, that would be worthy of a manually typed justification.

    0
  • Rhonda Budvarson
    Rhonda Budvarson ✭✭✭✭
    March 12

    Thank you for your feedback, and your patience as we refine this beta project :)

    0
  • Mary Anna Ebert
    Mary Anna Ebert ✭✭✭
    April 9

    @SteveLinke
    What did you like about the old "canned" explanations?

    Do you have any recommendations for new or improved explanations?

    0
  • Rhonda Budvarson
    Rhonda Budvarson ✭✭✭✭
    June 4

    no reply. closing

    0
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories