Review Organization
CiteTraverse keeps paper-level context beside each decision. Notes, tags, collections, metadata completion, and merge review all help a growing corpus remain explainable.
The detail pane combines metadata, coverage, notes, tags, collections, raw BibTeX, and paper actions for the selected record.
Notes, Tags, And Collections
Notes are saved to ct_notes. Tags are saved to ct_tags, including the reserved seed tag used for imported seeds. Collections are saved to ct_collections and power sidebar collection filters and derived custom BibTeX exports.
These edits are compact autosave actions. They do not require moving a paper between boxes and do not rewrite screening timestamps just because annotation fields changed.
Metadata Completion
Metadata completion enriches records without overwriting user-authored fields by default. Completed values are written to ct_completed_* fields, while provider citation counts can be stored in ct_citation_count when known.
This preserves the difference between the original BibTeX record and metadata CiteTraverse learned later.
Merge Review
When CiteTraverse detects an ambiguous duplicate or alias match, the candidate remains in Deferred until review is resolved. Merge-review metadata is stored on the deferred entry so the unresolved decision stays visible in ordinary project files.
Merge review compares the current workspace entry with the candidate entry before accepting, keeping, or merging fields.
External Edits
If authoritative box files change on disk while a project is open, CiteTraverse asks whether to dismiss those changes or review them. Review exposes field-level differences and applies chosen resolutions together, so external edits are not silently dropped.