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
Demo Data from EDBT 2026 / reviewers in the wild / expert

Steve Hartley

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

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

Software 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.

Computer architecture, parallel and distributed computing, and storage systems
1 paper
Storage systems · 100%
Software engineering, system software, and programming languages
1 paper
Services computing and microservices · 100%

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

TopicWeightPapersLastEvidence papers
Storage systems › data management
object database		 0.011994
Persistent Storgage for a Workflow Tool Implemented in Smalltalk · OOPSLA 1994
Storage systems › storage architecture
persistent storage		 0.011994
Persistent Storgage for a Workflow Tool Implemented in Smalltalk · OOPSLA 1994
Services computing and microservices
workflow management		 0.011994
Persistent Storgage for a Workflow Tool Implemented in Smalltalk · OOPSLA 1994

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

object-relational coexistence · 0.0
YearPublicationVenuePosition
1994 Persistent Storgage for a Workflow Tool Implemented in Smalltalk
abstract
This paper describes a new workflow model and its implementation in Smalltalk. The paper also details problems with using a RDBMS as the persistent store for the workflow tool and the subsequent experiences in using an ODBMS for this purpose. The final solution was a coexistence approach, using the RDBMS for legacy corporate data and the ODBMS for the process description and workflow status data.
Bob Beck, Steve Hartley
 OOPSLA2