Update models to match current DB index/key setup
Write a working stub for DB maintenance component
Importer: upsert mechanism, consenus deduplication

 - Write a sane upsert mechanism for the intermediary fingerprint table
   in importer.py - update/insert is efficient, but intelligent enough
   to know when to overwrite data (newer last_va), update/insert, etc.

 - When switching from a batch archival data import setup (via mass
   import shellscripts in tools/, etc.) to rsync'ed ::recent, there may
   be overlapping data that Stem's persistence_file approach will not
   cover. Solve this by checking for existing valid-after (efficiently,
   using 'consensus' table)
Write cronjob script for hourly rsync and import
Implement date range params for all 3 doc types

 - from..to parameters to filter down valid-afters (and {first,last}_va
   before the JOINs in the fingerprint table) for summary, details, statuses

 - use dateutil.parser for intelligent user-supplied datetime string parsing

 - hence update requirements.txt: add dateutil
Netstatus doc: simplify; implement 'ranged' view

 - fingerprint mentioned only once; overall, a simpler JSON structure

 - ?condensed=true => valid-afters are given in condensed range form
Merge branch 'master' of github.com:wfn/torsearch

 - README.md was updated on github