So, I can verify the data for “Old age but no death”. That’s pretty cool. I have an imported tree, and somehow, a lot of people ended up “living” even if they were born in the 1700s. I can mark people in the verification list with a checkbox, but can I add a “death” event to all marked people at once to save work? Mass edit murder? How can I do that?
(Win 11, Gramps 5.1.6)
No. Gramps does not allow dropping an event onto a list of people. You can give a list of people an existing or a new Tag.
Gramps assumes that all people older than 110 years old has died. In Preferences (menu >> Edit >> Preferences, there date settings to set certain limits. One of the limits is Maximum age probably alive: Default: 110. Absent a death event, Gramps uses this setting.
Right. Too bad, but thanks for the clarification. So it’s like every software uses their own way to mark people as deceased, as I have done this elsewhere before exporting my tree, but it’s never becoming part of the GEDCOM obviously.
So I’ll manually add a death event a couple of hundred times, this hopefully saves my dead folks from being resurrected elsewhere again.
May I ask about what purpose the checkboxes in the verification list actually serve? Just a manual reminder?
There is an addon tool that will Calculate Estimated Dates based on dates and expected lifespan information found in people nearby.
(i.e., The child of a parent who died in the 1750s will have been born before that. And if the max lifespans are set to 110 years, then they will have died within that span after the birth.)
It also recognizes information that it creates. So those events can be purged or refined when new data is added.
I am assuming you are referring to the Verify Data tool,
The missing or inexact date option allows the tool to consider Baptism/Christening events when the Birth date is missing or Burial date in place of a Death date.
The invalid date is self explainatory.
Sounds useful. I’ll check it out, thanks!
Note that this is unnecessary for Gramps. (Gramps has a “Probably alive?” determination built-in.) But, as you said, Calculated an Estimated is useful when exporting for use with other tools.
I was thinking it might be possible in the following manner, though I have not yet got it to work. First, make a CSV export of the marked people (using the Export View feature). Then use the same CSV file for import, after changing the death information to something like “Unknown”. I had hoped this would create death events for the people, since the wiki says that “the data can be edited and read back in, thereby updating the database”. But no luck so far.
Another option – create a single death event with a description such as “Presumed to be deceased” (and no date!) and share it with all of those people. You could avoid exporting the event if you like, so that you use it only for your research. There are probably a number of pros and cons that I haven’t thought of. just tossing the idea out there.Maybe the data entry for this approach would be a little faster using drag-and-drop.
I strongly recommend delaying for 5.2 (hopefully, a couple weeks) to do this.
Doug just improved it to to not overwrite ALL names when just the Surname was specified.
With fewer data elements overwritten, it should be better for this task.
(Although SuperTool would be my preference for changes en masse.)
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.