Dealing with profile spam quickly may discourage some repeat offenders. Dealing with it in bulk would seem to be more efficient than handling a just few at a time.
Attached is a mock-up of possible g.d.o. report. There is flexibility for the format. This report would be used by a relatively small number of people (infrastructure, webmasters, and spam fighting deputies). This report is similar to the one requested for d.o. #1513024: Report for review and clean-up of d.o. profiles
In some ways, the g.d.o. report may be more important because:

  1. G.d.o. Does not have a Member Directory (like d.o.'s limited one).
  2. Gaps in the g.d.o. User numbers make it awkward to brute force a review of recently created profiles (in the unlikely event that somebody would be so masochistically inclined).

The mock-up shows a 'block' checkbox - this is not critical to the report, but might be a productivity improvement. The actual implementation of this would need to be defined by somebody with a better understanding of the maintenance processes for d.o. / g.d.o / etc.
Selection should be allowed by profile creation date range. Selection based on contents of a few of the fields would also be useful - several people will share thoughts on this. Let me know if I can clarify, help test, etc. Thanks!

CommentFileSizeAuthor
ReportMockupGDOOnly.pdf49.44 KBdougsap

Comments

sreynen’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
Issue summary: View changes

Something to review after D7 migration.