reports

[vincent-peugnet]

Report are made to avoid abuse and try to keep a minimum security layer using user self moderation and dedicated moderators.

add the ability to report sharables and interested users to users. (interested users are users that have clicked on interested button on a sharable

This could be an UserClass propriety defining who can or not report. But keep in mind that it's a security tool, so this should not be reserved to only high user classes.

There should be different types of reports adressing to differents users types :

• report

  • the sharable is not available anymore (maybe this could be only when manager don't take responsibility for it) This is send to managers or public in case of no-responsibility for example
  • there's been a problem with the sharable
    • send it directly with managers
    • or send it to moderators, the reports will be analysed and used to block dangerous users or sharables

• [ ] user can create reports on

  • [x] sharable
  • [ ] interest
  • [ ] validation
  • [ ] contact ???

• [x] report right is set in their user class

[vincent-peugnet]

Managers should be able to report a validation they find strange or abusive. Especially if they have checked the responsive checkbox. For example, you're sharing a guitar lesson, an user validate you, but you've never seen her or him... straaannge...

[vincent-peugnet]

Things that can be reported:

• sharable
• validation
• interest
• question
• answer

there could be a parent class report

class Report

id        int
rule      rule_id (int)
comment   text
creation  dateTime
user      user_id (int)

And child classes like ReportSharable

class ReportSharable extends Report

sharable   int

[vincent-peugnet]

Mmmhh, I'm thinking again of how should Reports be stored.

I wanted to to a ReportReport entity allowing moderators to report a report :smile:

But these would need to allow report ReportSharable, ReportInterest, ReportUserProfile.... etc... so I should create a ReportReportSharable !!! That's horrible.

So I'm wondering if, from the begining, I could have done things differently by using a lot of columns that won't be used at the same time.

class Report V2

id         int
rule       rule_id (int)
comment    text
creation   dateTime
user       user_id (int)

sharable   sharable_id (default: NULL)
interest   interest_id (default: NULL)
validation validation_id (default: NULL)

I can manage to only allow one of thoose parameter to be filled. But of course that would create many empty columns.

But I like the idea of each report sharing the same ID count.

[vincent-peugnet]

As said @n-peugnet , it correspond to problems resolved by Doctrine Inheritance.

Maybe the easiest way could be to use the single table inheritance strategy.