Rights Management
Public Domain Territory and Verification
Capture the jurisdiction, basis, source edition, and confidence of an assertion.
- 6 min read
- 6 min read
- Last reviewed 2026-08-11
- Last reviewed 2026-08-11
- Beginner
- Beginner
Territory and evidence
Enter the jurisdiction where the assertion applies. Describe the basis without storing secrets, and identify the edition or source reviewed. Different publication histories, restorations, translations, and jurisdictions can change the analysis.
Verification states
User Asserted records who supplied the claim. Needs Review identifies an incomplete basis. Reviewed records a human review; Documented indicates supporting evidence was captured. These states describe workflow confidence, not a legal conclusion. Recheck before each material use.
A territory should be specific enough for another reviewer to understand the scope; avoid Worldwide unless the evidence genuinely covers every intended jurisdiction. The basis may summarize relevant facts or authority, while the source-edition note distinguishes the exact score, publication, translation, or adaptation examined. Evidence notes should be concise and must not include passwords, tokens, or privileged material. Record the reviewer and timestamp through the application workflow. When a user changes the assertion, CatalogIQOS creates an audit event without copying sensitive evidence content into the audit log. If evidence conflicts or expires, move the record to Needs Review and disclose uncertainty in downstream pitch material.