Laserfiche WebLink
<br />Chapter 2 <br /> <br />Framework for <br />Developing the Database <br /> <br />This chapter provides an overview of the framework and logic ECO and the TAC <br />used to develop the Lane County Commercial and Industrial Lands database. It <br />begins with a discussion of the ideal database, then describes what was practical <br />given the scope and budget of this project, and concludes with a description of <br />what is included in the Lane County Commercial and Industrial Lands database. <br /> <br />IDEAL DATABASE AND QUERY SYSTEM <br /> <br />The ideal data system to address the questions of this project is one that is: <br />. Fed continuously by real-time data from a variety of individual databases <br />. Queried in a manner that extracts only data relevant to the question at <br />hand <br /> <br />. Able to produce new data based on calculated relationships between <br />existing data <br /> <br />. Accessed by users through an interface that is simple and user friendly. It <br />displays results through easy to use client interfaces customized for <br />specialized needs. <br /> <br />In short, direct views of the tables in the database, stored procedures, or <br />queries are of little use to the planner or economic development specialist. <br />Customized interfaces should present the end user with essential information in <br />graphical format that facilitates easy analysis. Additionally, the custom interface <br />would also permit the user to not only view the current data but also extend the <br />data with modeling functions and produce reports and maps. Such a system <br />requires that: <br /> <br />. Data are accurate and up-to-date. An ideal system is made up of several <br />databases, residing within the various agencies that are responsible for <br />their maintenance and are at the initial point of receiving updates to the <br />data. <br /> <br />. Data contained within the source databases is dynamically connected <br />throughout the system: to the intermediate queries and views of the <br />database, all the way to the custom client interfaces. When any record in <br />the source database is updated, the updates are automatically carried <br />through the system, updating the values seen in the queries, calculations, <br />and interfaces. This process is done through a series of stored procedures. <br />Rather than having to initiate a new query of the database each time from <br />the end user, the updating of any relevant record in the database initiates <br />or triggers the update of the system. <br /> <br />Figure 2-1 diagrams such a system. <br /> <br />DRAFT: Commercial and Industrial Lands Database <br /> <br />ECONorthwest <br /> <br />July 2006 <br /> <br />Page 5 <br />