title: In MVC, should the Model or the Controller be processing and parsing data?
body: <p>Until now, in my MVC application, I've been using the Model mainly just to access the database, and very little else. I've always looked on the Controller as the true brains of the operation. But I'm not sure if I've been correctly utilizing the MVC model.</p>
  
  <p>For example, assume a database of financial transactions (order number, order items, amount, customer info, etc.). Now, assume there is a function to process a .csv file, and return it as an array, to be inserted into the database of transactions.</p>
  
  <p><em>I've</em> placed my .csv parse function in my Controller, then the controller passes the parsed information to a function in the Model to be inserted. However, strictly speaking, should the .csv parsing function be included in the Model instead?</p>
  
  <p>EDIT: For clarity's sake, I specifically am using CodeIgniter, however the question does pertain to MVC structure in general.</p>