1986
DOI: 10.1145/27633.27634
|View full text |Cite
|
Sign up to set email alerts
|

A comparative analysis of methodologies for database schema integration

Abstract: One of the fundamental principles of the database approach is that a database allows a nonredundant, unified representation of all data managed in an organization. This is achieved only when methodologies are available to support integration across organizational and application boundaries.Methodologies for database design usually perform the design activity by separately producing several schemas, representing parts of the application, which are subsequently merged. Database schema integration is the activity… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
591
0
25

Year Published

1998
1998
2011
2011

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 1,270 publications
(616 citation statements)
references
References 36 publications
0
591
0
25
Order By: Relevance
“…There is a broad array of related work including form-driven database generation [11], DIY web services for form creation [1] schema mapping [20], view integration [7], schema evolution [26], and automatic understanding of Deep Web search interfaces [17]. However, the problem that we address here is a new and has not been addressed before in totality.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…There is a broad array of related work including form-driven database generation [11], DIY web services for form creation [1] schema mapping [20], view integration [7], schema evolution [26], and automatic understanding of Deep Web search interfaces [17]. However, the problem that we address here is a new and has not been addressed before in totality.…”
Section: Related Workmentioning
confidence: 99%
“…Schema mapping aims to discover meaningful relationships between database schemas [20,21,23,5], while view/schema integration builds a database schema by unifying a set of views/schemas [7]. Both problems primarily focus on schema elements and do not consider database extension.…”
Section: Related Workmentioning
confidence: 99%
“…For the purposes of this study, we took data on projects and grants from RCs in three domains: engineering and physical sciences (EPSRC) 3 , biotechnology and biological sciences (BBSRC) 4 , and medicine (MRC) 5 . These RCs were chosen because their funding activities overlap in an area known as the Life Sciences Interface, which supports interdisciplinary research between engineering and physical sciences, and the life sciences.…”
Section: Data Gatheringmentioning
confidence: 99%
“…Integration of databases raises several well known challenges, such as resolving the conceptual differences between database schemas, identifying data duplications and inconsistencies, etc [4]. Ontologies have been widely proposed as a major role player in information integration [7][14] [15].…”
Section: Introductionmentioning
confidence: 99%
“…Moreover, these semantic differences can cause different kinds of conflicts, ranging from simple contradictions in name use (when different names are used by different sources to indicate the same or similar real-world concept), to structural conflicts (when different models/primitives are used to represent the same information). Complicating factors with respect to conventional view integration techniques [4] are related to the fact that semantic heterogeneity occurs on the large-scale. This heterogeneity involves terminology, structure, and domain of the sources, with respect to geographical, organizational, and functional aspects of the information use [48].…”
mentioning
confidence: 99%