Avoiding duplicates Nodes

Clearly, this duplicate issue is rising to the top of the priority list. Certainly in the final submit phase a check could be done to see if there is an exact match in the database, but even the smallest of differences in punctuation, capitalization etc. can lead to duplicates anyway. Do most of your entries have unique identifiers like DOI's or ISBN/ISSN numbers? These are by far the easiest way to detect duplicates.

In theory, if one of the authors adds the publication, it should show up on ALL of the authors profile pages without any further action by anyone (so maybe they should check to see if it's there first :-)

Would it be required to that granular level ...? my concern is with author names....so many types to represent the names...no 2 articles of the author matches the names styles..

If entering these by hand, auto-complete on the author field should help to standardize, and the author merge can help to clean the database if you are certain a number of different formats are actually the same person. In it's current state, Biblio tries to create a unique identifier for each author, this makes it much easier to track down all the publications for a given author. In theory there should only be duplicate author names on the "biblio/authors" page if they ACTUALLY are two different people. If they are the same person, represented in two different formats, then they should be merged together.

All that being said, a check of title, first author, and publication year could (and is actually done, but not used) to weed out potential duplicates before they get saved to the database. I'll do a little more research into this subject and see if I can come up with something useful.

How ? You mean all co-authors are registered and their name is associated with drupal username ?

Oh yes, I forgot that they would have to associate their Drupal UserID with one of the Authors listed in the Biblio author database before that would work.

marking issue closed.
bekasu

Have a look at Biblio Advanced Import. It should be able to avoid duplicates, no matter if the biblio records are imported or added manually.

Interesting, but rather than creating a separate module to do this, would you consider submitting patches for the biblio module?

Also, the 6.x-2.x branch already does a pretty good job of stopping duplicates, the only thing it doesn't currently do is give the option of creating a new revision. Quite frankly, I don't know why I didn't think of that sooner, but it's a good idea.

Cheers,

Ron.

The additional module currently targets biblio 6.x-1.x and I'll complete the required features.

But I'm fine with merging it into 6.x-2.x.

BTW the duplicate detection of the unstable 6.x-2.x did not solve our customers problems. I suggest to not discuss this in the issue queue. I'll send you a mail.

Yes, please do, I appreciate constructive feedback.

Is advanced import now integrated with biblio?
I use the latest d6 biblio module and i dont see the possibility to choose to duplicate, to update or to create a new revision.
And if advanced import is set to duplicate it doesn't work, probably because the rules in biblio module come first.
So, is there a possibility to desactivate the anti-duplication from the biblio module so i can use all advanced import options?
Thanks,
pht3k

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.