Database

From Nemo

Jump to: navigation, search

Use Cases

Sample Queries

Overview

The overall design of the database is sketched in the following architectural diagram. There are a few important aspects of the database worth noting.

  • First, the database will store structured information in tables as usual.
  • Second, raw EEG, ERP and of the other data outputs, while still highly structured, are just too large to put directly in a database. Furthermore, there is no known need to query them via SQL. Therefore, the database will be accompanied by a file archival system. Files will be referenced via pointers (or URIs) to the files and they will be appropriately linked into the functional and other provenance data.
  • Third, some of the raw file outputs (e.g., autolabel files) are small enough and useful enough to be "slurped" into database tables for direct SQL querying. Therefore, for both satisfying archival purposes and utility, the raw files as well as the same information slurped in tabular form will be appropriately managed, linked, etc. by the database.
  • Finally, the database will be accompanied by automated processes as well. For example, an autolabel file might get uploaded. Background processes might detect and automatically slurp it into the database tables. After that is complete, another process might be fired that transforms that data into an RDF-compliant format (see Data_Annotation).

(source file: File:DatabaseArchitecture.pptx)

/wiki/images/1/17/Fish1.png /wiki/images/e/ea/Fish2.png /wiki/images/f/fa/Fish3.png /wiki/images/f/ff/Fish4.png /wiki/images/4/40/Fish5.png /wiki/images/c/c5/Fish6.png
Personal tools