Orange County NC Website
Browse       Search
DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 <br /> In the EnerGov model, contacts are stored as in category 1 above. Those contacts put into EG_Template without a <br /> master'contact' record link(category 2 above)will be migrated into custom field memo boxes to avoid duplication of <br /> contacts within the EnerGov contact repository. <br /> For example, when populating the permit contacts, those contacts for category 1 should go into the 'permit_contact' <br /> table. Those contacts for category 2 should go into the 'permit_contact_no_key' table. <br /> Multiple Legacy Data Sources: <br /> There are usually multiple data sources to convert in a project. The plan is to have all data sources populated into the <br /> EG_Template db. At the main table level,there is an optional column where the legacy data source can be populated <br /> for reference. This is provided as a way to easily count up or research records originating from a particular legacy data <br /> source. <br /> Overall Architecture of Conversion: <br /> There are 3 SQL Server databases involved in the conversion process. <br /> 1. EG_Template (for legacy data) <br /> 2. EnerGov (the production EnerGov db) <br /> 3. A database containing all conversion processes and mapping tables. This is maintained by Tyler's data <br /> conversion team. This db takes the data from EG_Tempate, translates it, and populates it into the EnerGov db. <br /> All legacy data sources will be This db will be used to This is the EnerGov db used by the <br /> loaded into this one db,within the map/translate data before it passes EnerGov software. <br /> provided table structure. into EnerGov. Stored procedures <br /> and functions will exist in this db, <br /> which will essentially be the <br /> conversion source code. <br />