OpenSPAD Administration Ontology Management
● Connecting to Neo4j… ← Back to Administration

Ontologies › Complete Suite Import

Enter one Core Ontology URI. OpenSPAD resolves the complete suite, reverse imports, dependencies and alignments before Neo4j import.

Suite Resolver Starts from one Core URI and searches for suite members that import the Core, explicit suite references, dependencies and alignment ontologies.
Maximum recursion depth

Drag & drop ontology file here

or click to browse

Supported: OWL, TTL, RDF/XML, JSON-LD Maximum file size: 50 MB

Import destination

Central Neo4j Database Suite, ontologies, classes, properties, imports and alignments are persisted.
Ontology Suite
◉ Neo4j Ontology Registry
Ontology Suites0
Imported Ontologies0
OWL Imports0
Vector Queue0
Total Classes0
Total Properties0
Stored in Neo4j0
Source Data0 MB
Last refresh: Now ● Checking Neo4j
Analysis Preview
Enter one Core Ontology URI and choose Resolve Suite. Nothing is written to Neo4j during analysis.
Semantic Vectorization Checking...
Embedding Model-
Dimensions-
Text Schema-
Ontologies0 / 0
Classes0 / 0
Properties0 / 0
Total Pending0
Ontology index: - Class index: - Property index: -
Ontology vectors describe scope and representative terms. Class vectors use labels, definitions and parent context. Property vectors use labels, definitions, type, domain and range.
◉ Ontology Suites
Imported Ontologies
Name Suite Classes Properties Size Vector Actions
⌘ Selected Ontology
● Database mode: Resolve Suite discovers the Core, extensions, dependencies and alignment documents but does not write to Neo4j. Import to Neo4j persists the resolved suite and connects suite roles, owl:imports and detected alignments. Vector status remains pending.