Are you sure you want to do this in SQL? Taking 'slices' of your results isn't very SQL-like, and doing text searches in the where clause isn't a thing in which SQL shines as well (since there won't be constraints the engine can use).

Considering the secret of time travel hasn't been discovered yet, there won't be any new articles of the Campus Newspaper that will be printed between 1925 and 1980, nor will they become unprinted. Your engine screams for a solution where the articles are preprocessed, and indexed based on their content. You know, like google and other search engines do it). That doesn't mean you don't store anything in a SQL database - in fact, you could still store all your data in a SQL database. But you wouldn't be doing full table scans, with full scans of text fields.

Abigail