Devour provides an extensible workflow to establish connections to external sites and extract data according to user input. Devour prefers geodata that is referencable and comparible as this is most easily relatable.
It is extensible in that site configurations can be easily added using Drupal hooks. This allows much simpler (and in-turn much quicker) deployments to various sites.
Devour depends on the following tools:
- Selenium WebDriver to create REAL user sessions that can move thru a site and do complex tasks that are unavailable to other methods.
- php-webdriver to send commands to Selenium using PHP.
- Drupal to present the data and facilite in error handling.
Error handling and logging is a big part of Devour as there are so many possible iterations of a page response. Errors due to maintenance or changes are considered normal and must be well-documented and seamless to user interaction. Devour hooks integrate this error handling.
Here is the roadmap for development for Devour:
- Database table for storing system settings (adding sites)
- What data I need to extract data - (Site name,User specific data)
- Table for storing user settings (perferences) Array of data in table for now
- Setup Fields added to devour_specific tables
- Create initial form
- Block(s) for outputting the data
- Database table for accessing content (caching)
- Mapping functionality to tie into the user interface (Allow for more speicifc user location data (street))
- Allow to add additional profiles from settings page
- Add validation
- Create custom user page for preferred content (Put preferred content in select boxes)