Modify existing data mining(fetch) code

This job requires the programmer to update/modify existing PHP code and PostgreSQL tables/columns. The purpose of this code is to fetch data from a remote website, and this remote website was recently updated, and now some of the data/data structure has changed, and some additional data fields(columns) have been added.

The fetching/data mining occurs on 2 pages on my website... predial.php and dmp.php. These two pages call to the following pages:

predial.php requires:
require 'framework.pg.php';
require 'config/settings.inc.php';
require 'inc.settings.func.php';
require 'inc.template.php';
require 'inc.claves.func.php';
require 'inc.predial.func.php';
require 'inc.dates.func.php';

dmp.php requires:
require 'framework.pg.php';
require 'inc.template.php';
require 'inc.claves.func.php';
require 'inc.dates.func.php';
require 'inc.tramites.func.php';
require 'inc.predial.func.php';
require 'inc.idx.func.php';

The data is written into the dmp dB and into the predial and predial_history tables.

The website where the data is mined from is located at the following URL:
http://www.eloscabos.gob.mx/CATASTRO/ESTADO_DE_CUENTA.aspx?CLVCAT=

This website requires a CLAVE NUMBER that is usually 12 digits(e.g.- 403045001007) or 18 digits with a dash(e.g.- 409002001001-002015), but can also be 10 digits(e.g.- 4010690288). These clave numbers are in my PostgreSQL 'dmp' database mentioned above, in the 'claves' tables under the 'clave' column. Below are the complete URL query string for the above clave number examples:

http://www.eloscabos.gob.mx/CATASTRO/ESTADO_DE_CUENTA.aspx?CLVCAT=403045001007

http://www.eloscabos.gob.mx/CATASTRO/ESTADO_DE_CUENTA.aspx?CLVCAT=409002001001-002015

http://www.eloscabos.gob.mx/CATASTRO/ESTADO_DE_CUENTA.aspx?CLVCAT=4010690288

Please visit the above URLs so you may view the various data that is returned, and be advised that the same data is not returned for each and every clave number... some may produce more data then others.

It is also important to note that any query that is made that does not return BOTH an OWNER NAME or PROPERTY TAXES needs to be considered INVALID, and NOT written to the dB.

Sometimes a query result will return no OWNER NAME but it will return PROPERTY TAXES, in these instances, the record needs to be considered VALID. As example of such a record is as follows:
http://www.eloscabos.gob.mx/CATASTRO/ESTADO_DE_CUENTA.aspx?CLVCAT=401001077015

The data that is fetched from this remote website is subject to change, therefore, each time a CLAVE number is fetched from this remote site, the data as a whole needs to be TIME/DATE stamped so that versions may be maintained. For example; if a CLAVE number is fetched today, and the OWNER NAME returned is JOE BLOW, and then if this same CLAVE NUMBER is fetched next month and the OWNER NAME is JANE PLAIN, the previous information fetched(JOE BLOW) needs to be moved to the HISTORY table. If in 3 months this same clave number is fetched, and the OWNER NAME is DON JUAN, then the previous JANE PLAIN needs to be moved to the HISTORY table along side JOE BLOW. Over a few years, the data base may have several historical OWNER NAMES saved in the predial_history table.

The same thing apples to PROPERTY TAXES, but unlike OWNER NAMES, PROPERTY TAXES change much more often, and contain many more pieces of data(table columns), and data that is grouped and calculated(ledger, sum totals), so these need to be properly structured and formatted in both the 'dmp' 'predial' and 'predial_history' tables.

The following URL shows all the possible fields(dB table columns) of information that may be returned when fetching a CLAVE number, so please take note of this, as every bit of information must be fetched when available:
http://www.eloscabos.gob.mx/CATASTRO/ESTADO_DE_CUENTA.aspx?CLVCAT=408002661001

At the present time, my website only displays current information for a CLAVE number. After the above HISTORY feature is completed, the pages on the website that displays the CLAVE number information, needs to have the ability to display HISTORICAL information for each CLAVE number. When we chat and discuss this job, and look at the existing pages, we will mutually decide how this historical information is to be displayed, and I will add the results to this Job page for clarification purposes, and you can submit your bid accordingly.

======

Winning bidder will be required to comment any code they change/add with their name and time/date stamp.

IMPORTANT NOTICE:
DO NOT BID UNLESS YOU HAVE FIRST CONTACTED ME AND HAVE REVIEWED THE WEBSITE AND CODE! ANY BIDS MADE WITHOUT FIRST DOING THIS WILL BE IGNORED.

I will need to provide you with a user name and password in order to log onto the website and view the code in action. please message me when you are ready to start a chat session(skype).

Thank you,

Eric Jarvies