Author | Thread |
|
08/06/2010 09:39:31 PM · #1 |
Hi,
I have a dumb question about challenge entries getting DQ'd... In the Industrial II Challenge, I understand why the previous original #4 was DQ'd, but how did two of the DQ's get DQ'd before voting ended and how did original #70 get DQ'd? To clarify my question, did voters spot something questionable and request validation on the one's that were DQ'd? How did those entries get on the SC's radar?
(I guess the original #70 got me curious about how/why SC asked for his original...)
Thanks in advance,
Leo
|
|
|
08/06/2010 10:02:46 PM · #2 |
On every voting page is a link to "click here if you suspect a rules violation" -- you'll be asked to provide a reason for your suspicion and the specific rule violation.
The reason can be for editing outside the applicable rule set or for being taken outside the original dates, or for a TOS violation. Not meeting the challenge topic is NOT grounds for DQ unless listed in a "special rule" (exceedingly rare).
If you suspect illegal editing, click the link and list the reason, then vote as if it is completely legal -- if it is not, it will be discarded, but if it is indeed legal, it will not be penalized for your misunderstanding.
We do not always put a "Validated" notice on the photos** -- if any photo is available for voting, just vote as if it is legal.
Most photos requiring validation are brought to our attention by voting members, but SC members are voting members (and subject to the same validation/DQ procedures) too, and can also initiate a validation request in the same manner as anyone else. The top five finishers are always validated. Some photos can ve validated or disqualified with minimal investigation, while others relatuing to a subjective interpretation can take extensive discussion.
Occasionally one or more photos can be brought to our attemtion long after a challenge has ended. There is no "statute of limitations" on a photo being disqualified. If we find a pattern of deliberate and repeated violations a user can be suspended or permanently banned.
**it's not always helpful ... ;-)  |
|
|
08/06/2010 10:30:23 PM · #3 |
Originally posted by GeneralE: Occasionally one or more photos can be brought to our attemtion long after a challenge has ended. There is no "statute of limitations" on a photo being disqualified. |
Okay, so someone questioned them...
Aight, thanks General.
|
|
|
08/06/2010 11:13:18 PM · #4 |
Hey, I got asked to produce the specs for this piece of art ... so I guess anything is possible.
Ray |
|
|
08/07/2010 09:39:30 AM · #5 |
Originally posted by GeneralE:
Occasionally one or more photos can be brought to our attention long after a challenge has ended. There is no "statute of limitations" on a photo being disqualified. |
I see a discrepancy in this statement and what actually happens in reality. I can specifically recall an instance where I reported a photo that had violated the rules - clearly both in the image and in the photographers description of what they had done during editing and the response I got from SC was "we are not going to go back and DQ an image this late after submission. Especially when it is not a ribbon winner."
Message edited by author 2010-08-07 09:40:11. |
|
|
08/07/2010 10:56:48 AM · #6 |
You're both right. Per the Voting Rules, "You must: submit any disqualification requests as soon as you suspect a rule violation, but no later than seven days after the challenge results are posted." We can't expect people to hold on to their originals forever, so there is a "soft" limit of 1 week after the challenge results are posted. However, in cases of intentional cheating (things like EXIF tampering and ghost accounts), there is no statute of limitations and older entries can be disqualified. |
|
Home -
Challenges -
Community -
League -
Photos -
Cameras -
Lenses -
Learn -
Help -
Terms of Use -
Privacy -
Top ^
DPChallenge, and website content and design, Copyright © 2001-2025 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 08/07/2025 03:43:15 AM EDT.