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
N1 - Publisher Copyright:
© 2017, Springer Science+Business Media, LLC.
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
U2 - 10.1007/s10619-017-7213-1
DO - 10.1007/s10619-017-7213-1
M3 - Article
AN - SCOPUS:85033563221
SN - 0926-8782
VL - 36
SP - 121
EP - 151
JO - Distributed and Parallel Databases
JF - Distributed and Parallel Databases
IS - 1
ER -