Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared...
-
Upload
kelley-andrews -
Category
Documents
-
view
224 -
download
0
Transcript of Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared...
![Page 1: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/1.jpg)
Data Integration Progress
![Page 2: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/2.jpg)
BIRN Data Integration Framework
2. Create conceptual links to a shared ontology
1. Create multimodal databases
3. Situate the data in a common spatial framework
4. Use mediator to navigate and query across data sources
![Page 3: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/3.jpg)
Data Integration Deployment & Utilization
• Significant events in last year related to BIRN data integration progress– Test bed database availability– BIRNLex and BIRN ontology development– Hardening of data integration environment
• Enhanced production deployment of BIRN Data Integration Environment as part of BIRN 3.0 release– Enhancements driven by distributed queries against BIRN data
sources– Significant performance improvements
• Deployment in the BIRN test beds– Mouse BIRN - Utilization within atlasing environment (i.e. MBAT and
SmartAtlas)– Function BIRN - Queries across fBIRN HID databases, addition of
BrainMap
![Page 4: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/4.jpg)
BIRN CC – Test Bed Data Integration Deployment
• Function BIRN– Vadim Astakhov, David Little, Edward Ross, Daniel Wei, Vicky
Rowley, David Keator (fBIRN/UCI), Dingying Wei (fBIRN/UCI), Burak Ozyurt (fBIRN/UCSD), Angie Laird/Angela Uecker (BrainMap)
• Mouse BIRN– Vadim Astakhov, Brian Sanders, Daniel Wei, Steve Anderson (Mouse
BIRN/UCLA), Bill Bug (Mouse BIRN/Drexel), Asif Memon (Mouse BIRN/UCSD), Heng Yuan (Mouse BIRN/UCLA)
• Morphometry BIRN– Vadim Astakhov, David Little, Daniel Wei, Dan Marcus (Morphometry
BIRN/WUSTL)
![Page 5: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/5.jpg)
Data Integration Utilization
• With BIRN 3.0 release, have begun tracking utilization of data integration environment
• In first month of tracking - more than 2,000 queries were issued
![Page 6: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/6.jpg)
Data Integration Sources
• Data integration team has worked closely with test beds to register databases from testbeds
• Registration of external data sources (e.g. BrainMap)
• Driven by test bed requirements
![Page 7: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/7.jpg)
Access to Data Integration Environment
• Tool Developers
• Data Integration Specialists
• Domain Scientists
Web Services
Data Integration Tools
Concept Based Visual Query Environment
![Page 8: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/8.jpg)
Data Integration Services
• Data Integration Environment accessible through web service interface
• Driven by requirements and direct interaction with test beds
• Utilization in Mouse BIRN Atlas Environments (e.g. MBAT)
• Services being deployed for Human Imaging Database
![Page 9: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/9.jpg)
BIRN Data Integration Tools
• Three core data integration tools hardened and made available through the BIRN Portal
• Database Registration
• Integrated View Construction
• Query Development and Execution
![Page 10: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/10.jpg)
Concept Based User Interface
• Has been developed based on feedback from community at Ontology boot-camp and test bed AHMs
• Provides access to BIRN ontological sources
• Allows for the construction of queries based on familiar concepts - architecture handles the generation of integrated vies
![Page 11: Data Integration Progress. BIRN Data Integration Framework 2. Create conceptual links to a shared ontology 1. Create multimodal databases 3. Situate the.](https://reader030.fdocuments.in/reader030/viewer/2022032611/56649f455503460f94c66bff/html5/thumbnails/11.jpg)
Evolution of the BIRN Data Integration Environment
• BIRN mediator has evolved significantly in response to emerging technologies and user requirements/preferences
– Two development streams: mediator and source database
• Initially our only way of querying integrated data was based on a query form– Downside: users had to know the integrated schema– Upside: Many really complex queries can be formulated
• Users wanted– A simple keyword style query interface– An ontology augmented keyword style query interface
• Extension Developed– Created a new mechanism to accept a set of keywords– Automatically construct an integrated query– Provide users choices of the results they want back
1999 2004 2006