Scoop -- the swiss army chainsaw of content management
Front Page · Everything · News · Code · Help! · Wishlist · Project · Scoop Sites · Dev Notes · Latest CVS changes · Development Activities
The Next Big Thing After Diaries: Reviews Feature Requests
By Eloquence , Section Wishlist []
Posted on Fri Dec 15, 2000 at 12:00:00 PM PST
I have raved and ranted a lot about the importance of ratings in the past. While Scoop already does a good job at implementing ratings in story & comment moderation (in spite of its shortcomings), there's ground it does not cover yet: reviews. I have talked about distributed databases for such purposes, but given that nobody will code a sophisticated one in the near future, implementing reviews in Scoop would already be a great step forward. Read on..

Many big players in the dot-com field by now have realized how useful reviews with ratings can be. Take a look at Amazon's book reviews, or at CNET's software reviews. Given the fact that Scoop is primarily for news & discussions, implementing reviews hasn't been a priority so far, but together with diaries it would certainly add further to the "community" aspect of big sites like K5, and allow smaller ones like infoAnarchy to give users an additional feedback channel.

Here's how it could work. In the list of sections, you could choose criteria for reviews, for example

- usability
- graphics
- sound

Each of these could have a value from 1 to 5, as with the comments. Now in any section that has rating criteria defined, if you post a comment to an article posted in that section, you also get a list of the defined criteria with a dropdown or radio buttons to choose the rating in each category. Scoop would automatically calculate the average of all criteria and print it.

There would be several additional options that the site operator could choose for a section that would be configured as a review section:

  • ( ) request section - ( ) collaborative review - ( ) both
    A section that is classified as "request" doesn't require the submitter to fill in a product/service field on submission. The subject of all replies is empty by default, users enter the name of the product or service they submit here. This type of section is used for asking for a product/service that fills a given need.
    A "collaborative review" section requires the submitter to give a product/service name, which is used as the default subject. This type of section is used for discussions on a given matter, where it is likely that many users can contribute a review.
    "both" is self-explanatory, if the field is left blank on submission, it is considered a request.

    (I think it's better to separate these, to have request-only sections etc.)

  • [ ] Require ratings
    If not checked, a user can also post a comment without giving ratings.
  • [ ] Require comment
    If checked, additional to giving numeric ratings for the individual criteria, you also have to explain your review.
  • [ ] Calculate review's average points and show them as [________]
    (e.g. "Final Score"). This would simply calc the average of an individual review and print it out with the label entered in the textfield.

The practical implementation would be left to the site editors. Normally you would have a section called Collaborative Reviews or something like that where all reviews are stored, instead of having them scattered all over the place. This way, it would be easier to reference them later. In the story body, you would introduce the product, link to the site, give background info etc.; generally the body would be smaller than for most stories.

Here are some practical examples:

  • Joystick101 posts news about a demo download and everyone can give their rating to it.
  • iA has a release announcement for a new version of pronster, and everyone who gives it a try posts a short review. Next release, new ratings. Users can also comment on the product or write-up without giving a review.
  • Babel.org reports about a Jewish conference and those who have attended give it a rating according to its information value, atmosphere etc., others have normal discussion.
  • Kuro5hin could have a section for users to submit web sites that could be commented and reviewed (perhaps replacing the old MLP).
  • Geeky could have reviews of interesting hardware pieces.
  • Mahonri could have a story asking users to submit reviews of their favorite bible translations. ;-)

I don't know how much work it would be, but it would IMHO be the next important thing to add to Scoop after diaries. Then comes the fine-tuning.

< Remove comment moderation from diaries. | Formatting in polls not consistent >

Menu
· create account
· faq
· search
· report bugs
· Scoop Administrators Guide
· Scoop Box Exchange

Login
Make a new account
Username:
Password:

Poll
Good idea?
· basic idea=5, details=5 75%
· basic idea=5, details=1 25%
· basic idea=1, details=1 0%
· basic idea=1, poster=evil 0%

Votes: 4
Results | Other Polls

Related Links
· Scoop
· Kuro5hin
· importance of ratings
· CNET's software reviews
· Joystick10 1
· iA
· pronster
· Babel.org
· Kuro5hin [2]
· Geeky
· Mahonri
· More on Feature Requests
· Also by Eloquence

Story Views
  23 Scoop users have viewed this story.

Display: Sort:
The Next Big Thing After Diaries: Reviews | 1 comment (1 topical, 0 hidden)
I vote yes! (none / 0) (#1)
by Dries on Sat Dec 16, 2000 at 09:14:47 AM PST

I'm not a contributer to Scoop though I do like to follow up on it. The more because I have my own weblog project. I don't want to advertise or whatever but I wonder how hard it is to add and integrate such functionality in Scoop?

Is Scoop originally designed to be easy to extend or is it somewhat monolitic? For the diary system you used a trick even though some others might somewhat consider it a hack - i.e. diaries are just like stories, therefore easily integrated/added. First time I read that, it made my eyebrows frown and left me with a strange feeling: I still don't know whether that is considered good.

Anyway. Can someone easily write and plugin such a review system without having to touch other parts of the code or without a recondite knowledge of Scoop itself?

My own weblog relies on a modular design - I could write such feature in a few hours and have it integrated. In addition, anyone using the code could easily remove or add the review system without having to touch a single line of code. That is, by just removing the module's files the review system will magically dissapear - including all links, administration interface and so on.

-- Dries
-- Dries
drop.org weblog - drupal engine



The Next Big Thing After Diaries: Reviews | 1 comment (1 topical, 0 hidden)
Display: Sort:

Hosted by ScoopHost.com Powered by Scoop
All trademarks and copyrights on this page are owned by their respective companies. Comments are owned by the Poster. The Rest © 1999 The Management

create account | faq | search