Sorry Jim 
I guess the first thing you’re going to need is a Rating:Form
So to start you off, I’ve provided an example from the Docs:
{exp:rating:form entry_id="{entry_id}" form_name="review" require_membership="yes" status="open" return="{path='rating/thanks'}"}
<input type="hidden" name="name" value="{screen_name}" />
<input type="hidden" name="email" value="{email}" />
<label for="review">Your Rating</label>
<select name="rating">
<option value="1">1</option>
<option value="2">2</option>
<option value="3">3</option>
<option value="4">4</option>
<option value="5">5</option>
</select>
<label for="review">Your Review</label>
<textarea name="review" rows="10" cols="40"></textarea>
<input type="submit" name="submit" value="Submit!" />
{/exp:rating:form}
This code can be placed inside or outside of the Weblog:Entries loop on a Single Entry page, (though I would place OUTSIDE of the weblog:entries loop).
Parameters:
So what’s happing in here, is that the entry_id parameter will relate the Rating to the weblog entry.
The form_name parameter will create a dynamic form name as an extra way of sorting entries. It’s your option of how you want to organize this. An example might be, using this form on Restaurant Reviews, Movies Reviews, Hotel Reviews… you might want to group your ratings by “restaurant”, “movies”, hotels”, etc. It’s all dynamic, so you don’t need to create anything for a “Form name” in the CP… it’s like Freeform (if you’re familiar with it).
The require_membership parameter is self explainitory… the person must be a logged in member to submit ratings when set to YES.
The status parameter sets the status of which the Rating will go into once submitted. Setting the status to closed will allow you to review them first (in the CP).
The return parameter allows you to specify which template you want the member to go to once rating is submitted.
As for form fields:
Both the name and email form fields are required. Because we’re assuming you want your ratings submitted only from logged in members (with the require_membership parameter specified), showing the Name and Email fields is a little redundant. We still need them though, so we’ve hid them, and plopped in the {screen_name} and {email} variables to automatically grab this data.
The rating and review form fields are default fields from the Rating Module. They already exist in the CP as fields. You can create more in the Rating CP and add them as form fields in your Rating Form, should you want to collect more data
CP Home › Modules › Rating › Manage Fields >> click Create New Field
That’s it! The FORM is done.
Now, you’re probably going to want to display the Ratings 
You’re going to want to use the Rating:Entries loop for this.
Simple example from the Docs:
{exp:rating:entries limit="10"}
<p>{stars}{rating}{/stars}</p>
<p><a href="/user/edit/{rating_author_id}">{screen_name}</a></p>
<p>Date: {rating_date format="%m/%d/%y"}</p>
<p>Review: {review}</p>
<hr />
{/exp:rating:entries}
So we’ve specified a very simple example here. You would place this on a Single Entry page outside of the Weblog:Entries loop as well.
There’s more parameters you can use to filter and organize your results, but we’ve only chosen the “limit” parameter here. The form will only show up to 10 results.
You can see we’ve included the {rating}, {screen_name}, {rating_author_id}, {rating_date}, and {review} variables. The {stars}{/stars} variable pair is special that is converts your {rating} variable into a visual element - Stars images. The {rating_date} variable can be controlled in which format you want the date to display
The Rating Module goes a lot further than this. I hope that made sense, and gives you a good start with it. See if you can get those two working for you, and add to it from there (if necessary)
If you have any further questions, please let me know 
