COACT: a query interface language for collaborative databases

Khaleel Mershad, Qutaibah M. Malluhi, Mourad Ouzzani, Mingjie Tang, Michael Gribskov, Walid G. Aref, Deo Prakash

Research output: Contribution to journalArticle

Abstract

Data curation activities in collaborative databases mandate that collaborators interact until they converge and agree on the content of their data. In a previous work, we presented a cloud-based collaborative database system that promotes and enables collaboration and data curation scenarios. Our system classifies different versions of a data item to either pending, approved, or rejected. The approval or rejection of a certain version is done by the database Principle Investigators (or PIs) based on its value. Our system also allows collaborators to view the status of each version and help PIs take decisions by providing feedback based on their experiments and/or opinions. Most importantly, our system provided mechanisms for history tracking of different versions to trace the modifications and approval/rejection done by both collaborators and PIs on different versions of a data item. We labeled our system as Update-Pending-Approval model (or UPA). In this paper, we describe a high level SQL query interface language for PIs and collaborators to interact with the UPA framework. We define a set of UPA keywords that are used as a part of the history tracking mechanism to select specific versions of a data item, and a set of UPA options that select specific versions based on possible future decisions of PIs. We implemented our query interface mechanism on top of Apache Phoenix, taking into consideration that the UPA system was implemented on top of Apache HBase. We test the performance of the UPA query language by executing several queries that contain different complexity levels and discuss their results.

Original languageEnglish
Pages (from-to)121-151
Number of pages31
JournalDistributed and Parallel Databases
Volume36
Issue number1
DOIs
Publication statusPublished - 1 Mar 2018

Fingerprint

Query languages
Feedback
Data base
Language
Query
Experiments
Key words
Query language
Mandate
Scenarios
Experiment

Keywords

  • Collaborative databases
  • False positives and negatives
  • Query options
  • SQL
  • True values
  • Update authorization

ASJC Scopus subject areas

  • Software
  • Information Systems
  • Hardware and Architecture
  • Information Systems and Management

Cite this

Mershad, K., Malluhi, Q. M., Ouzzani, M., Tang, M., Gribskov, M., Aref, W. G., & Prakash, D. (2018). COACT: a query interface language for collaborative databases. Distributed and Parallel Databases, 36(1), 121-151. https://doi.org/10.1007/s10619-017-7213-1

COACT : a query interface language for collaborative databases. / Mershad, Khaleel; Malluhi, Qutaibah M.; Ouzzani, Mourad; Tang, Mingjie; Gribskov, Michael; Aref, Walid G.; Prakash, Deo.

In: Distributed and Parallel Databases, Vol. 36, No. 1, 01.03.2018, p. 121-151.

Research output: Contribution to journalArticle

Mershad, K, Malluhi, QM, Ouzzani, M, Tang, M, Gribskov, M, Aref, WG & Prakash, D 2018, 'COACT: a query interface language for collaborative databases', Distributed and Parallel Databases, vol. 36, no. 1, pp. 121-151. https://doi.org/10.1007/s10619-017-7213-1
Mershad, Khaleel ; Malluhi, Qutaibah M. ; Ouzzani, Mourad ; Tang, Mingjie ; Gribskov, Michael ; Aref, Walid G. ; Prakash, Deo. / COACT : a query interface language for collaborative databases. In: Distributed and Parallel Databases. 2018 ; Vol. 36, No. 1. pp. 121-151.
@article{e05706ed3b784b5284c4ae19e20c17b4,
title = "COACT: a query interface language for collaborative databases",
abstract = "Data curation activities in collaborative databases mandate that collaborators interact until they converge and agree on the content of their data. In a previous work, we presented a cloud-based collaborative database system that promotes and enables collaboration and data curation scenarios. Our system classifies different versions of a data item to either pending, approved, or rejected. The approval or rejection of a certain version is done by the database Principle Investigators (or PIs) based on its value. Our system also allows collaborators to view the status of each version and help PIs take decisions by providing feedback based on their experiments and/or opinions. Most importantly, our system provided mechanisms for history tracking of different versions to trace the modifications and approval/rejection done by both collaborators and PIs on different versions of a data item. We labeled our system as Update-Pending-Approval model (or UPA). In this paper, we describe a high level SQL query interface language for PIs and collaborators to interact with the UPA framework. We define a set of UPA keywords that are used as a part of the history tracking mechanism to select specific versions of a data item, and a set of UPA options that select specific versions based on possible future decisions of PIs. We implemented our query interface mechanism on top of Apache Phoenix, taking into consideration that the UPA system was implemented on top of Apache HBase. We test the performance of the UPA query language by executing several queries that contain different complexity levels and discuss their results.",
keywords = "Collaborative databases, False positives and negatives, Query options, SQL, True values, Update authorization",
author = "Khaleel Mershad and Malluhi, {Qutaibah M.} and Mourad Ouzzani and Mingjie Tang and Michael Gribskov and Aref, {Walid G.} and Deo Prakash",
year = "2018",
month = "3",
day = "1",
doi = "10.1007/s10619-017-7213-1",
language = "English",
volume = "36",
pages = "121--151",
journal = "Distributed and Parallel Databases",
issn = "0926-8782",
publisher = "Springer Netherlands",
number = "1",

}

TY - JOUR

T1 - COACT

T2 - a query interface language for collaborative databases

AU - Mershad, Khaleel

AU - Malluhi, Qutaibah M.

AU - Ouzzani, Mourad

AU - Tang, Mingjie

AU - Gribskov, Michael

AU - Aref, Walid G.

AU - Prakash, Deo

PY - 2018/3/1

Y1 - 2018/3/1

N2 - Data curation activities in collaborative databases mandate that collaborators interact until they converge and agree on the content of their data. In a previous work, we presented a cloud-based collaborative database system that promotes and enables collaboration and data curation scenarios. Our system classifies different versions of a data item to either pending, approved, or rejected. The approval or rejection of a certain version is done by the database Principle Investigators (or PIs) based on its value. Our system also allows collaborators to view the status of each version and help PIs take decisions by providing feedback based on their experiments and/or opinions. Most importantly, our system provided mechanisms for history tracking of different versions to trace the modifications and approval/rejection done by both collaborators and PIs on different versions of a data item. We labeled our system as Update-Pending-Approval model (or UPA). In this paper, we describe a high level SQL query interface language for PIs and collaborators to interact with the UPA framework. We define a set of UPA keywords that are used as a part of the history tracking mechanism to select specific versions of a data item, and a set of UPA options that select specific versions based on possible future decisions of PIs. We implemented our query interface mechanism on top of Apache Phoenix, taking into consideration that the UPA system was implemented on top of Apache HBase. We test the performance of the UPA query language by executing several queries that contain different complexity levels and discuss their results.

AB - Data curation activities in collaborative databases mandate that collaborators interact until they converge and agree on the content of their data. In a previous work, we presented a cloud-based collaborative database system that promotes and enables collaboration and data curation scenarios. Our system classifies different versions of a data item to either pending, approved, or rejected. The approval or rejection of a certain version is done by the database Principle Investigators (or PIs) based on its value. Our system also allows collaborators to view the status of each version and help PIs take decisions by providing feedback based on their experiments and/or opinions. Most importantly, our system provided mechanisms for history tracking of different versions to trace the modifications and approval/rejection done by both collaborators and PIs on different versions of a data item. We labeled our system as Update-Pending-Approval model (or UPA). In this paper, we describe a high level SQL query interface language for PIs and collaborators to interact with the UPA framework. We define a set of UPA keywords that are used as a part of the history tracking mechanism to select specific versions of a data item, and a set of UPA options that select specific versions based on possible future decisions of PIs. We implemented our query interface mechanism on top of Apache Phoenix, taking into consideration that the UPA system was implemented on top of Apache HBase. We test the performance of the UPA query language by executing several queries that contain different complexity levels and discuss their results.

KW - Collaborative databases

KW - False positives and negatives

KW - Query options

KW - SQL

KW - True values

KW - Update authorization

UR - http://www.scopus.com/inward/record.url?scp=85033563221&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=85033563221&partnerID=8YFLogxK

U2 - 10.1007/s10619-017-7213-1

DO - 10.1007/s10619-017-7213-1

M3 - Article

AN - SCOPUS:85033563221

VL - 36

SP - 121

EP - 151

JO - Distributed and Parallel Databases

JF - Distributed and Parallel Databases

SN - 0926-8782

IS - 1

ER -