balsama/bos311drupal

Boston 311 reports in Drupal

bos311drupal's Issues

Periodically check for updates to open issues

Report IDs are generally sequential. This is undocumented but observable. I say "generally sequential" because there seem to be large and small gaps periodically. But, as far as I can tell, newer reports are always given a numeric Report ID higher than older reports.

Currently, the fetcher works in two ways:

• Starts with the highest current local Report ID and gets n new reports higher then that - incrementing by one..
• Starts with the lowest current local Report ID and gets n new reports lower then that - incrementing by one.

In this system, reports that have been fetched are never updated.

We need an additional fetcher that finds existing (already fetched) reports, determined if new info is available, and updates the record accordingly.

Outstanding

[ ] Fetcher needs to periodically check for updates on open issues [#4]
[ ] Smaller area taken up by default image
[ ] Neighborhood cleanup (very few leather district reports, Downtown vs Financial District)
[ ] Somehow limit initial searches to last month (or week or year)