Home | Connectors | OpenText Lens - Data Visibility | OpenText Lens - Data Visibility - Sanity Integration and Automation
OpenText Lens - Data Visibility and Sanity complement each other by connecting unstructured data discovery and governance with structured content operations. OpenText Lens helps teams identify what content exists, where it lives, and whether it is sensitive, redundant, or obsolete. Sanity then provides the controlled environment to create, manage, and publish approved content. Together, they support cleaner content operations, lower risk, and better cross-team visibility.
Data flow: OpenText Lens - Data Visibility to Sanity
Use OpenText Lens to scan file shares, legacy repositories, and collaboration platforms to identify content that is obsolete, duplicated, or sensitive before moving content into Sanity. Business teams can use the findings to decide what should be migrated, rewritten, archived, or discarded.
Data flow: OpenText Lens - Data Visibility to Sanity
OpenText Lens can identify documents or source assets containing personal, financial, legal, or confidential information. That insight can be used to flag content before editors import or reference it in Sanity-managed experiences, helping teams avoid publishing restricted material.
Data flow: OpenText Lens - Data Visibility to Sanity
Organizations often have large volumes of unstructured content that can be converted into reusable structured content in Sanity. OpenText Lens can identify overlapping, outdated, or duplicate content sets so content strategists can rationalize what should become canonical reusable content blocks, product descriptions, policy snippets, or campaign assets.
Data flow: Bi-directional
Sanity manages the approved content used in websites, apps, and campaigns, while OpenText Lens can periodically scan related source repositories and exported content packages to verify that no sensitive or obsolete material is being reused. If Lens identifies a risk, the issue can be routed back to content owners in Sanity for correction.
Data flow: OpenText Lens - Data Visibility to Sanity
Before building new content types in Sanity, teams can use OpenText Lens to analyze legacy documents, manuals, product sheets, and knowledge articles to understand common themes, fields, and content patterns. This helps information architects design a content model that reflects real business content rather than assumptions.
Data flow: OpenText Lens - Data Visibility to Sanity
OpenText Lens can detect stale or obsolete content in source repositories, such as expired product documentation, outdated policy references, or superseded marketing collateral. That information can be used to trigger updates, retire content in Sanity, or prevent outdated material from being republished.
Data flow: Bi-directional
When OpenText Lens flags content issues such as duplication, sensitivity, or retention concerns, those findings can be assigned to content owners working in Sanity. Editors and content stewards can then update, replace, or retire the affected content and confirm remediation back to governance teams.
Data flow: OpenText Lens - Data Visibility to Sanity
For new websites, portals, or regional launches, OpenText Lens can assess source content readiness by identifying what content is available, approved, and safe to reuse. Sanity can then be used to structure and publish the selected content into the new experience with greater confidence and less manual review.
Together, OpenText Lens - Data Visibility and Sanity enable a more controlled content supply chain, from discovery and risk assessment to structured creation and publishing.