This chapter discusses Stardog Studio - the IDE for the Knowledge Graph Engineer designed to make Stardog functionality easier for everyday users.
Stardog Studio is the IDE for the Knowledge Graph Engineer designed to make Stardog functionality easier for everyday users.
Aside from administering Stardog clusters, almost all functionality that exists through the CLI and other APIs is available in Studio, and most non-admin users are able to use Studio without need for the command line.
To authenticate using Kerberos, both the Stardog server and your browser must be correctly configured. Check out the documentation on how.
Studio’s UI is split into the sections below.
This is not a comprehensive list of functionality but a general summary of functionality in each section.
- Get a high-level overview of your knowledge graph
- Visualize connections between data sources (including virtualized sources) and entities in your data
- Write, execute, and see query plans for queries in SPARQL and GraphQL
- Interact with constraints and rules in SHACL and Stardog Rules Syntax
- Edit RDF with TriG and Turtle
- Edit Virtual Graph mappings with Stardog Mapping Syntax
- See query plans
- Visualize query results as nodes and edges
- Create and edit Stored Queries
- Visualize your schema
- Create and edit OWL- and RDFS-defined schemas in a form-based experience
- Write, edit, and validate constraints
- Create and configure virtual graphs and virtual graph mappings
- Create and configure data sources
- Manage databases
- Update database properties and namespaces
- See and kill running queries
- Load and remove data
- Manage GraphQL Schemas
- Manage BI Mapping
- Create users and roles
- Assign permissions to users and roles
If your Stardog server users and roles are managed through LDAP, Stardog Studio will restrict the creation of users and assigning of roles. From the Security hub, admins will only have the ability to manage permissions for users and roles.
Stardog Studio has a number of preferences that can be set based on user choice.
To change a preference:
- Open Studio’s preferences with the following keyboard shortcuts.
Meta + ,. The meta key is likely
Update the preference attribute to the desired value.
- Save your preferences - the theme should immediately take effect.
Meta s. The meta key is likely
|Preference||Description||Default Value||Additional notes|
|editorFontSize||Font size of all editor inputs.||14|
|labelPredicatesByDatabase||Label predicates order for search and visualization. These must be the full URI.|
|modelsBaseIriByDatabase||Base IRI for creating new items in the Models Hub. This must be the full IRI.|
|queryLimit||The LIMIT to apply (specifying maximum number of results) to all non-CONSTRUCT/DESCRIBE SPARQL queries run inside of Studio.||1000||If set to 0, this preference will be ignored. The maximum limit is 50000.|
|theme||Studio color theme. If ||“dark”|
For questions, comments, or feature requests, please post in the Studio section of the Stardog Community.
The Stardog blog includes post about new Studio functionality. All of those posts are available under the Studio Tag.
The parsers used by Stardog Studio are available on Github. These provide support for all of the languages supported by Studio, from the standards like SPARQL and Turtle to Stardog specific syntaxes like SMS.
To improve Stardog Studio, we collect anonymous usage data. We only collect information like session duration, feature usage, and the size of queries and results. We never collect the actual content of queries or results. To opt-out, set
false in your Preferences. You can access your preferences using the following keyboard shortcuts:
Meta + ,. The meta key is likely