Friday, April 30, 2010

How Not to Write a Call for Papers

Dr. Jody Byrne has received quite a few calls for papers over the years. One he received recently, however, really caught his attention... for all the wrong reasons.

As Dr. Byrne points out, "Calls for papers are supposed to inspire, encourage and explain. All this one does is bombard you with jargon, vague descriptions and non-explanations and then give you a bit of a headache."

Have you ever received a particularly bad call for papers? What stood out about it? What could have made it better?

Friday, April 23, 2010

Tweet Archive

For anyone who wants to capture and archive tweets from a conference, you might want to check out TweetNotes.

What makes the app so special? For one thing, it's free. It also lets you:

  • Add context by incorporating content, like slides and handouts.
  • Organize multiple sessions under one meeting space.
  • Visualize participants.
  • Embed in blogs, Web sites, etc.
  • Archive activity for future reference.

The developers say they're planning a lot more features, including additional collaboration tools. We're not sure how they plan to monetize it, so it might not be the best option for mission-critical applications, but definitely worth looking into.

Tuesday, March 30, 2010

New Feature: Grouped Checkboxes

Our drag-and-drop form builder now allows multiple checkbox items in a single form element.

Why is this important? Let's say you want to collect A/V requirements from your speakers. Before, you had to create a separate question on the form for each requirement:

Now, you can include all of those checkboxes in one element:

We've also added new requirement options for grouped checkboxes: You can make the checkboxes optional, you can require that at least one box be checked, or you can require all the boxes to be checked.

Monday, March 8, 2010

Usability Enhancements

We've just released two enhancements that make the site a little easier to use...

For call administrators: We've made it easier—and faster—to view submission details from the Submissions page. Previously, when you clicked on a submission's title, you were taken to a new page. Now, the same information is displayed in an overlay.

For authors: We've added a tab to the top of the proposal screens that links to the call's submission instructions. Now you have access to that information throughout the entire submission process. (Previously, the instructions were only displayed when you first created the proposal.)

Let us know what you think!

Thursday, March 4, 2010

New Feature: Late Submissions

ProposalSpace now allows you to accept late submissions for a call without having to change the call's official submission deadline. The new setting (named "Late Submissions") is on the Submission Settings page right below the Submission Deadline field.

If you enter anything other than zero in the field, ProposalSpace will continue to allow submissions for that number of days without altering the official submission deadline. We'll also display a notice to users letting them know that although the submission deadline has passed, late submissions are still being accepted.

Tuesday, March 2, 2010

Introductory Pricing Extended

We've extended our introductory pricing another month!

Just start a call in ProposalSpace before April 1, 2010 and you'll lock in the special pricing of $49.95 to activate the call and $4.50 for every submission. You don't have to activate the call before April 1, you just have to create it by then.

So hurry up and start your calls before this offer ends!

Monday, January 11, 2010

Standardized Guidelines

We recently came across an article by Dr. Stuart J. Salasche in the June, 1997 issue of Dermatologic Surgery in which he suggested eight steps reviewers should take when reviewing journal manuscripts. We've modified them slightly to come up with what we think are valuable guidelines that should be at the core of any review process:

  1. Read the material once through to gain a general familiarity with it.
  2. Identify the author's main objective or hypothesis.
  3. Reread the material as many times as necessary to gain a full understanding of it.
  4. Determine if the main objective was satisfied or the hypothesis proven.
  5. Determine if new or valid information was provided or if older material was successfully assimilated and clarified.
  6. Decide whether the material should be accepted or rejected.
  7. Suggest ways the material could be improved.

Are these guidelines sufficient? Are they too specific? Are they just right? Let us know your thoughts.