When creating an alert an estimate should be made of the number of hits

[freelawbot]

Using a query like this one, you can almost instantly get the number of hits per day for a query over the past 60 days:

http://localhost:8983/solr/select/?q=_:_&facet=true&rows=0&facet.range=dateFiled&facet.range.start=NOW/DAY-60DAYS&facet.range.end=NOW/DAY%2B1DAY&facet.range.gap=%2B1DAY

With a bit of work, we could make a simple API that you could feed a query, and which would say, "Average 33 hits/day". This could be displayed in the alert form when a user selects the rate that they want to receive the alert, using AJAX.

With this in place, users would know in advance about how many hits an alert is going to have per day/week/month. Should be fairly simple to implement using the query above.

---

• Bitbucket: https://bitbucket.org/mlissner/search-and-awareness-platform-courtlistener/issue/198
• Originally Reported By: Mike Lissner
• Originally Created At: 2012-01-01T02:56:26.717

[freelawbot]

Moved to feature tracker.

---

Original Comment By: Mike Lissner

[mlissner]

No idea why this was closed. Re-opening.

[mlissner]

This is now an important part of #612. It's fine if people want to create opinion alerts that have more results than are good for them, but it's problematic if they do so with RECAP, which has so much more content.

This ticket thus has two goals. First, add something to provide the estimate. Second, use that estimate to block new alerts that have a nonsensical number of results per period of time.

[mlissner]

I left blocking people to a later commit, but estimations should be working once I do a deploy. Closing this and I'll do the blocking code in another issue.