how do I split database models based on a single spreadsheet table (beginner)?

how do I split database models based on a single spreadsheet table
(beginner)?

My question is conceptual, I suppose, rather than practical (though I
don't mind if the practical makes an appearance).
I'm a graphic designer that is now building a web application at my
workplace (a business firm) with Rails + postgresql, in which the premise
is to display a list of services stored in a database. I've been requested
to design a spreadsheet table for use by data-entry folk to do the grunt
work of copying hard-copy into data, that I can then, in turn, transfer to
the database.
The data is to be displayed, sorted, and filtered with JQuery - so the
point of the table structure is to lend itself well to that process. My
question is, is it better to split an incoming table of data (from
spreadsheets or .csv's) into two in order to separate the data displayed
explicitly (i.e., name, description, link, image) from the data that will
be used for sorting and filtering (i.e., tags like "location" and
"category of service") or best to keep the database table single and the
same as the incoming spreadsheet?
Or have I gone wrong already in the way I've begun to think about it?