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

R. L. Lapp

dblp:81/6537 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1984
—ORCID · none

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

Databases, data management, data science and information retrieval · 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
Distributed and cloud data management · 33% Transaction processing and concurrency control · 33% Data integration and cleaning · 33%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%

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

TopicWeightPapersLastEvidence papers
Distributed and cloud data management
data replication
0.011984
Mutual Consistency Maintenance in A Prototype Data Trafic Management System · ICDE 1984
Data integration and cleaning
heterogeneous data integration
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
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
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
ICDE17