<?xml version="1.0" encoding="utf-8"?>
<export-example>
  <doc>
    <id>3721</id>
    <completedYear/>
    <publishedYear>2017</publishedYear>
    <thesisYearAccepted/>
    <language>eng</language>
    <pageFirst>2462</pageFirst>
    <pageLast>2471</pageLast>
    <pageNumber/>
    <edition/>
    <issue/>
    <volume/>
    <type>conferenceobject</type>
    <publisherName>IEEE</publisherName>
    <publisherPlace/>
    <creatingCorporation/>
    <contributingCorporation/>
    <belongsToBibliography>0</belongsToBibliography>
    <completedDate>--</completedDate>
    <publishedDate>--</publishedDate>
    <thesisDateAccepted>--</thesisDateAccepted>
    <title language="eng">Uncovering the evolution history of data lakes</title>
    <abstract language="eng">Data accumulating in data lakes can become inaccessible in the long run when its semantics are not available. The heterogeneity of data formats and the sheer volumes of data collections prohibit cleaning and unifying the data manually. Thus, tools for automated data lake analysis are of great interest. In this paper, we target the particular problem of reconstructing the schema evolution history from data lakes. Knowing how the data is structured, and how this structure has evolved over time, enables programmatic access to the lake. By deriving a sequence of schema versions, rather than a single schema, we take into account structural changes over time. Moreover, we address the challenge of detecting inclusion dependencies. This is a prerequisite for mapping between succeeding schema versions, and in particular, detecting nontrivial changes such as a property having been moved or copied. We evaluate our approach for detecting inclusion dependencies using the MovieLens dataset, as well an adaption of a dataset containing botanical descriptions, to cover specific edge cases.</abstract>
    <parentTitle language="eng">2017 IEEE International Conference on Big Data (Big Data),,11-14 Dec. 2017, Boston, MA, USA</parentTitle>
    <identifier type="doi">10.1109/BigData.2017.8258204</identifier>
    <enrichment key="opus.import.date">2022-04-28T18:57:25+00:00</enrichment>
    <enrichment key="opus.source">sword</enrichment>
    <enrichment key="opus.import.user">importuser</enrichment>
    <enrichment key="BegutachtungStatus">peer-reviewed</enrichment>
    <licence>Keine Lizenz - Es gilt das deutsche Urheberrecht: § 53 UrhG</licence>
    <author>Meike Klettke</author>
    <author>Hannes Awolin</author>
    <author>Uta Störl</author>
    <author>Daniel Müller</author>
    <author>Stefanie Scherzinger</author>
    <author>Uta Storl</author>
    <author>Daniel Muller</author>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>Data mining</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>evolution operations</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>Grippers</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>history</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>inclusion dependencies</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>integrity constraints</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>Lakes</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>NoSQL databases</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>Protocols</value>
    </subject>
    <subject>
      <language>eng</language>
      <type>uncontrolled</type>
      <value>schema version extraction</value>
    </subject>
    <collection role="institutes" number="FakIM">Fakultät Informatik und Mathematik</collection>
    <collection role="othforschungsschwerpunkt" number="16311">Digitalisierung</collection>
  </doc>
</export-example>
