Publications by Sukriti Ramesh

×

Status message

The Publications site is currently under construction, as a result some publications might be missing.

2012

January 2012
@techreport{abc,
	author = {Anja Gruenheid and Donald Kossmann and Sukriti Ramesh and Florian Widmer},
	title = {Crowdsourcing Entity Resolution: When is A=B?},
	year = {2012}
}

2011

Proceedings of the ACM SIGMOD International Conference on Management of Data, SIGMOD 2011, Athens, Greece, June 2011
@inproceedings{abc,
	author = {Michael J. Franklin and Donald Kossmann and Tim Kraska and Sukriti Ramesh and Reynold Xin},
	booktitle = {Proceedings of the ACM SIGMOD International Conference on Management of Data, SIGMOD 2011, Athens, Greece},
	title = {CrowdDB: answering queries with crowdsourcing.},
	url = {http://doi.acm.org/10.1145/1989323.1989331},
	year = {2011}
}
Systems Group Master's Thesis, no. 2; Department of Computer Science, April 2011
Supervised by: Prof. Donald Kossmann
Despite the advances in the areas of databases and information retrieval, there still remain certain types of queries that are difficult to answer using machines alone. Such queries require human interaction to either provide data that is not readily available to machines or to gain more information from existing electronic data. CrowdDB is a database system that enables difficult queries to be answered by using crowdsourcing to integrate human knowledge with electronically available data. To a large extent, the concepts and capabilities of traditional database systems are leveraged in CrowdDB. Despite the commonalities, since CrowdDB deals with procuring and utilizing human input, several existing capabilities of traditional database systems require modifications and extensions. Much unlike electronically available data, human input provided by crowdsourcing is unbounded and virtually infinite. Accordingly, CrowdDB is a system based on an open-world assumption. An extension of SQL, termed as Crowd- SQL, is used to model data and manipulate it. CrowdSQL is also used as the language to express complex queries on the integrated data sources. Furthermore, interaction with the crowd in CrowdDB requires an additional component that governs automatic user interface generation, based on available schemas and queries. Also, performance acquires a new meaning in the context of a system such as CrowdDB. Response time (efficiency), quality (effectiveness) and cost (in $) in CrowdDB are dependent on a number of different parameters including the availability of the crowd, financial rewards for tasks and state of the crowdsourcing platform. In this thesis, we propose the design, architecture and functioning of CrowdDB. In addition, we present the details of building such a system on an existing Java-based database, H2. The design and functionalities of CrowdDB have also been presented in [13].
@mastersthesis{abc,
	abstract = {Despite the advances in the areas of databases and information retrieval, there still remain certain
types of queries that are difficult to answer using machines alone. Such queries require human interaction
to either provide data that is not readily available to machines or to gain more information from
existing electronic data.
CrowdDB is a database system that enables difficult queries to be answered by using crowdsourcing
to integrate human knowledge with electronically available data. To a large extent, the concepts
and capabilities of traditional database systems are leveraged in CrowdDB. Despite the commonalities,
since CrowdDB deals with procuring and utilizing human input, several existing capabilities of
traditional database systems require modifications and extensions. Much unlike electronically available
data, human input provided by crowdsourcing is unbounded and virtually infinite. Accordingly,
CrowdDB is a system based on an open-world assumption. An extension of SQL, termed as Crowd-
SQL, is used to model data and manipulate it. CrowdSQL is also used as the language to express
complex queries on the integrated data sources. Furthermore, interaction with the crowd in CrowdDB
requires an additional component that governs automatic user interface generation, based on available
schemas and queries. Also, performance acquires a new meaning in the context of a system such as
CrowdDB. Response time (efficiency), quality (effectiveness) and cost (in $) in CrowdDB are dependent
on a number of different parameters including the availability of the crowd, financial rewards for
tasks and state of the crowdsourcing platform. In this thesis, we propose the design, architecture and
functioning of CrowdDB. In addition, we present the details of building such a system on an existing
Java-based database, H2. The design and functionalities of CrowdDB have also been presented in
[13].
},
	author = {Sukriti Ramesh},
	school = {2},
	title = {CrowdDB \&$\#$150; Answering Queries with Crowdsourcing},
	year = {2011}
}
PVLDB, January 2011
@inproceedings{abc,
	author = {Amber Feng and Michael J. Franklin and Donald Kossmann and Tim Kraska and Samuel Madden and Sukriti Ramesh and Andrew Wang and Reynold Xin},
	booktitle = {PVLDB},
	title = {CrowdDB: Query Processing with the VLDB Crowd},
	url = {http://www.vldb.org/pvldb/vol4/p1387-feng.pdf},
	year = {2011}
}