Database structure. The database of seismogenic sources is a geographically referenced relational database. Guidelines on how to compile records of the database and/or to reproduce the entire database structure (Basili et al., 2009) have been distributed at the WP3 Meeting on 14-16 September 2009 in Rome and made available from several websites. The database is composed by several subsets which share the same structure and data model. Each subset covers a different region of the SHARE area. The subsets are first collated automatically into a single dataset and then scrutinized to produce and homogenized database (Figure 2). The latter procedure is illustrated in Chapter 4 in more details. This multi-level structure has the advantages of preserving the original data as they were supplied by the regional compilers and permits an easy update of the merged database when new data are added or old data reviewed.
Database structure. The NANoREG WP6 literature database contains 8 types of information that can be extracted from published studies. - Study information (1) - Nanoparticle identification parameters (2) - Physicochemical characteristics of a nanoparticle (4) - Data of experimental media (3) - Data of the preparation protocols (3) - Data of the test subject (4) - Data of the exposure conditions (4) - Data on the endpoints (5) The underlying database structure is a MySQL database, which is a relational database. The database consists of multiple tables. A specific field in a table is defined by its name and the table in which it exists and the relation of that table to others. The tables are built up in a hierarchy. The number in the list of 8 types of information indicate how the hierarchy of tables is built up. A database entry is defined by information on the study from which it is extracted. In a study, multiple particles can be described/investigated, so multiple tables on nanoparticle identification parameters can exist within one study. Of each particle multiple physical chemical characteristics of the nanoparticle can be provided/ measured. Within each combination of an exposure/ test medium and preparation protocol multiple measurements of physical chemical characteristics multiple and exposure conditions with test subject characteristics can be added to each nanoparticle. Finally multiple (eco)toxicity/ bio assays can be added to each set of exposure conditions and test subject characteristics. Figure 1 explains more clearly on the structure of the database and the hierarchy.
Database structure. The database will contain information about the stored samples in the distributed storage solution. This information will be previously processed by the aforementioned Web Service. The database will be implemented in MySQL and the information will be stored in a structure as follows: CenterID OrganizationID Abbrev Description Date PATHOLOGIES DEVICES
Database structure. The geodatabase is comprised of two feature classes (observations and survey_poly) and two tables (incidental_attributes and reference_information). Each Observation is assigned an ID that is used to link it to either a Survey (Survey_ID) or an Incidental (Incd_ID) record. Observations of yellow-billed loons (YBLOs) are considered to have been derived from a survey if both of the following conditions are met 1) there was a search area with reasonably well-defined boundaries, and 2) YBLOs were among the taxa specifically targeted by the survey. Any observation that does not meet these criteria is classified as incidental observations. Incidental observations can include observations contributed by persons engaged in activities other than wildlife surveys, observations obtained during the course of biological survey work targeted at another species such as caribou, historical observations from the literature, or observations derived from surveys that cannot be matched with a corresponding survey polygon. Incidental observations are assigned the non-unique value "Incidental" in the Survey_ID field and are related to the incidental_attributes table via a unique value in the Incd_ID field. A simplified schema for the geodatabase is presented in Figure 2. A complete data dictionary is provided in Appendix A. Figure 2. Simplified database structure.
