1990
DOI: 10.1016/s0020-7373(08)80005-3
|View full text |Cite
|
Sign up to set email alerts
|

No IFs, ANDs, or ORs: A study of database querying

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
51
3
1

Year Published

1993
1993
2005
2005

Publication Types

Select...
6
3

Relationship

0
9

Authors

Journals

citations
Cited by 74 publications
(58 citation statements)
references
References 14 publications
0
51
3
1
Order By: Relevance
“…It has been studied that it is generally more adequate to provide customers with fairly simple and easy to use search interfaces [7], whereas experts and content managers, who are aware of many internal information details, can benefit from more complex and powerful search facilities. This is supported in our platform by creating different templates for different user profiles and usage modes, thus enabling the creation of as large and varied an array of power levels and modalities as needed (see [12] for an overview of user interface approaches for searching), in a highly modular way, very easy to extend.…”
Section: Information Searchmentioning
confidence: 99%
“…It has been studied that it is generally more adequate to provide customers with fairly simple and easy to use search interfaces [7], whereas experts and content managers, who are aware of many internal information details, can benefit from more complex and powerful search facilities. This is supported in our platform by creating different templates for different user profiles and usage modes, thus enabling the creation of as large and varied an array of power levels and modalities as needed (see [12] for an overview of user interface approaches for searching), in a highly modular way, very easy to extend.…”
Section: Information Searchmentioning
confidence: 99%
“…In a review of previous experiments (for example, Greene et al [23] and Michard [37]), Young and Shneiderman [53] note that a common error in textual query languages is that of using the logical AND operator as opposed to the logical OR operator when translating from English sentences. They also note that users found it dif®cult to specify precedence in query expressions due to``parenthesis complexity'' [39].…”
Section: General Database Issuesmentioning
confidence: 99%
“…They also note that users found it dif®cult to specify precedence in query expressions due to``parenthesis complexity'' [39]. Syntactical errors are also a problem in query languages [23], [38], [44], [50], [53]. In their evaluations, Young and Shneiderman [53] chose not to rate queries with syntax errors as incorrect, and Reisner [44] categorized these types of errors as``minor'' and placed them under the banner`e ssentially correct'' queries.…”
Section: General Database Issuesmentioning
confidence: 99%
“…Prototype applications have been used in usability tests of database query languages [6]. However, these experiments were undertaken when the languages were already commercially available and, therefore, too late to influence SQL design materially.…”
Section: Previous Workmentioning
confidence: 99%