Reputation Based Permissions

[danielBingham]

As a user I want to gain permissions based on reputation so I can be rewarded for my work.

As a user, I want to receive reviews only from peers with enough reputation in my fields, so I can be sure the right people are reviewing my work.

As a user, I only want my paper voted on by peers with enough reputation in fields, so I can be sure the right people are assessing my work.

Story Background

What is the history or background behind this story? What context the developer researching or implementing this story need?

The plan has always been for users to gain permissions as their reputation increased. So far we haven't implemented this in the alpha, because it makes testing a lot easier. But we'll need to implement it before we go to beta. Initially, it's pretty straight forward. Uses will need a certain amount of reputation to post a review to a draft, vote, or submit a response to a published paper. We'll need to decide where the lines are. And we may need to allow there to be different lines for different fields.

Acceptance Criteria

At what point is this story considered "done"?

• Users can only review a paper if they have X reputation in one or more of the tagged fields.
• Users can only vote on a paper if they have Y reputation in one or more of the tagged fields.
• Users can only respond to a paper if they have Z reputation in one or more of the tagged fields.
• We have determined what X,Y, and Z should be.

Dependencies

What stories does this one depend on? What do we need to do first before we can call this one done?

[danielBingham]

Still need to permissions around publishing. Need to check when a user adds a field to a paper that they have enough reputation to publish in the field. We don't care that all others have enough reputation, only that one of them does. So we'll need to check each author on the paper and check to see if one of them has enough reputation to publish in each of the fields added to the paper.

...Do we care if the submitting author has enough reputation? Probably not as long as one of their coauthors does.

Review, voting, and responding are done on the front end.

Voting and responding are done on the back end.

We need to do the backend for review still.

So total todo list:

• [x] Review backend permisisons checking.
• [ ] Publish frontend permissions checking.
• [ ] Publish backend permissions checking.

[danielBingham]

• [x] Permissions for Voting and Responding need to be refactored to account for the optimizations.