Someone(s) has been very very busy! What do the columns mean?

And the entire list should actually be deleted. There are no duplicates for the 3 iris that I could see and all the roses are all different plants with the same names.

Some members deserve a huge pat on the back.

I'll refresh the list and see if there are any new ones hanging around.

It seems that a small bug was introduced when I moved the ATP system to a new server a week ago, and that broke the duplicates list. I re-generated it and it's back to its normal size again.

How do I get this off the duplicate list?
They are all different species of sedum, but have the same Cultivar name.
1: Stonecrop (Sedum kamtschaticum 'Variegatum')
2: Japanese Sedum (Sedum makinoi 'Variegatum')
3: Carpet Sedum (Sedum lineare 'Variegatum')

And:
1: Stonecrop Sedum (Sedum erythrostictum 'Mediovariegatum')
2: Stonecrop (Sedum sieboldii 'Mediovariegatum')

I can add an exception to the report, to tell it to not check certain genera. I already do that with Roses and Daylilies - they are excluded from the report. I'll add Sedum as another exception to skip.

Dave, please add Clematis as an exception also. Names are reused indiscriminately in that genus.

Don't exclude the sedum. I have caught a few that were actually duplicate with some incorrect specie names.

Okay, I put Sedum back in and am now excluding Clematis. The report has also been refreshed.

Lynn: this report is just here for our convenience. If some show up as duplicates but you know that they are not dups, just ignore them.

I can do that.

Dave, I'd guess this would be wayyy down your list of priorities BUT, if there was a way to add a comment or something to specific plants on the list we'd know when a plant had been verified as not a duplicate.

That would be real tricky. The report is not a live report but a copy of a report I make locally. For that reason it cannot be manipulated in any way by users on the site. I'd have to think of a better way to make the report, and cause it to occur live. But searching for duplicates in a database of over 500,000 plants takes a lot of CPU resources, which is why I haven't done that yet.

500,000 and counting.