Demo Data from EDBT 2026 / reviewers in the wild / expert
Keith Waclena
dblp:97/4488
· DBLP profile ↗
3ranked-venue papers
0as first author
0since 2021 · last 1995
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 2Artificial intelligence and machine learning · 1Software engineering, systems software and programming languages · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Databases, data mining, and information retrieval
1 paper |
Information retrieval · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Information retrieval › document processing › document analysis
document structure |
0.0 | 1 | 1992 | A Textual Object Management System · SIGIR 1992 |
Information retrieval › search engines
full-text search |
0.0 | 1 | 1992 | A Textual Object Management System · SIGIR 1992 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1995 | Funser: A Functional Server for Textual Information RetrievalabstractAbstract This paper describes a data-intensive application written in a lazy functional language: a server for textual information retrieval. The design illustrates the importance of interoperability, the capability of interacting with code written in other programming languages. Lazy functional programming is shown to be a powerful and elegant means of accomplishing several desirable concrete goals: delivering initial results promptly, using space economically, and avoiding unnecessary I/O. Performance results, however, are mixed. Donald A. Ziff, Stephen P. Spackman, Keith Waclena |
J. Funct. Program. | 3 |
| 1992 | A Textual Object Management SystemabstractComputer programs that access significant amounts of text usually include code that manipulates the textual objects that comprise it. Such programs include electronic mail readers, typesetters and, in particular, full-text information retrieval systems. Such code is often unsatisfying in that access to textual objects is either efficient, or flexible, but not both. A programming language like Awk or Perl provides very general facilities for describing textual objects, but at the cost of rescanning the text for every textual object. At the other extreme, full-text information retrieval systems usually offer access to a very limited number of kinds of textual objects, but this access is very efficient. The system described in this paper is a programming tool for managing textual objects. It provides a great deal of flexibility, giving access to very complex document structure, with a large number of constituent kinds of textual objects. Further, it provides access to these objects very efficiently, both in terms of time and auxiliary space, by being very careful to access secondary storage only when absolutely necessary. Scott C. Deerwester, Keith Waclena, Michelle LaMar |
SIGIR | 2 |
| 1990 | An Architecture for Full Text Retrieval Systems
Scott C. Deerwester, Donald A. Ziff, Keith Waclena |
DEXA | 3 |