The document describes a new neuroimaging data repository created to organize and facilitate analysis of data from multiple studies conducted by Dr. Margot Taylor's lab. The repository is a browser-based database built using the MEAN stack (MongoDB, Express, Angular.js, Node.js). It stores participant demographic data, records of associated projects and scan sessions, and allows querying and exporting of data while protecting privacy through access controls. The repository allows researchers to efficiently analyze the lab's large aggregated dataset across studies for the first time.

1. FrameworkBackground
Objectives
Data Structures
Main Features
The Functional Neuroimaging Data Repository: a browser-based
cross-study database for tracking MEG and MRI metadata
Shawna (Xun) Wei1, Simeon M Wong2,3, Margot J Taylor2,3,4.
1 Faculty of Applied Science and Engineering, University of Toronto 2 Neurosciences & Mental Health, Hospital for Sick Children
3 Diagnostic Imaging, Hospital for Sick Children 4 Department of Pediatrics, University of Toronto
Search…… MJT Data Repository For more information, please contact me at shawnawei2@gmail.com
OLD
NEW
Dr. Margot Taylor’s functional neuroimaging lab investigates
the structural and functional developmental trajectories
between ASD, preterm born and typically developing children.
Over multiple studies, the lab collected a massive
neuroimaging dataset. Some participants are enrolled in
multiple studies and most have indicated consent for their
data to be stored and analyzed in future projects. This rich
dataset also includes valuable longitudinal data.
However, due to privacy and anonymity, it is difficult to
retroactively identify scans when analyzing data aggregated
from multiple studies. In addition, these data were collected
and organized in idiosyncratic ways, with differing naming
and organizational systems by various students and lab
members.
Develop a new system that is flexible, secure, as well as
consistent and applicable for all current and future projects.
We decided on a database-driven web application that
satisfies the following requirements:
 Store participant demographic information, associated
projects and scan sessions
 Tag each scan with scan type, scan time, and clinical
behavioural test scores
 Identify relations between each scan session and its
associated research participant and project
Moreover, for accessibility and security of data, the web-app
should also support:
 Query based on demographics, age at scan, scan type, test
type etc.
 Access limitation on each project and its associated scans
based on the user identity
 Exporting selected list of data as an Excel spreadsheet
The repository is written in HTML, CSS and JavaScript. To allow ease of development, future expandability, and adhering to
modern web-development best practices, the website complies the “MVC”: Model, View and Controller architectural
pattern and is developed using the “MEAN” stack: MongoDB, Express, Angular.Js and Node.Js.
The spreadsheet of scans
researchers work with.
Data are retrieved
through unintuitive and
unappealing Linux terminal
Description MEAN Components
• Manage
information stored
in database
• Manipulate how
application runs
• MongoDB: NoSQL
database for
flexible storage
Description MEAN Components
• Bridge between M
& V. Bringing user
requests from ‘V’
to ‘M’, and send
‘M’ responses
(manipulated data)
back to V
• Angular.Js: Two way
data binding between
M & V
• Express: web
framework, handles
request & response
from routes
• Node.Js: a runtime
server-side platform
Description MEAN Components
• User interface
• Present visually
appealing data
• Allow intuitive
interaction with
data
• Angular.Js: extend
HTML syntax for
dynamic app
• Other Libraries:
Bootstrap, jQuery,
Moment, SheetJS,
etc.
Model Controller View
Conclusion
With the implementation of the neuroimaging data repository,
tasks previously requiring hours of work can now be completed
within seconds by effortless clicks. This web application greatly
facilitates the research work done in the lab by fully utilizing the
data that have been collected, allowing larger, more complete and
more efficient analyses.
Information stored in the database is categorized into three
collections: Subjects, Projects, and Scan Sessions.
Subjects Collection
Subject 1 Subject 2 Subject 3
 -Subject ID
 Demographic Info
 Projects
Project 1 Project 2
 -Project ID
 -Subject ID in Project
Scan Sessions Collection
Session 1 Session 2 Session 3
 MEG Scans
 MRI Scans
 Behavioural Tests
 -Subject ID
 Scans/Tests
Projects Collection
Project 1 Project 2 Project 3
 -Associated Project ID
 -Subject ID in Project
 -Project ID
 Project Name
 Project Information
 Subjects
Subject 1 Subject 2
 -Subject ID
 -Subject ID in Project
Administrator
LabMember
Home Page
Subjects List / Subject Details
(Admin only) Search Subjects (Admin Only)
Home Page
Search ScanProjects List Projects List
Project Details / Scan Session
(View Only )
Project Detail / Scan Session
(Editable)
Administrator View (A) Lab Member View (L) Both (B)
Home Page
1A – Has ‘Subjects’ and ‘Admin
Options’ navigation options
1L – No ‘Subjects’ and ‘Admin Options’
navigation options
1B.1 – Update number when database
has been edited
1B.2 – User information and project
accessibility
Projects List
2A.1 – Add a new project
2A.2 – Direct to Project Details page
2L.1 – Cannot add a new subject
2L.2 – Disable button for projects staff has
no permission to access
2B.1 – Search for project
Subjects List /
Subject Details
3A.1 - Direct to subject’s detail page
3A.2 - Add a new subject.
3A.3 - Edit/delete this subject
3A.4 - Direct to Scan Session page
No access to subjects demographic
information
N/A
Search Pages
4A.1 – Allow search based on subject
info
4L.1 – Disable search of subjects based on
demographic information
4B.1 - Select specific scan and export
to Excel Spreadsheet
4B.2 - Pops up search criteria
Accessibility to each project is divided into “View Only” and “Editable” categories:
View Only Editable
5.1 & 5.3 - Edit/delete project and associated scans No Yes
5.2 – Add subject to project No Yes
5.3 – Export scan data to Excel Spreadsheet Yes Yes
1A 1L
1B.1
1B.2
1B.1
1B.2
2B.1
2A.1
2L.12B.1
2A.2 2L.2
3A.2
3A.1
3A.3
3A.4
4A.1
4B.1
4B.2
4B.1
5.1
5.2
5.3
5.1
5.1
5.1
5.2
5.3
4L.1
4B.2