Advertisement

Tracing Data Lineage Using Automed Schema Transformation Pathways

Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2405)

Abstract

Data warehousing is being increasingly used for integrating distributed, heterogeneous data in order to enable sophisticated analysis of this data. Automed is a database transformation and integration system supporting both virtual and materialized integration of schemas expressed in a variety of modelling languages [9,5,6]. Automed has as its a common data model a low-level hypergraph data model (HDM), and a set of primitive schema transformations operate on HDM schemas. An HDM schema consists of a set of nodes, edges and constraints. The primitive transformations add, delete, and rename a node, edge or constraint. The addNode and addEdge transformations include a query which defines the extent of the new schema construct in terms of the extents of the existing schema constructs (so adding the construct does not change the information content of the schema). Similarly, the delNode and delEdge transformations include a query which shows how the extent of the deleted construct can be reconstructed from the remaining schema constructs.

Keywords

Data Lineage Transformation Language Source Database Transformation Step Schema Transformation 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    M. Boyd and N. Tong. The Automed repositories and API. Technical report, Automed Project, 2001.Google Scholar
  2. 2.
    P. Buneman, S. Khanna, and W.C. Tan. Why and Where: A characterization of data provenance. In Proc. ICDT 2001, pages 316–33, 2001.Google Scholar
  3. 3.
    Y. Cui, J. Widom, and J.L. Wiener. Tracing the lineage of view data in a warehousing environment. ACM TODS, 25(2):179–227, 2000.CrossRefGoogle Scholar
  4. 4.
    H. Fan and A. Poulovassilis. Tracing Data Lineage Using Automed Schema Transformation Pathways. Technical report, Automed Project, 2002. BBKCS-02-07.Google Scholar
  5. 5.
    P. McBrien and A. Poulovassilis. Automatic migration and wrapping of database applications-A schema transformation approach. In Proc. ER’99, pages 96–133, 1999.Google Scholar
  6. 6.
    P. McBrien and A. Poulovassilis. A uniform approach to inter-model transformations. In Proc. CAiSE’99, pages 333–348, 1999.Google Scholar
  7. 7.
    A. Poulovassilis. An enhanced transformation language for the HDM. Technical report, Automed Project, 2001.Google Scholar
  8. 8.
    A. Poulovassilis. The Automed Intermediate Query Language. Technical report, Automed Project, 2001.Google Scholar
  9. 9.
    A. Poulovassilis and P. McBrien. A general formal framework for schema transformation. Data and Knowledge Engineering, 28(1):47–71, 1998.zbMATHCrossRefGoogle Scholar
  10. 10.
    N. Tong. Database schema transformation optimisation techniques for the Automed system. Technical report, Automed Project, 2002.Google Scholar
  11. 11.
    A. Woodruff and M. Stonebraker. Supporting fine-grained data lineage in a database visualization environment. In Proc ICDE’97, pages 91–102, 1997.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2002

Authors and Affiliations

  • Hao Fan
    • 1
  1. 1.School of Computer Science and Information Systems, Birkbeck CollegeUniversity of LondonLondon

Personalised recommendations