Views

Table View

A scrollable, collection-by-collection breakdown.

Name – e.g., Accounts.
Primary Key – default _id (ObjectId) unless overridden.
Field List – each field shows:
- Field name (ACCOUNT_NUMBER, USERNAME, …).
- Required badge if the field is present in every sampled document.
- Right-aligned type chip (string, date, objectId, …).
Field / Required counters – top-right of each block (e.g., “11 fields • 8 required”).

Copy JSON (upper-right) – copies the full schema in JSON Schema-like format to clipboard.

A lightweight ERD (entity-relationship diagram) generator.

Element	Description
Collections	Rendered as cards (one per collection) with port connectors for relations.
Fields	Displayed inside each card; optional to expand/collapse for readability.
Relations	Lines connecting collections (none detected in screenshot).

Button	Function
Filters – Isolated Only	Hide collections with at least one relation.
Filters – With Relations Only	Show only collections that participate in a relation.
Re-organize	Run an auto-layout algorithm to tidy node positions.
Fit View	Zoom/pan canvas so all nodes fit in the viewport.
Copy JSON	Same JSON export as in Table View.

Adjust Sample Size – Increase for production databases with schema drift; decrease for quicker previews.
Use Required Badges – Quickly identify mandatory fields and candidates for indexing.
Switch Views – Table View excels at field-level audits, while Design View helps visualise relationships.
Export JSON – Feed the exported schema into validation libraries or documentation tools.

Cmd/Ctrl + (plus) / Cmd/Ctrl + - (minus) – Zoom in / out (Design View).
Space + Drag – Pan the canvas (Design View).

Next Steps: Combine Schema Analyzer results with the Aggregate Builder to craft queries that respect detected data types and relationships.