Hi
I want to suggest, that the current clarification collection will get a specific rejection reason, which we should use. Like this:
That could increase the amount of agreements and let the reviewer pool who read them, get a similar understanding/interpretation.
4 Likes
People need clarifications. People need to understand what Niantic wants in their database. People need to understand what Niantic does not want in their database. People need to understand what rejection reasons should be used for nominations that should be denied.
Maybe when Niantic goes to all ML or in house decisions, we will no longer need clarifications.
Agree, and I have previously suggested the same, but not a clearly as you did.
3 Likes
Oh sorry
I probablly missed this while sleeping.
Everytime we discuss critria, criteria, criteria in >50 comments, I fall in deep sleep
But repeating underlines our similar thinking on this. Let you a over there
i can’t find anything on here if it didn’t just happen to pop up at the top when i happen to check. no need to say sorry for not seeing my earlier buried comment, and i am glad you started a new topic for this!
3 Likes
I think this is an excellent idea that would help streamline the process a bit more and help everyone understand better what to do.
3 Likes