Attaching Find A Grave Index Record No Longer Populates the Burial Field?
Starting about two days ago, when I attach a Find A Grave Index record to a FamilySearch record, FS no longer populates the Date and Place of Burial in the Burial field. In fact, it no longer even displays those fields in the "Attach Historical Records to Family Tree" screen. What is wrong? (I did clear my cache, just to make sure that wasn't the cause, but it continues to happen.) Here's an example.
The Burial field is blank:
I select the record to attach. The Date and Place of Burial are present:
I click on "Attach to Family Tree", and the "Attach Historical Record to Family Tree" screen appears. You can see that the Date and Place of Burial are absent in the left column, where they normally would appear.
I click on Attach. The number of sources has incremented by 1 and the Latest Changes shows Source Attached, but the Burial field in the FS record is still blank.
Answers
-
Thank you for taking the time to report this issue. It is a wide-spread problem that has now been reported to the engineers. We hope for a solution soon.
Take care.
0 -
If I may add - the date of burial is not present in the Findagrave record. The date of death is present, but not the date of burial.
In the past, FamilySearch autopopulated the date of burial field with the same year as the date of death. That's not always the case. For example, my father's ashes were buried more than 4 years after the date of death and cremation. Or, someone who died at the end of December likely was not buried until early January of the following year.
Better, in my opinion, to leave the year field blank than to autofill with something that is, at best, an approximation and may be very wrong.
1 -
Thank you, Aine. My mistake. You're right, the date of burial field is almost never populated. (That has always bugged me, as I always have to go back and manually enter the YEAR of burial in both the Burial date field AND in the date field of the source on the Sources screen, so the sources will correctly sort in chronological order.) But the place of burial was always populated, and it is not working now. And I think this new defect is related to the other defect I reported, which is that attaching Census records no longer creates a new Residence field in the Other Information section, with the Census year and the residence location.
BTW, as long as we're talking about it, the place of burial only used to populate the city/township, county and state (for U.S. burials). It never populated the cemetery name. I wish it would, because that information IS on the Find A Grave record, and that would be a helpful enhancement. I always manually copy-and-paste it in when I attach the record.
0 -
Has anyone had an opportunity to test out what collections or types of records this problem affects? I ask because I've searched my relations high and low and haven't found a record that doesn't offer to transfer events -- but the part of the world they lived in doesn't have census records available as a genealogical source, and the few Find A Grave records I found didn't do (or not do) anything that I found exceptional or noticeable.
The church indexes continue to offer to add a baptism, like always. (I don't take them up on it, because Source Linker sticks them in the wrong place, as a custom event under Other, instead of under Christening where they belong -- and where they almost always already exist.)
The civil registers continue to sometimes offer to add a marriage or death, depending on how that particular part of that indexing project was set up. (Sometimes they offer a "registration" event instead; I don't take them up on those.)
I think the most likely culprit is a change in labeling somewhere in the database, which is causing the ever-literal-minded Source Linker to no longer offer events for the affected collections.
0 -
Julia - I know of no other source type which had this Source Linker problem, other than U.S. Census records and U.S. Find A Grave records. However I am happy to report that the problem (which I reported last week) are now fixed as of yesterday, for both Census and Find a Grave records.
0 -
I've had some New Jersey births that did not capture the place of birth earlier this week. I haven't been active today.
0
