PHP/CRON AUTO-FETCH + MISC script modifications

1 - change all website php/cron scripts from localhost postgresql server to remote postgresql server at 204.232.201.155.

2. fix all CRON/AUTO-FETCH scripts so TRAMITES and IDX fetch automatically daily, and immediately afterwards any of those TRAMITES and IDX records that have CLAVE numbers are then AUTO-FETCHED against the PREDIAL source. this code already exists, it just needs to be updated/modified/fixed and fine tuned so it works properly again. please make sure to tune the queries so they are as fast as will the proxy code/servers allow them to be, aka fine tune the fetching for optimum performance.

3. after connecting to the remote postgresql dB in item #1, and after repairing the CRON/AUTO-FETCH code in item #2, need to manually purge all superfluous records in the dB, namely 'aun' column flagged UNASSIGNED/NOT YET SEARCHED records that are NOT either IDX, TRAMITES, or GIS derived. in the end, no records should remain in the NOT YET SEARCHED category, and only TRAMITES, IDX, and GIS records without valid PREDIAL records should remain in the UNASSIGNED category. after this is done, please do a test by fetching the day's TRAMITES and IDX records, and making sure all NEW CLAVE numbers are placed in the UNASSIGNED category, and then make sure they are then AUTO-FETCHED against PREDIAL, until they are all done. by the end of each day, all TRAMITES and IDX and GIS records should be fetched/processed against remote PREDIAL source and categorized accordingly.

4. on clave.php, make each row/field editable. need to add the ability to add PHOTOS(png, jpg, etc.) and DOCUMENTS(xls, doc, ppt, pdf, etc.), and CAD drawings(dxf, dwg, etc.) attachments. add a new field called WWW so we can add website for a given record. add a URLs field so we can add one or more reference websites.

5. on claves.php page, need to display all columns(LIGHTING, SIDEWALK, etc.). extending on the above item #3, we need to be able to add/associate PHOTOS/DOCUMENTS to/with multiple records. a good example is a condo regime with 50 units... adding one PHOTO that covers the condo regime's 50 individual units, so we do not have to add the PHOTO one record at a time, in this example 50 times for 50 units in the condo regime. the same thing applies for DOCUMENTS and CAD DRAWINGS.

6. TRAMITES.PHP & PREDIAL.PHP SEARCH/QUERY FILTER ADDITIONS:
A. On the Tramites page, need to add 'Process Type' and 'Reason' selections to the pull-down filter menu. They are as follows:
(following found in 'process_type' column in 'tramites' table):
PROCESS TYPE: 01 AVALUOS PERICIALES
PROCESS TYPE: 02 SUBDIVISION DE PREDIOS
PROCESS TYPE: 03 FUSION DE PREDIOS
PROCESS TYPE: 04 LOTIFICACION Y RELOTIFICACION
PROCESS TYPE: 05 REGIMEN DE PROPIEDAD EN CONDOMINIO
PROCESS TYPE: 06 CANCELACION DE DOCUMENTOS
PROCESS TYPE: 07 REGISTRO DE TITULOS O POSESION
PROCESS TYPE: 08 MANIFESTACION DE CONSTRUCCIONES
PROCESS TYPE: 09 MANIFESTACION DE ESCRITURAS
PROCESS TYPE: 10 CORRECCION DE MANIFESTACION
PROCESS TYPE: 11 ISABIS
PROCESS TYPE: 12 DESLINDES CATASTRALES
PROCESS TYPE: 13 CERTIFICACION DE DOCTOS.
PROCESS TYPE: 14 EXPEDICION DE COPIAS
PROCESS TYPE: 15 CARTA DE NO PROPIEDAD
PROCESS TYPE: 16 SOLICITUD DE ACLARACIONES
PROCESS TYPE: 18 PROTOCOLIZACION
PROCESS TYPE: 20 PUNTOS UTM
PROCESS TYPE: 21 GENERACION DE PLANOS
PROCESS TYPE: 22 ACTA ACLARATORIA
PROCESS TYPE: 23 PROTOCOLIZACION SUBDIVISION
PROCESS TYPE: 24 REPOSICION MANIFESTACION
PROCESS TYPE: 25 TITULOS CORETT/ RAN
PROCESS TYPE: 26 CSL-MANIFESTACION DE CONSTRUCCION
PROCESS TYPE: 29 CEDULA DE INFORMACION CATASTRAL (or 29 CEDULA CATASTRAL )

(following found in the 'reason' column in the 'tramites' table):
REASON: ADMINISTRACION
REASON: AVALUOS
REASON: CAPTURA
REASON: CARTOGRAFIA
REASON: JURIDICO
REASON: MANIFESTACIONES
REASON: OPERACIONES CON PREDIOS
REASON: RECHAZADO
REASON: RECEPCION
REASON: TOPOGRAFIA

in effect, we need to add every data type contained within the TRAMITES table so we can search/organize/order using these respective filters. need to also check each and every existing filter to make sure each is working correctly.

B. just like the above TRAMITES filters, need to do the same for PREDIAL, adding every data field, like the recently added BIM, ANO, etc. fields to the FILTERS so data can be searched/drilled down per data type.

7. fix SEARCH results on TRAMITES/PREDIAL/IDX/CLAVES/CLAVE pages to only return results for entered string of text. currently searches return open-ended results, e.g.- searching for 'ERIC' returns 'ERIC, fredERIC, ERICSON, ERICK', and every other word containing 'ERIC', which is incorrect.... returned results should only contain records with 'ERIC' like 'ERIC JARVIES' or 'MARTIN ERIC JONES' but not 'ERICK JONES'.

8. add SETTINGS page to the main menu, wherein SETTINGS.PHP page contains editable settings currently found in config/servers.inc.php, so can edit DEVELOPMENT/STAGING/PRODUCTION server settings so it's easy to move the website code to any server, and to be able to point to any postgreSQL server and CRONTAB, either localhost or remote. the servers.inc.php code also needs to be cleaned-up, like i think the google maps key is no longer needed(is it?).

9. on the PREDIAL.PHP page need to update the movimentos section like was done on the CLAVE.PHP page so ALL the CORRECT PREDIAL tax information is displayed on the search results rows/individual records. this is actually left-over from the last task that i forgot about.

======

THIS JOB TO BE COMPLETED IN FULL ON OR BEFORE MARCH 4 2011.

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.


Thank you,

Eric Jarvies