Historical snapshots

As if Josh hasn't enough to do:

• A weekly post to a blog that lists the 20/## most downloaded resources for the week;
• A monthly post to a blog that lists the 40/## most downloaded resources for the month;
• A quarterly post to a blog that lists the 100/## most downloaded resources for the quarter;
• An annual post to a blog that lists the 500/## most downloaded resources for the year;
• A weekly/monthly post to a blog that lists the 10/## most downloaded resources for each resource category for the year. IE: the 10 most downloaded topical files for e-Sword 9, the 10 most downloaded topical files for e-Sword 8, the 10 most downloaded files for MySword, etc, etc, etc.

Ideally, the lists would have the number of times they were downloaded during the reflected time period.

Theoretically, a script could automatically make those posts.



jonathon

As if Josh hasn't enough to do:

• A weekly post to a blog that lists the 20/## most downloaded resources for the week;
• A monthly post to a blog that lists the 40/## most downloaded resources for the month;
• A quarterly post to a blog that lists the 100/## most downloaded resources for the quarter;
• An annual post to a blog that lists the 500/## most downloaded resources for the year;
• A weekly/monthly post to a blog that lists the 10/## most downloaded resources for each resource category for the year. IE: the 10 most downloaded topical files for e-Sword 9, the 10 most downloaded topical files for e-Sword 8, the 10 most downloaded files for MySword, etc, etc, etc.

Ideally, the lists would have the number of times they were downloaded during the reflected time period.

Theoretically, a script could automatically make those posts.

jonathon

Yeah that's pretty easy to do. Sql statements in a php file, triggered by a once daily cron job so the display page would update once a day. You can't hit the database that hard for every unique viewer, but it could easily update once a day. That's really not a bad idea. I like it.