Reviewing Requests
How to evaluate, approve, and manage content requests.
The request queue
New requests appear in the curator dashboard under "Pending Review". These are only visible to the submitter and curators until approved. Aim to review requests within a few days of submission.
What to look for
When reviewing a request, consider:
- Clarity - Is it clear what's being requested? Can you identify the specific book, series, or character?
- Scope - Does it fit within OpenFiction's focus on fictional characters in published books?
- Duplicates - Has this already been requested? Is the content already in the database?
- Can we do it? - Is there enough source material to work from?
Changing a request's status
Approve for voting
Move the request to "Open for Votes". This makes it visible on the public requests page where anyone can vote. The submitter is notified.
Accept
Move the request to "Accepted" when you've decided to add the content. This signals to the community that it's on the roadmap.
Reject
If a request doesn't meet the criteria, reject it with clear feedback. The submitter sees your reason but the request stays private. Common reasons: duplicate, out of scope, insufficient detail.
Other statuses
You can also mark requests as "In Progress" when work begins, "Completed" when the content is live, "Withdrawn" if circumstances change, or "Declined" if you decide not to add content that was previously approved.
Writing feedback
Good feedback is specific and constructive. The submitter might be new to OpenFiction, so explain your reasoning clearly.
- Explain why you're rejecting, not just that you are
- Suggest improvements if the request could be resubmitted
- Link to similar existing content or requests if relevant
- Keep the tone friendly and encouraging
See the full status reference for details on what each status means to users.