Problem: We often are asked to report download metrics geographically. This can be done by hand based on IP address in our metrics but is a bit tedious. It would be better if we had an automated solution for determining IP address location.

User: Admin, metrics stakeholders

Solution: Use quartz to run ~daily job. Job finds oldest unpopulated IP address and processes it, performing bulk database update Confirm quartz job concurrency.

Idea: Algorithm to find oldest not geocoded ip, then update all file download records with that ip, repeat. Consider a 24 hour cache for IP address.

Big steps:
Quartz trigger
DB Query for IP address
Call GeoCode service
Run DB mass update in Tx

Idea: Background process to add nslookup of ip, geocode (lat, lon) of ip. Use a caching table to lookup IP (use ehcache?)

Add: lat, lon, city, state, county, etc.