Abstract
Data integration is an important step in integrating information from multiple sources. The problem is how to find and combine data from scattered data sources that are heterogeneous and have semantically informant interconnections optimally. The heterogeneity of data sources is the result of a number of factors, including storing databases in different formats, using different software and hardware for database storage systems, designing in different data semantic models (Katsis & Papakonstantiou, 2009, Ziegler & Dittrich , 2004). Nowadays there are two approaches in doing data integration that is Global as View (GAV) and Local as View (LAV), but both have different advantages and limitations so that proper analysis is needed in its application. Some of the major factors to be considered in making efficient and effective data integration of heterogeneous data sources are the understanding of the type and structure of the source data (source schema). Another factor to consider is also the view type of integration result (target schema). The results of the integration can be displayed into one type of global view or a variety of other views. So in integrating data whose source is structured the approach will be different from the integration of the data if the data source is not structured or semi-structured. Scheme mapping is a specific declaration that describes the relationship between the source scheme and the target scheme. In the scheme mapping is expressed in in some logical formulas that can help applications in data interoperability, data exchange and data integration. In this paper, in the case of establishing a patient referral center data center, it requires integration of data whose source is derived from a number of different health facilities, it is necessary to design a schema mapping system (to support optimization). Data Center as the target orientation schema (target schema) from various reference service units as a source schema (source schema) has the characterization and nature of data that is structured and independence. So that the source of data can be integrated tersetruktur of the data source into an integrated view (as a data center) with an equivalent query rewriting (equivalent). The data center as a global schema serves as a schema target requires a "mediator" that serves "guides" to maintain global schemes and map (mapping) between global and local schemes. Data center as from Global As View (GAV) here tends to be single and unified view so to be effective in its integration process with various sources of schema which is needed integration facilities "integration". The "Pemadu" facility is a declarative mapping language that allows to specifically link each of the various schema sources to the data center. So that type of query rewriting equivalent is suitable to be applied in the context of query optimization and maintenance of physical data independence.Keywords: Global as View (GAV), Local as View (LAV), source schema ,mapping schema
Highlights
As complete information from an application is often provided by many different and autonomous data sources as a reference in providing an integrated global scheme [1]
Arrange the data with different methods and methods such as web forms and database client. This makes the function of combining data from different sources is not easy to do and requires a stronger effort
The first step that must be done in doing data integration is to take separate data from each different source, memahi each data and linkage relationship
Summary
As complete information from an application is often provided by many different and autonomous data sources as a reference in providing an integrated global scheme [1]. Each user queries all objects related to the global schema the mediator will use query-reformulation procedure to translate the query into an executable sub query from all the schema sources involved in the query and reassemble the answer from each - the source of the schema to be further combined to answer the query. There are four main approaches to data integration: Local as View (LAV), Global as View (GV), Global Local as View (GLAV) and Both as View (BAV) All of these approaches are unmaterialized (virtual) in which it uses the definition of a view to determine the mapping between local schema and global schema. Mapping is used to translate queries that are expressed in the global schema framework to sub queries that are expressed in the local schema
Published Version (Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have