Re: [Gramps-users] Can XML import gramplet used to ADD data to existing person?

[Jérôme <rom...@ya...>]

> While this is true, I think that it's safe to import XML that has no ID's or
> other references to existing data, like in the example given on the site,
> and then attach the new object an existing one, right? I mean, if the import
> gramplet creates an object with a new ID, and the object can be seen in one
> of the views on the main screen, you can see the new ID, and then create a
> link to that from an existing object.

Take care, IDs are cosmetic into Gramps database!
The real internal ids are not visible via Gramps' user interface.

Yes, there is an id for primary objects, but the 'handle' value is more 
important.

In the past, I made some flat XML tables (fake ids, no handle), then 
after an import according to Gramps XML file format, Gramps has 
generated these handles. ;)

> especially when someone writes a convertor for the certificates that
> we can find on familysearch, genlias, and so forth.

Michiel made something like that, but ... it is experimental.
You can find some urls about this on the wiki: this should be tested 
with caution!

Note, as online web repositories often change their API, I wonder how 
long we will keep active such a convertor...

Just a question: how many web sites provides a good plain text based 
file format on export (or a correct Gedcom support)? No need something 
very complex... as said, comma separated value (csv) sounds designed for 
that! or json, xml if need some validations, etc ...


Jérôme


Le 16/10/2012 01:14, Enno Borgsteede a écrit :
> Hi,
>
>> Importing, in general, should not be used if you have any overlap with
>> existing records. You could end up corrupting your data, or
>> duplicating existing records.
>
> While this is true, I think that it's safe to import XML that has no ID's or
> other references to existing data, like in the example given on the site,
> and then attach the new object an existing one, right? I mean, if the import
> gramplet creates an object with a new ID, and the object can be seen in one
> of the views on the main screen, you can see the new ID, and then create a
> link to that from an existing object.
>
>> On the other hand, the Spreadsheet Import [1] can be used to update
>> existing records. I think that is the only current method.
>
> Right. But when we have a choice between expanding the spreadsheet import to
> add notes, sources, or citations, to a person, I can imagine that XML is
> easier, especially when someone writes a convertor for the certificates that
> we can find on familysearch, genlias, and so forth.
>
> cheers,
>
> Enno
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Gramps-users mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-users
>