EDBT 2026 Demo / reviewers in the wild / expert
Gaurav Vijayvargiya
dblp:90/2948
· DBLP profile ↗
3ranked-venue papers
0as first author
0since 2021 · last 2005
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 3
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Databases, data mining, and information retrieval
3 papers |
Data integration and cleaning · 53% Information retrieval · 18% Query processing and optimization · 18% |
Topics — the 4 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Data integration and cleaning › table understanding › table annotation
annotation management |
0.1 | 2 | 2005 | An annotation management system for relational databases · VLDB J. 2005 An Annotation Management System for Relational Databases · VLDB 2004 |
Information retrieval
annotation propagation |
0.1 | 1 | 2005 | DBNotes: a post-it system for relational databases based on provenance · SIGMOD Conference 2005 |
Data integration and cleaning
data provenance |
0.1 | 1 | 2005 | DBNotes: a post-it system for relational databases based on provenance · SIGMOD Conference 2005 |
Database system architecture and tuning
relational database system |
0.0 | 2 | 2005 | DBNotes: a post-it system for relational databases based on provenance · SIGMOD Conference 2005 An Annotation Management System for Relational Databases · VLDB 2004 |
Methods — techniques the papers use, named apart from their topics
provenance-based annotation propagation · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2005 | DBNotes: a post-it system for relational databases based on provenanceabstractWe demonstrate DBNotes, a Post-It note system for relational databases where every piece of data may be associated with zero or more notes (or annotations). These annotations are transparently propagated along as data is being transformed. The method by which annotations are propagated is based on provenance (aka lineage): the annotations associated with a piece of data d in the result of a transformation consist of the annotations associated with each piece of data in the source where d is copied from. One immediate application of this system is to use annotations to systematically trace the provenance and flow of data. If every piece of source data is attached with an annotation that describes its address (i.e., origins), then the annotations of a piece of data in the result of a transformation describe its provenance. Hence, one can easily determine the provenance of data through a sequence of transformation steps simply by examining the annotations. Annotations can also be used to store additional information about data. Since a database schema is often proprietary, the ability to insert new information about data without having to change the underlying schema is a useful feature. For example, an error report could be attached to an erroneous piece of data, and this error report will be propagated to other databases along transformations, thus notifying other users of the error. Overall, the annotations on the result of a transformation can also provide an estimate on the quality of the resulting database. Laura Chiticariu, Wang Chiew Tan, Gaurav Vijayvargiya |
SIGMOD Conference | 3 |
| 2005 | An annotation management system for relational databases
Deepavali Bhagwat, Laura Chiticariu, Wang Chiew Tan, Gaurav Vijayvargiya |
VLDB J. | 4 |
| 2004 | An Annotation Management System for Relational Databases
Deepavali Bhagwat, Laura Chiticariu, Wang Chiew Tan, Gaurav Vijayvargiya |
VLDB | 4 |