Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

K. A. Kaufman

dblp:02/5239 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 1986
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 2

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
2 papers
Data integration and cleaning · 38% Information retrieval · 22% Distributed and cloud data management · 17%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%

Topics — the 7 heaviest of 7, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Data integration and cleaning
heterogeneous data integration
0.021986
Report Generation Facility, A High-Level Interface for Coherent Access to Heterogeneous Database Systems · ICDE 1986
Mutual Consistency Maintenance in A Prototype Data Trafic Management System · ICDE 1984
Information retrieval › cross-language information retrieval
query translation
0.011986
Report Generation Facility, A High-Level Interface for Coherent Access to Heterogeneous Database Systems · ICDE 1986
Distributed and cloud data management
data replication
0.011984
Mutual Consistency Maintenance in A Prototype Data Trafic Management System · ICDE 1984
Transaction processing and concurrency control › consistency
mutual consistency
0.011984
Mutual Consistency Maintenance in A Prototype Data Trafic Management System · ICDE 1984
Data models and query languages
natural language interface
0.011986
Report Generation Facility, A High-Level Interface for Coherent Access to Heterogeneous Database Systems · ICDE 1986
Distributed systems
replication
0.011984
Mutual Consistency Maintenance in A Prototype Data Trafic Management System · ICDE 1984
Distributed systems › replication
update propagation
0.011984
Mutual Consistency Maintenance in A Prototype Data Trafic Management System · ICDE 1984
YearPublicationVenuePosition
1986 Report Generation Facility, A High-Level Interface for Coherent Access to Heterogeneous Database Systems
abstract
The Report Generation Facility is a high-level interface designed and implemented to support coherent access of data stored in a number of stand-alone, independent, database systems served by it. Specifically, the Report Generation Facility provides a menu which allows a user to request one or more standard reports provided by the individual database systems and the Report Generation Facility, or to formulate a query in an English-like query language without having to specify where the requested data reside or how to retrieve them. The Report Generation Facility translates the user's request or query into subtransactions to the individual database systems and submits the substransactions in order to retrieve and format the data requested by the user. Thus, the Report Generation Facility provides a standard way to produce reports based on data stored in the database systems with minimal user effort and expertise. This paper describes its capabilities and architecture.
Geneva G. Belford, Jane W.-S. Liu, S. C. Hwung, Chi-Yin Huang Hsu, K. A. Kaufman, C. K. Kim, Jung K. Kim, J. Leo, Anthony V. Ma, J. Ng, D. Neff, J. Quinn, Sudha Ram, Y. L. Yan
ICDE5
1984 Mutual Consistency Maintenance in A Prototype Data Trafic Management System
abstract
This paper describes the mutual consistency maintenance mechanism used in a prototype Data Traffic Management System (DTMS), which was designed and implemented to integrate several independent and stand-alone data systems owned by the U. S. Army, Corp of Engineers (CE). The major design constraints were that no modification to the data systems involved were allowed and that the update to each duplicate copy was to be handled as automatically as possible and in a manner approved by the manager of the system containing the copy. The capabilities of the prototype DTMS and the Mutual Consistency Maintenance Subsystem are discussed. The linkage directory used to support mutual consistency maintenance and the mutual consistency maintenance mechanism are described.
Geneva G. Belford, Jane W.-S. Liu, D. Cho, P. Cotten, S. England, J. D. Goldstein, S. C. Hwung, K. A. Kaufman, C. K. Kim, J. Leo, A. P. Manolas, A. Moon, A. D. Smet, Y. L. Yan, G. L. Robinson, R. L. Lapp
ICDE8