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

Kai Dauberschmidt

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

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

Databases, data management, data science and information retrieval · 1 · 1 since 2021

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 system architecture and tuning · 50% Data models and query languages · 50%
Software engineering, system software, and programming languages
1 paper
Software maintenance and evolution · 100%

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

TopicWeightPapersLastEvidence papers
Data models and query languages › schema languages
JSON Schema
0.512021
Josch: Managing Schemas for NoSQL Document Stores · ICDE 2021
Software maintenance and evolution › software evolution
schema evolution
0.112021
Josch: Managing Schemas for NoSQL Document Stores · ICDE 2021
YearPublicationVenuePosition
2021 Josch: Managing Schemas for NoSQL Document Stores
abstract
NoSQL document stores have become vastly popular. One major selling point is their flexibility w.r.t. schema management: With MongoDB, developers can actually switch back-and-forth between operating in schema-free mode, and schema fixed mode, where all write operations are validated. In this tool demo, we present Josch, which integrates state-ofthe-art third-party tools to support novel workflows for NoSQL document stores: Using Josch, DevOps teams may (1) extract a JSON Schema declaration from the production data instance, (2) manually refactor the schema (e.g., to account for upcoming schema changes), and (3) compare the extracted and the refactored schema, on a semantic level, e.g., to ensure that the rewritten schema is a generalization. (4) Finally, they may register the refactored schema with the NoSQL document store for schema validation. Apart from supporting this and other practical use cases, one further contribution of our demo is that we reveal current blind spots in NoSQL schema management tools that inspire novel research questions.
Michael Fruth, Kai Dauberschmidt, Stefanie Scherzinger
ICDE2