User actions: implicit voting mechanism and crowdsourcing

(wip)

entity properties

Here below a list of properties for each node labeled (ent:entity) involved in the voting mechanism

ent.upvote   = [] // list of usernames
ent.downvote = [] // list of usernames
ent.issues   = [] // list of valid issue type

Rules

1. User can up-vote an (ent:entity) only when he/she up-votes a specific (ent:entity)-[:appears_in]->(res:resource) relationship. In this case the (entity) will be up-voted, since we implicitly recognise that "this entity is valid enough".
2. User can down-vote a specific relationship ()-[:appears_in]->() (e.g, "this person is not mentioned in this document").
3. User can add issue on (ent:entity) when the type is not correct (e;g. "this is not a person")
4. User can propose a substitute (alias:entity) for a specific (ent:entity) in a specific context (res:resource): the relationship (ent:entity)-[:appears_in]->(res:resource) will be down-voted, while the (alias:entity)-[:appears_in]->(resource) will be created when needed and up-voted; moreover, the (alias:entity) itself will be up-voted, rule 1 applies.
5. User can add a new entity only if it is attached to a resource: (ent:entity) will be up-voted by default and the (ent:entity)-[:appears_in]->(res:resource) relationship.