Neurolex is being transitioned to a new system and is currently not accepting new additions. If you have additions or questions please contact us at [email protected], or submit an issue to the github issue tracker at


From NeuroLex

Jump to: navigation, search
Abbrev EEGbase  +
CurationStatus curated  +
DefiningCitation  +
Definition EEG base is a system for storage and manag EEG base is a system for storage and management of EEG/ERP resources - data, metadata, tools and materials related to EEG/ERP experiments. EEG base advances electrophysiology research by enabling access to public data, tools and results of research groups. The system essentially offers the following set of features (the set of accessible features depends on a specific user role): * User authentication * Storage, update, and download of EEG/ERP data and metadata * Storage, update and download of EEG/ERP experimental design (experimental scenarios) * Storage, update and download of data related to testing subjects * Fulltext search * Sharing of knowledge and working in groups The system is based on tree layer architecture (MVC pattern) consisting of persistent layer (relational database), application layer (object oriented code, object relational mapping from persistence layer) and presentation layer (JSP). The persistence layer uses Hibernate framework; Oracle 11g database server is used to ensure the processing of large data files. Application and presentation layers are designed and implemented using Spring technology. This framework supports MVC architecture, Dependency injection and Aspect Oriented Programming. There were no significant difficulties with integration of both frameworks, Hibernate and Spring MVC. Spring Security framework is used to ensure management of authentication and user roles. Since the system is thought to be finally open to the whole EEG/ERP community it is necessary to protect EEG/ERP data and metadata, and especially personal data of testing subjects stored in the database from an unauthorized access. Then a restricted user policy is applied and user roles are introduced. The complete overview of the system features and user roles (use case diagram) is available in (Pergler 2009). Concerning the architectural layers there is a question which layer is more feasible for mapping of its structure into ontology. Currently we have studied two possibilities: * Mapping from the persistence layer (relational database) * Mapping from the application layer (object oriented code) The mapping from the application layer to an ontology includes the precedent object relational mapping provided by Hibernate framework. l mapping provided by Hibernate framework.
ExampleImage EEGbase.PNG +
Grant Category:1F84B/042/520   +, Category:102/07/1191   +, Category:406/09/0150   +, Category:ME 949   +
Has default formThis property is a special property in this wiki. Resource  +
Has role Database +, Data repository +
Id nif-0000-08190  +
Is part of University of West Bohemia; Pilsen; Czech Republic +
Keywords Electroencephalography recording protocol +, Event related potential +, Experiments +, Scenarios +
Label Resource:EEGbase  +
Modification dateThis property is a special property in this wiki. 20 December 2014 02:03:14  +
ModifiedDate 20 December 2014  +
Page has default formThis property is a special property in this wiki. Resource  +
PublicationLink  +
SuperCategory Resource  +
Supporting Agency Ministry of Education +, Czech Science Foundation +
Synonym EGG base  +
Usedby Resource:NIF Data Federation +
Categories Resource
hide properties that link here 
  No properties link to this page.


Enter the name of the page to start browsing from.

*Note: Neurolex imports many terms and their ids from existing community ontologies, e.g., the Gene Ontology. Neurolex, however, is a dynamic site and any content beyond the identifier should not be presumed to reflect the content or views of the source ontology. Users should consult with the authoritative source for each ontology for current information.