System-to-dataset mapper

What does the system-to-dataset mapper produce?

Map actual applications, databases, files, datasets and organizational owners.

Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.

What do you need before you start?

• Define the authorized source population and your review rules.
• Keep the unchanged original files and record the snapshot and exclusions.
• Review missing and invalid inputs before preparing the finalized pack.

What information do you enter?

Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.

• Map reference. Customer-controlled graph reference.
• Map version. Customer-controlled graph version.
• Map owner. Responsible customer reviewer.
• Observation date. YYYY-MM-DD. Effective intervals include both endpoints.
• Selected map scope. Name actual entities, time period, selected requirements and declared boundaries.
• Population comparison. Selected nodes alone cannot establish population completeness.
• Task-specific nodes. Actual identified node versions and source IDs.
• Task-specific relationships. Actual typed links between exact node versions.
• Selected starting nodes. Explicit node ID and version for reachability and lineage.
• Your expected graph. Optional exact node or relationship expectations with approval evidence.

What you can download

Every result must identify its supplied facts, assumptions and unresolved items.

Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.

How does the system-to-dataset mapper work?

1. 1
   Define actual nodes and relationships

   Map reference. Customer-controlled graph reference.

2. 2
   Freeze the review rules

   Join each declared relationship to exact node versions and source bytes. Validate ownership, storage and read/write directions. Identify datasets without a declared host or owner and show paths from selected systems. The map never discovers unprovided assets.

3. 3
   Inspect complete findings

   Review all source-linked results and unresolved items. Free JSON and CSV preserve complete results.

4. 4
   Keep recoverable work

   Current drafts retain exact input strings and original files locally. Strict backup and cloud restores validate schemas, graph identity, source hashes and history before changing work. Prior checkpoints and earlier generic work remain separate.

5. 5
   Prepare the finalized pack

   Prepare eight core formal and data files, including the actual declared SVG map and selected exact attachments, then download them free. Review the fictional sample below.

Method and sources

Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.

• PROV-DM The PROV Data ModelA domain-independent reference for source identity, versioned entities, relationships and responsibility. It supplies no domain legal rules or authority. Entities and agents have distinct identities. Activities and relationships retain their actual provenance and declared responsibilities.World Wide Web Consortium. Reviewed 2026-10-09.

Common questions

What still needs review?

Your declared relationships only. Exact input and source bytes stay in this browser. Original files are not saved to the cloud. No source authentication, discovery, legal applicability, screening, alert, external message or provider change is performed.

At most 200 rows per table and 20000 characters per answer, 20 local files, 10 MB each and 25 MB total. Paths use bounded shortest traversals rather than all exponential routes.

Financial amounts retain exact declared values with at most two decimal places per currency. Quantities use six decimal places and ownership percentages four. No currency or unit conversions are performed.

Related working records

The related workspace contains working administrative records. Open it for the related administrative task.

Related tools

Browse all privacy and data rights tools.

• Personal-data inventoryCatalog datasets, purposes, locations, owners and access arrangements. Try a free example. Review your inputs and result.
• Processing activity registerCreate a structured US privacy operations record, with an optional GDPR Article 30 edition. Review the result. No account or payment required.
• Data-flow diagram generatorDraw flows from confirmed relationships. Try the free example, then enter your own inputs and review the result before exporting.
• Purpose compatibility workpaperOrganize proposed secondary uses and supporting reasoning. Try a free example. Review your inputs and result. No account or payment required.
• Inventory reconciliation toolCompare departmental submissions and identify missing or conflicting records. Try a free example. Review the result. No account or payment required.