SQL Server for Content Censorship

  • Hi Champs,

    We have little strange requirement in a case of SharePoint where backend is SQL.

    Users in social features of SharePoint shout not be able use offensive words in comments, newsfeeds, conversations, reply etc, The system must not allow “offence words”. Somehow it is not possible SharePoint automatically. We can do it only manually through content approval process. But that approach is not practical approach for the larger environment.

    What i was thinking if something can be done from the SQL Side as SharePoint stores Data in SQL. I was thinking something at runtime detection of Offensive words against a Master Table (Offensive word Dictionary) or While user post (Saved) also fine so SQL can compare and if found offensive Data it should tgriger alert for Admin.

    Please champs let me know if this approach is possible some how. Thanks.

    Regards,

    Inder.

  • This can be done,but you need to develop your own code to do this.

    Some of the best online job boards (such as the Totaljobs Group boards) use this type of technique to help automate compliance with anti-discrimination legislation and decency T&Cs. It can be difficult to prevent all violations, and you may want to plan for manual assessment of flagged items to see if they are really violations and to give feedback to the original posters.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • Direct manipulation of the sharepoint database will void your support and may break sharepoint if you're not careful. Any manipulation of the sharepoint database should be done through the sharepoint API (web services afaik)

    Do bear in mind that the flagging you're talking about can, when done without great care, produce very bad results. What happens when someone comments that "Dick needs to go through all that cl***ic code check for consistency in the constituent parts"

    http://thedailywtf.com/Articles/The-Clbuttic-Mistake-.aspx

    http://www.codinghorror.com/blog/2008/10/obscenity-filters-bad-idea-or-incredibly-intercoursing-bad-idea.html

    http://en.wikipedia.org/wiki/Scunthorpe_Problem

    Edit: And it seems that the SSC forums have provided a nice example of stupid content filtering. Classic.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Thanks Gail

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply