Should you use the canonicalization tag when the content isn't exactly a duplicate?

[Fuel]

We have a site that pull data from different sources with unique urls onto a main page and we are thinking about using the canonicalization tag to keep those source pages from being indexed and to give any authority to the main page. But this isn’t really what canonicalization is supposed to be used for so I’m unsure of if this is the right move.
To give some more detail: We manage a site that has pages for individual golf courses. On the golf course page in addition to other general information we have sections on that page that show “related articles” and “course reviews”.
We may only show 4 or 5 on each of those courses pages per page, but we have hundreds of related articles and reviews for each course. So below “related articles” on the course page we have a link to “see more articles” that would take the user to a new page that is simply a aggregate page that houses all the article or review content related to that course.  
Since we would rather have the overall course page rank in SERPs rather than the page that lists these articles, we are considering canonicalizing the aggregate news page up to the course page.
But, as I said earlier, this isn’t really what the canonicalization tag is intended for so I’m hesitant.
Has anyone else run across something like this before? What do you think?

[AndrewAtMGXCopy]

Hey Fuel Interactive --

To answer your specific question, I would use the meta (noindex, follow) tag instead of the canonical. It doesn't pass authority, but it is the correct usage. It will strike the page from ranking consideration, and allow the overall course page to have less competition.

Another question for you: is the article listing page already ranking higher than the overall course page, or is this a worry? If it's a worry, I recommend testing it out first so you don't prematurely optimize. Just a thought.

Hope that helps -- Andrew