A typical situation I feel happens from time to time is that a question got some response quickly, and the OP accepted one of these answers. Then a little later, maybe half a day, a new answer emerges, and doesn't get the upvotes it could have gotten if it had hit that limited window of popularity when the post is new or recently edited.
In order to address this, I tried writing an SEDE query to find answers with a low score from high reputation users (with the possibility to limit by tag). This is based on the assumption that those high reputation users most likely write good answers. If answers have a low score, they could be hidden gems.
Latest version of this SEDE-query.
DECLARE @reputationLimit AS INT = ##ReputationLimit:int?5000##;
DECLARE @lowScoreLimit AS INT = ##LowScoreLimit:int?5##;
DECLARE @tag as NVARCHAR(60) = ##Tag:string? ##;
SELECT TOP ##Limit:int?100##
u.Id AS [User Link],
a.Id AS [Post Link],
a.CreationDate,
a.Score,
q.MaxAns,
q.AvgAns,
q.Tags
FROM Posts a
JOIN Users u ON a.OwnerUserId = u.Id
JOIN (
SELECT q.Id, q.Tags, AVG(a.Score) AvgAns, MAX(a.Score) MaxAns
FROM Posts q
JOIN Posts a ON a.ParentId = q.Id
WHERE q.AcceptedAnswerId IS NULL
GROUP BY q.Id, q.Tags
) q
ON a.ParentId = q.Id
WHERE (u.Reputation > @reputationLimit)
AND a.Score <= @lowScoreLimit
-- AND q.MaxAnswerScore = 0
AND (@tag = '' or q.tags like '%'+@tag+'%')
ORDER BY a.CreationDate DESC
Is this a worthwhile approach and query? Do you think it is good trying to find such answers? Do you think the limits are somewhat reasonable?
or q.tags like '%<'+@tag+'>%'
;-) \$\endgroup\$< >
for word boundaries of something similar? \$\endgroup\$<beginner><datetime><cobol>
... (see this temporary query) - Adding the<...>
to the search means that queries forjava
get onlyjava
, and not all thejavascript
too. \$\endgroup\$