Browse by Date: use most recent pub date as the endDate for "past week", "past month", and "past 3 months"

Not sure I have understood this correctly. We have the concept of Past Month and Past 3 Months. Journals can choose to make one of them the default. Why do we need to do it on a weekly basis?

I think we need to get away from Browse by data altogether. I would be curious to see what the user stats here are. With the ability to do search on date ranges why is this needed?

See source:private/russ/benchmark.xls, the first sheet - seems to get used.

addition to past month and past 3 months we also have past week. this is nothing new.

"journals pubbed in the last week" is the default response to browse.action?field=date if no day, month, or year parameters exist.

it's what we point the "browse by date" link to in all the journals.

if nothing has been published in the last week, it's blank, which is lame.

we'd the default case to find the most recent pub date, and use that as endDate for the week calculation.

in fact, it would probably be good use to the most recent pub date as the endDate for all 3 "past x" actions.

So we need to add 'last published date' somewhere (probably to Journal).

First, I would argue that "past week" means exactly that, not some random previous week. If journals don't publish weekly, then just have browse-by-date point to previous month or something. Also, it's not hard to add other, fixed, previous-interval options.

From the implementation side a previous-x-starting from last-published would be far more work than just adding another date field, because currently the queries currently always know what date to search for, which will not be the case anymore. This could have a noticeable hit on performance and will require a whole bunch of rework on the caching side.

I.e. this would not be a "simple" change.

:) Seem my first comment.