Laserfiche WebLink
eLogical Database Design Methodology <br /> The Logical Database Design should consist of four parts : <br /> 1 . Kickoff Meeting <br /> 2. Existing data acquisition and review <br /> 3. Interviews <br /> 4. Logical Database Design <br /> Kickoff Meeting <br /> Kickoff meeting attendees should include all Indian River County personnel that currently or <br /> will in the future: <br /> • Create spatial data <br /> • Provide input on the creation , updating or use of spatial data <br /> • Use spatial data on a regular basis . <br /> The kickoff meeting should introduce the goals and objectives of this project, outline how the <br /> project will be conducted , and inform attendees of what will be required of each them . <br /> Existing Data Acquisition and Review <br /> Before the Logical Database Design process can move forward , Indian River County will <br /> need to ensure that if has a copy of all existing County data layers and source data from <br /> each department that will be included in the database design . <br /> Interviews <br /> All pertinent staff members from each County department/division should be interviewed . <br /> Interviews can be conducted separately for each department, or in logical groupings . The <br /> goal of each interview is to discuss in detail each data layer for which attendees are the <br /> Subject Matter Expert . <br /> Issues that should be discussed include : <br /> Deletion of existing attribute fields <br /> w0 Addition of new attribute fields <br /> • Allowable values for important attribute fields <br /> • Relationship of layer to other layers <br /> • Associated tables and cardinality <br /> • Description or alias of each field (when not obvious) <br /> • Subtypes <br /> • Default values <br /> • Whether null values are allowed or not <br /> • Indexes <br /> Several important metadata aspects ( not documented or available from the earlier existing <br /> data acquisition ) to include ( but not limited to) should be documented , including : <br /> • Feature Class Name <br /> • Feature Class Type ( point, line , polygon or raster) <br /> Feature Dataset <br /> • Description <br /> • Purpose <br /> • Data source <br /> 54 <br /> GIS Needs Assessment and Implementation Plan Chapter 5 - Database Design and Setup <br />