FlowDB

Here we describe how to apply the FuGE model for creating a database schema using standard SQL that can be used to populate an SQL compliant database. Included here are notes on how to create a database schema for storing RDF and RDF schema information.

First Steps

  1. Map Generic Protocol from FuGE to Schema to learn how to do the mapping
  2. Establish rules for mapping FuGE to Schema in a Generic way
  3. To Identify what is missing in FuGE that might be needed at the DB Schema level
  4. Apply what we have learned to FlowDB.

News

2007-11-14


Development of a database schema based on FuGE

SQL attribute Categories

Attributes are tagged with a prefix that describes the category to which an attribute belongs. These categories distinguish the role of the attributes.

  1. Record Attributes that are used for administrative record keeping

  2. Lims Attributes that are needed to reference a LIMS record

  3. Entity Attributes that re derived from a FuGE model

  4. Application Framework Attributes that are related to an application framework


Mapping Rules from DB to FuGE

  1. Identify all attributes that are not exported to FuGE, mark them for omission
  2. Organize db attributes into 'SQL attribute categories'
  3. Assign all FuGE related attributes to NameValueType

  4. Re-Assign NameValueType attributes that map to FuGE

  5. Map all foreign keys to the associated ends


Diagrams

  1. ONT ERD Diagram: Ontology
    • Zipped JPG

SQL


Development of a database schema for RDF and RDF Schema

Articles

  1. Montano et al., "A Path-based Relational RDF Database"
  2. Montano et al., "An Indexing Scheme for RDF and RDF" Schema based on Suffix Arrays"


FlowDB (last edited 2007-11-28 18:30:09 by PeterWilkinson)