Hi
I’m trying to improve the import of gw file from geneweb.
I just began and saw that in geneweb, one can enter an event with alternate date.
For example, this event occurred at data1 or data2.
As far I can see, there’s no equivalent.
Right now, the import just uses the first date and silently discards the second.
I’m wondering if the less worse solution would be to go to a textual date with the two or more dates.
what do u think of?
You might take a layered approach:
1st, you could store the _gwDateList as an Event Attribute… the label indicating that the value contains information in GeneWeb format’s data structure. (The label could be named in another way. It just needs to help you associate the attribute’s value with the date list in the .gw format/tag within the format.)
2nd, individually evaluate the list of .gw dates to find a minimum and maximum to create a ”between <minimum> and <maximum>” date… although a ’between’ is not a great equivalent to the .gw list of dates, it IS parsable with the existing Gramps DateHandlers.
(Such a _gwDateList custom attribute has the potential of writing a .gw file that is symetrical in your export add-on. Although you might want to add a comment to the .gw attribute of the evaluated ”between” date. If unchanged since import, that evaluation can be discarded during export. If changed, you would have to decide what to do.)
Eventually, you might write a DateList Gramps DateHandler & a utility that converts _gwDateList attributes into that newly supported Gramps date format.
Note: GeneWeb appears to have some other idiosyncratic date information in its format.
I wonder if there shouldn’t be a way to compare & contrast research data in Gramps.
I often see conflicting parentage, dates, places in different source citations… particularly in secondary sources.
Perhaps some sort of Python List structure would be doable? Something that correlates the Confidence of the Citation for the evaluation.
The case Eric describes is more precise… only 1 part (the date) has a conflict. That’s as common as the entire Event differing.
The second date could be added as an attribute, so the information is not lost.
I agree with @Mattkmmr, enter any alternate birth dates as a separate event with the Type Alternate Birth. This type does not currently exist, but you can type the entry into the drop-down list.
Gramps will only act on the one main Birth event so use this for your best supported (sourced) information. Not all reports will use the alternate information so these alternate events will only show in reports that will display a list of all of a person’s events.
Have to disagree. This approach arbitrarily assigns greater weight to the first date when that weight doesn’t exist in the original file. (Although that is still better than discarding the 2nd date!)
‘Between’ maintains the uncertainty and equal weight. The GEDCOM import preserves the original context in a Note containing the unparsable data tag. But while the sort-Notes-by-date simulates a ”import failure” log, Notes invite careless editing.
So storing the unmodified & unsupported record in an Attribute offers stable future options should the date handling evolve.
I think that sounds like a good approach for getting the import done, and then later you can move dates to attributes or wherever you like.
I have tried both of the other approaches mentioned (multiple events, attributes) and have not decided which I prefer.
To clarify my previous comment on how I’d handle two or more alternative dates for one event:
I’d record several alternative event dates by creating one event where the event date is a date range which encloses all alternative dates. All alternative dates should be added as attributes and their sources as citations/sources. Maybe a tag “event with alternative dates” would also make sense.
I’d avoid creating several events for alternative dates, because yes for birth events it is obvious that a person was just born once (same for death), but for all other event types it could be either the one event with two alternative dates or two seperate events. It could also happen that you have several events of a certain type where each event has several alternative dates. A complex situation like that could make it impossible to match the correlating alternative dates from different events afterwards.
Thanks for all your answer
but i am in a far more poor context.
Indeed i import geneweb file
then i have an event with two or more alternte date and only one source for the events.
I guess i will go for a textual description.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.