Duplicate entries/registration?!?
Brought to you by:
canajun2eh,
yalnifj
Menu
▾
▴
Hi.
Is there any built in warning system in PGV that warns me if I try to add a already added person? If so I doesn't work for me. I have now exactly same data, same place, same name on 2 persons and now I don't know which one I can delete. One I added 4th feb, and the second on 17th feb, and I didn't get any warnings that the person already existed.
I think this is built in in Swedish PC program Holger and Min Släkt (My Relatives).
//Tobbe
"same name" -- no, nor would we want to. There's a good possibility that two users might have the same name.
"same userid" -- yes. All userids have to be unique. In PGV, capitalization matters. "Userid" is not the same as "USERID". We will never change this.
Why don't you look at the Users list in the User Administration menu? The list tells you when the last access was. Delete the userid that hasn't been used.
But...same name, same birthday, same deathday, same birthplace. Why couldn't I get a message that say "You have one person with the same data already in PGV, please check this entry again" or something like that. I know that it could be same name for several persons, but it's rare that 2 have the same name, and same birthday, deathday, birthplace. Well I might be more careful in the future when I add a new person. I don't want to delete something that shouldn't be deleted.
Thanks
//Tobbe
Sorry, you still won't get any support for this.
I'm registered more than once in my database. This is so that I can test various privilege levels without needing to go into User Management first. Even so, I'd still need 2 userids, one with admin rights and the other not.
I think Tobbe's suggestion for early duplicate checking has some merit. I think Gerry may have mistakenly thought Tobbe was referring to users (and registration etc) rather than INDIs in the GEDCOM.
It is done very well in GDBI, and is one aspect of that programme I miss.
For clarification, I'm referring to PGV checking an entry for a new INDI as I make it, and to SUGGEST existing INDIs who already exist that MIGHT be the same person. GDBI does this with a simple list showing the close match's key data, allowing me to accept one of them or ignore all.
This has been discussed before, and there may well be a very old Feature Request in the system. As I recall the main objection was that it might consume excessive resources, slow the system down, and even be un-workable on large GEDCOMs. This might still be the case, but then we do now have a reasonably well tuned autocomplete function in place for other fields, so perhasp this might be seen as an advanced version of that?
It should, I think, also be limited only to the current GEDCOM file, where a site has more than one, as it is possible to have the same person in more than one tree, if they are separate. "Linked" GEDCOMs however should be treated as if they were one.
Tobbe, for your comment <<I have now exactly same data, same place, same name on 2 persons and now I don't know which one I can delete.>> - have you cinsidered using PGVs merge function to sort these out (On the admin page)?
Exactly kiwi_pgv,
You understand what I'm talking about. I don't mean users I might have on my site. I refering to when I add new INDI (as you call it).
Ok, didn't know there was a merge thing. I try that and get back as soon as I can.
Thanks
//Tobbe
The merge thing seems to do the job really good. Haven't seen any error after I tried it.
Thanks
//Tobbe
The word "registration" in the title of this post is misleading. Generally, in English one speaks of "registration" when dealing with a user database, not a person in a genealogical database.
I'm glad that the confusion was sorted out, and that the merge option corrected your problem.
Tobbe
Now thats sorted - you should raise a Feature Request (under Trackers, menu at the top here) for your duplicate checking idea. No guarantees it will happen, but at least it will be there if someone has the interest to develop the concept.
I thought there might already be one, but can't find it.
It's there already, under Administration "Perform batch updates/edits on your GEDCOM", there is a "Remove duplicate links" and the information about it say "A common gedcom error is to have multiple links to the same record, for example listing the same child more than once in a family record." Hope it is the same as I asked about before, sounds like it anyway.
Thanks
//Tobbe
No, thats not it at all. That is just a correction tool to clean up when the same person (with the same "Ixxx" reference) is accidentally added to a family record.
Your suggestion was for a warning system at the time of data entry.