Review Guidelines

These are the most recent guidelines for the tool reviews which are being commissioned for TAPoR 2. Tool reviews should include:

1. Introduction: The basics about the tool. Identify what the tool is (what does it do? is it online? free?.) Who developed it? Who the intended audience? What it is meant to do?
2. Details: More information about the tool. What does it do in detail? What features? What other tools are similar?
3. Limitations: What doesn't it do. What are the limitations? What bugs are there?
4. Questions: What might others comment on.

Other things to take into account

1. The requirements for use. Is it a download, a plugin, a webapp? Is it free or does it require purchase? Is it open source? Does it require a license? Where can you get it? What are the browser/OS requirements?
2. How quickly can you get the tool up and running? Are there any special requirements, such as creating an account, a lengthy install process, or other setup processes? How much room does the user have to customize elements, append custom code, or otherwise adapt it to their particular needs?
3. Ease of use. Is the interface intuitive? What kind of learning curve can the user expect? Are there any obvious limitations or bugs? Is it a specific-purpose tool, or does it have wider applications? Does it lag under certain circumstances, such as feeding in a large text or multiple texts? Does it demand input in a specific format or can it handle a wide variety?
4. Is this tool recommendable? Does it fit the needs of the stated audience? Are there any unique or particularly outstanding features? Any notable drawbacks? Where can you go for more information about the tool?

-- AmyDyrbye - 21 Sep 2011