Canada Spends Logo

Explorez notre analyse du budget 2026

Grant: Discovery Grants Program - Individual

University of British Columbia

$24,000.00

Improving schema understandability for semantic integration

EF 2014-15

Résumé
Databases are very complex; a typical database can store data in hundreds of tables and can contain hundreds of references between tables. The layout of the data into tables and references between them is referred to as a schema. Learning the details of these complex schemas requires significant time. This problem is exacerbated by data sources being shared across organizations, and users attempting to make their applications do something for which they were not originally designed. Consider the following two scenarios: (1) A user is integrating civil engineering data across a number of applications, including CAD models and project scheduling. The data in these applications can be exported via a number of different standards. In order to integrate the data, the user must first choose which standard to export from and then figure out how to understand how the data has been exported. (2) An end user has access to a database application that generates reports. The end user asks the database programmer to change the application to access more information than was originally accessible. The programmer has never seen the application before, but now must extend the application to access new data. This will require the programmer to understand how the data in the back-end database is stored well enough to write the new queries. Neither of these scenarios is adequately helped by existing approaches. I propose to improve schema understanding. The goal is to help users in a variety of scenarios including those above to make better use of the existing schemas that they are encountering for the first time, whether it is extending their understanding of a current application, trying to decide how to export their data to a standard schema (which is challenging since related data may be scattered across the standard schema, rendering it incomprehensible), or choosing a standard schema to which the data should adhere.
Programme
Discovery Grants Program - Individual
Emplacement
British Columbia, Canada
Type de bénéficiaire
Academia
Type
Grant
Source
NSERC's Awards Data

Tel que publié

Application id
312129-2011
Name nom
Pottinger, Rachel
Department département
Computer Science
Organization id
2
Institution établissement
University of British Columbia
Province en
British Columbia
Province fr
Colombie-Britannique
Country en
CANADA
Country fr
CANADA
Fiscal year exercice financier
2014
Competition year année de concours
2011
Award amount
24000
Program id
RGPIN
Program name en
Discovery Grants Program - Individual
Program name fr
Programme de subventions à la découverte - individuelles
Group en
Discovery grants programs
Group fr
Programmes de subventions à la découverte
Committee code
1507
Committee name en
Computer Science
Committee name fr
Sciences informatiques
Area of application code
801
Area of application group en
Information and communication services
Area of application group fr
Services d'information et de télécommunications
Area of application en
Computer software
Area of application fr
Logiciel
Research subject code
2711
Research subject group en
Information technology
Research subject group fr
Technologie de l'information
Research subject en
Database management
Research subject fr
Gestion de bases de données
Partie
4
Nb partie
5
Application title
Improving schema understandability for semantic integration
Keyword
NSERC
Application summary
Databases are very complex; a typical database can store data in hundreds of tables and can contain hundreds of references between tables. The layout of the data into tables and references between them is referred to as a schema. Learning the details of these complex schemas requires significant time. This problem is exacerbated by data sources being shared across organizations, and users attempting to make their applications do something for which they were not originally designed. Consider the following two scenarios: (1) A user is integrating civil engineering data across a number of applications, including CAD models and project scheduling. The data in these applications can be exported via a number of different standards. In order to integrate the data, the user must first choose which standard to export from and then figure out how to understand how the data has been exported. (2) An end user has access to a database application that generates reports. The end user asks the database programmer to change the application to access more information than was originally accessible. The programmer has never seen the application before, but now must extend the application to access new data. This will require the programmer to understand how the data in the back-end database is stored well enough to write the new queries. Neither of these scenarios is adequately helped by existing approaches. I propose to improve schema understanding. The goal is to help users in a variety of scenarios including those above to make better use of the existing schemas that they are encountering for the first time, whether it is extending their understanding of a current application, trying to decide how to export their data to a standard schema (which is challenging since related data may be scattered across the standard schema, rendering it incomprehensible), or choosing a standard schema to which the data should adhere.