More specific dataset types.

As a user I find that when I am uploading datasets on a quarterly basis, I often have to create a new dataset just for that quarter if I have too many files for a single dataset - one dataset with 100 resources (say 25 for each quarter) is hard to work with in the UI. This also applies to datasets that are updated monthly, or worse, weekly. I'd still however like to keep a year worth of data in a single dataset.

Should CKAN provide specific types of datasets out of the box, but all available at the same /datasets url?

Specifically could/should CKAN provide a QuarterlyDataset, where the user had to specify which quarter the resource belonged to, and/or a MonthlyDataset where the user had to specify which Month the resources belonged. This would make it much easier, at least at the UI level to group resources together so that they are easily manageable. I am envisioning at UI where the four quarters of the year are addressable directly, and also grouped within the UI so that users can go straight to the quarter they are interested in?

This would also potentially simplify reporting on when particular datasets are 'late', and other reports that required the regular updating of datasets.

No files, tests, or entry points are named. Start by clarifying whether quarterly or monthly grouping should be implemented at the shared /datasets URL and in the UI, then define how users specify periods and how reporting handles late datasets. Done means the scope and behavior for annual datasets with quarterly or monthly resources are agreed.

Written by the indexing model from the issue text.