Reviewing imported Things
Correct extraction results and keep the review in Git.
Review a branch
After importing, the review page opens automatically. Return through Review Things in the project header or Settings. The queue starts with Things needing attention. Filter by missing files, unassigned Things, suggested placements, possible duplicates, or extraction checks; search by name, part number, or source path. The queue shows 40 results per page. Select All Things to inspect items without pending checks.
Review one Thing at a time
Details edits identity and BOM role, Files manages source/model links and supporting files, and Assembly edits parent placements, quantities and relationships. Click an issue label to open its relevant section. Confirm & next clears the extraction check and confirms suggested placements for the selected Thing; optional and legacy relationships are preserved. Resolve missing files, duplicates and unassigned placements before confirming. Skip moves on without changing the Thing. These edits remain local until Commit review.
Correct the hardware structure
Rename Things, select their physical types, assign source and model files, link related files, and edit quantities, reference designators, and parent assemblies. Add Things or placements when extraction misses something. Merge duplicates to redirect their occurrences to one definition and combine file links. Removing a Thing keeps its source files and moves child placements up one level. Invalid or cyclic hierarchies cannot be committed.
Commit the review
Commit review writes thingatlas.review.json and a materialized thingatlas.json to the selected branch in a normal Git commit. The review file records schema version 1, the source commit, reviewed definitions and BOM occurrences, and baseline IDs used to suppress removed detections. Create a branch first if you want to propose corrections through a pull request. Released versions do not change. If the branch moves while you edit, saving is rejected so you can reload and reconcile your changes.
Future scans and imports
Reviewed definitions and placements take precedence over inferred rows with the same stable IDs. Newly detected IDs are still added. Missing source files are flagged for attention. Cloning includes both manifests; importing a repository containing the review file retains its corrections and remaps Thing identities to the new project. Renaming a source file may create a new detected identity: merge or remove the duplicate in review. Reviewed quantities and metadata remain fixed until you change them.