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

Laura Mota-Herranz

dblp:19/1441 · also Laura Mota · DBLP profile ↗
← Back
4ranked-venue papers
2as first author
0since 2021 · last 2000
—ORCID · none

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

Databases, data management, data science and information retrieval · 4 · 2 first-authorArtificial intelligence and machine learning · 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
Database theory · 100%

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

TopicWeightPapersLastEvidence papers
Database theory
deductive database
0.011994
Comparing and Synthesizing Integrity Checking Methods for Deductive Databases · ICDE 1994
Database theory › integrity constraints
integrity constraint checking
0.011994
Comparing and Synthesizing Integrity Checking Methods for Deductive Databases · ICDE 1994

Methods — techniques the papers use, named apart from their topics

metaprogramming · 0.0fact access analysis · 0.0
YearPublicationVenuePosition
2000 Transaction Trees for Knowledge Revision
abstract
For each view predicate, a Transaction Tree (T-tree) can be derived from a database schema. T-trees are data structures which serve to anticipate transactions by which view update requests can be translated to updates of underlying base relations. Since T-trees are obtained at schema specification time, i.e. in advance of update time, they provide a basis for planning strategies with which appropriate transactions can be chosen to satisfy view update requests, and also for strategies which support schema evolution. The main features of the approach are that it is simple, it offers solutions to the problem of missing values, it is correct and it is complete (in the case of nonrecursive views).
Laura Mota-Herranz, Matilde Celma, Hendrik Decker
FQAS1
1998 Automatic Generation of Trigger Rules for Integrity Enforcement in Relational Databases with View Definition
Laura Mota-Herranz, Matilde Celma
FQAS1
1994 Comparing and Synthesizing Integrity Checking Methods for Deductive Databases
abstract
We compare and synthesize different methods for integrity checking in deductive databases. First, we state simplified integrity checking for deductive databases independently of the particular strategy used by different methods found in the literature. In accordance with this statement, we classify integrity checking methods into two main groups: methods with a generation phase without fact access and methods with a generation phase with fact access. Then, we propose an implementation scheme (a metaprogram) where the differences and similarities among the methods can be pointed out. In this common implementation framework, we compare the methods; this comparison is based on the number of facts accessed by each of them during integrity checking. Finally and from the analysis of the results, we define a convergence method which synthesizes some different features from several methods.>
Matilde Celma, Laura Mota-Herranz, Hendrik Decker
ICDE3
1992 Foundations of Simplified Integrity Checking Reviewed
Matilde Celma, Laura Mota-Herranz
DEXA2