Putting the View back into MVC.

[eluser]dtrenz[/eluser]
Man, I am so confused now.

From everything I've read, it appears that one of the few concepts of MVC that is universally accepted is that MVC solves code/design problems that tend to arise as a result of too much coupling by separating data access, business logic, and presentation.

I guess I just assumed:

Model = data access
View = presentation
Controller = business logic

End of story.

But is sounds like my understanding of the meaning of business logic is wrong. I assumed business logic involved not only directing traffic between the model and view, but also massaging/preparing/staging data retrieved from the models before sending it to the views.

Are you all saying that all the controller should do is call model methods and load views, and that all data formatting or prep should be handled in the models as well as data access?

EXAMPLE:

What if you are on a user profile page on a website, and a truncated version of the users bio is displayed. By clicking a "read full bio" link, you are taken to the bio page where a NON-truncated version of the bio is displayed.

In this example, would you have 2 separate model methods for retrieving the bio text? One that returned the bio, truncated by some string truncate function, and another that returned the whole bio text?

I currently have one model for retrieving the bio, and then in the controller, I truncate (or not) before sending the bio text to the view.

Which is correct MVC? Either?