Again, how do you search the table? That is, what are the common WHERE clauses that you use on the table? That is what should control the clustering.
If you (almost) always include a specific column in the search criteria, then cluster first on that column. For example, if you (almost) always specify date and fairly often specify name, then cluster on ( date, name ). If date and category, then ( date, category ). Finally, if by chance category is by far the most common and then date, then cluster on (category, date ).
You might also consider testing page compression vs. columnstore, esp. in 2014. You won't get as much data compression, but you still might get better overall performance results.
SQL DBA,SQL Server MVP(07, 08, 09) Prosecutor James Blackburn, in closing argument in the Fatal Vision murders trial: "If in the future, you should cry a tear, cry one for them [the murder victims]. If in the future, you should say a prayer, say one for them. And if in the future, you should light a candle, light one for them."