I am currently working on a direct gedcom to xml converter for gramps. I have made it extremely far into the process however, I can not see to get the people view to show the dates event though there are event birth and death dates.
It would seem that the import gets the events and other data its just not displaying the dates in the People Treeview. can someone help me with what needs to be in the XML to show this correctly?
You probably need to set the Event Role to Primary too. (Family events need a Family Role.)
The Birth and Death dates displayed in the view are “fallback event” calculations. (So, if you only had a Burial event with a Primary role, then italicized burial date would be displayed.)
To verify, you could edit the imported event for the Person. (Open the Event editor from the Person View or Person Editor. Opening the editor from an Event view will not give acess to the Roles.) If the Role is Unknown, that is always a problem.
BTW, the Import Text gramplet addon might make a good reference code. It imports most of the basics. (Although it only creates Sources, no Citations.)
Also the current GEDCOM importer plugin leverages Preferences settings for Tagging and Sourcing records during import. However, this unfortunately loses the modification date info for all those records. Which is a definite loss and drawback in merging comparisons. (If you’re importing/merging/syncing/updating from a file exported from the same database with records that are older, it allows your importer to intelligently offer to not revert updated records to old data.)
You are Awesome, that is exactly what it was, except for Unknown mine had birth as the role. Once I switched it to primary it worked!!! Same thing with Death.
Ahh. That should straight-forward to find where your XML writer is setting the Role to the event type.
But… if you are continuing on with the database (instead of tweaking the writer and importing an updated XML into a blank tree), then you will want to do a bit of housekeeping.
That import would have added some custom types to the bottom of the Role pop-up menu selection. And you will want to make certain those nonstandard roles are not in use by any Event. And then flush them out of the list.
The whole point of being able to use custom roles just that, to be able to define real roles to any event participation… to use the actual work title of a person in an work event etc.
It’s actually way over time that these limitations get changes…
True. But the “Primary” (or “Family”) is the person (or 2 persons) having the central Role be implicit in the Event. So that you do not need to explicitly define Roles for each type of Event. Since most Events only have a single Person specified, it cuts the data entry burden by nearly half and eliminates the fussiness of mismatching roles to event.
This allows a lot more flexibility in Gramps to adapt for relationship, pronouns, gender, plurals and tense across various languages.