I manually check for current entries and submissions, so rarely trigger the duplicate block but do still seem to find them by others. Below is an example where the submission was under an artist and work on site yet an editor still made a duplicate entry:
Why didn't the system catch and block this entry?
That submission is less than a year old and a duplicate was added notwithstanding. (I can't see when the duplicate was editor added.) Has the duplicate check been upgraded during that time?
I'm sure the check catches a processed entry, but an unprocessed submission?
(I can't see when the duplicate was editor added.)
Here you go
So on Apr 8, 2022 the system failed to find that the same cover of a work on site and by an artist on site had already been submitted though not processed. The editor also failed to visually check as there aren't and weren't that many covers listed under this artist.
This tells me that the system doesn't check for submissions (only entries) and that there was at least an oversight by the editor by not checking prior to entry. There's not much to do about oversights other than perhaps training if it happens too often, but can the system be upgraded?
I don't see any duplicate performance?
DB "registered" the submission so the duplicate was resolved. The question is how did it occur in the first place.
When you create a new performance, there's no check to see if there's a similar submission.
Okay, that answers the why. Should and can it?
Just clarification, I suspect that we must rely on "manual" checks for new artists and/or works, but this example has both a work and artist on site. Seems like it would check the same as for existing entries.
