Changes between Initial Version and Version 1 of User_Database


Ignore:
Timestamp:
01/10/07 13:58:30 (12 years ago)
Author:
ebmoore
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • User_Database

    v1 v1  
     1What is a user level database? 
     2 * A user level database contains the data available to a user on their local filesystem (or networked file system) 
     3   * Not this does not preclude having a shared instance between users. 
     4 * Minimal configuration. 
     5 * Simple and abstracted (i.e. they should not know it is a database as opposed to a list of files and metadata) 
     6 * Elegantly handle sparse data. 
     7 * Like the iTunes Library (or iPhoto or even like a good email client) 
     8 
     9Problems for researchers: 
     10 * Most data is only organized as a series of folders or less organized than that 
     11 * Most neuroscience labs either lack the expertise, or the time to set up a full lab database. 
     12 * Most researchers know they need more, but won't invest the time until they know the benefits.  This means that any real setup is a discouragement to actually setting up a full database (especially because there are competing solutions that each offer different amounts of power and niches, our group has produced 2 such databases Seedpod and Celo). 
     13 * Quickly finding data and visualizing it is important when dealing with large sets of data. 
     14 
     15Priorities/Goals (in order from most to least important): 
     16 * Zero configuration 
     17   * install 
     18   * populate 
     19 * Elegantly handle sparse data 
     20   *Users unlikely to take the time until they see potential 
     21   *Users should get some benefit from the first untagged piece of data that is added. 
     22 * Intuitive 
     23   * Best user interface possible 
     24     * Multiple views of data 
     25       * table 
     26       * simple list 
     27       * tree where the tags are parent nodes 
     28     * Quick search feature (simply type into a search box and get a list of all the names and tags that match) 
     29     * maintain a minimal number of easy concepts 
     30       * Data 
     31       * Tags (like putting sticky notes on the data) 
     32       * Maybe Abstract Data (data that is not a file, i.e. Patient information) 
     33 * Responsive (this is different than speed) 
     34 * Power 
     35    * rely on brute force instead of having a more populated/complex database 
     36    * Allow the user to chain simple queries 
     37 * Speed 
     38    * While important, this is last because: 
     39       * users have powerful computers 
     40       * we want to minimize complexity and population requirements 
     41       * Good feedback and queries that don't need to be babysat may be sufficient.   
     42 
     43 
     44Additional goals (in no order): 
     45 * Fully integrate with MindSeer -- visualization is the cornerstone of making the database useful from the beginning.  It also ensures that users can see their results immediately.  Seems like a good way to set the standalone version apart from the competition. 
     46 * No matter what the internal format used is, keep a synchronized external format in XML so XQuery can ask queries across user computers and any central repository.  Sounds like good stuff for a grant, eh? 
     47 * Users of X-Brain should have virtually no populating requirements