Database Systems Usability Challenges and Solutions
This presentation delves into various aspects of making database systems usable, covering topics such as forms, natural language interfaces, and provenance work. Explore the pros, cons, and implications of different approaches in improving database usability. Gain insights into the complexities and limitations faced in querying databases effectively.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Making Database Systems Usable Slides courtesy Jagadish
This paper Unusual, provocative paper More problems than solutions A showcase of the work the group has done Naturally, very far from solving the problems Better to judge the paper for the questions it raises rather than the solutions it provides!
Forms Simple, but limited. How do we create a form to query a database? When would it be appropriate to use? Discuss!
Forms Simple, but limited. How do we create a form to query a database? When would it be appropriate to use? Discuss! Small number of types of queries Small number of predicates Small number of joins Possibly many values for attributes Conceptual schema need not be same as actual schema (e.g., flight database)
Natural Language Interfaces Pros/Cons?
Natural Language Interfaces Pros/Cons? No need for SQL: But not clear how much one can do without knowledge of schema Only short queries Probably a wider space of queries than forms Sometimes can be annoying Imagine having to specify flight searches via NL The feeling of less control Lack of understanding of knobs
Lots of work on Provenance Fine grained store origin of every single record Coarse grained store at a schema level: this table came from these two tables Pros/Cons?
Lots of work on Provenance Fine grained store origin of every single record Coarse grained store at a schema level: this table came from these two tables Pros/Cons? Fine-grained: too much data: all-all mappings Coarse-grained: cannot ask interesting questions
