Data Flow

Understanding how data moves through the PropertySync system helps clarify the platform's capabilities and workflows. This document outlines the primary stages that title plant data and imagery go through from initial import to final delivery.

Overview

PropertySync manages the complete lifecycle of title plant data and document images. Data flows through several distinct stages, each designed to ensure accuracy, accessibility, and security. From the initial ingestion of raw documents and indexes to real-time searches and exports, every stage is optimized for reliability and performance.

Stages

Ingestion

The ingestion stage is where new data enters the PropertySync system. This includes both document metadata (indexes) and associated imagery.

Importing

Raw data is imported from various sources including customer systems, SFTP dropboxes, and direct API submissions. PropertySync supports multiple data formats and validates incoming data for completeness and accuracy. Import processes run continuously to minimize delays between data availability at the source and searchability within the system.

Indexing

Once imported, documents are indexed to make them searchable. This process involves extracting key information (party names, legal descriptions, recording dates, document types, etc.) and storing it in a multi-layered data structure. PropertySync uses a hybrid approach combining traditional relational databases, NoSQL document stores, and proprietary indexing systems to optimize both search performance and data relationships.

Verification

After ingestion and indexing, data undergoes verification to ensure accuracy and completeness. This may include automated validation rules, quality checks, and manual review processes. Verification helps identify missing information, data inconsistencies, or formatting issues before documents become part of the searchable plant. Companies can configure custom validation rules to match their specific quality requirements.

Exporting to the Plant

Once verified, document data is formally published to the searchable title plant. This step makes the information available to end users performing title searches and retrieving plant data. Publishing involves updating all relevant indexes, establishing document relationships, and ensuring the data is replicated across geographically redundant storage locations for reliability.

Searching

The search stage is where end users and API consumers query the title plant to find relevant documents. PropertySync supports multiple search types including name searches, legal description searches, and document number lookups. Search results are compiled in real-time, drawing from the indexed data structures created during ingestion. Search performance is optimized through caching, indexing strategies, and distributed query processing.

Editing

PropertySync allows authorized users to edit document indexes to correct errors, add missing information, or update records. This maintains the accuracy and completeness of the title plant over time.

Versioning

All edits are tracked through a comprehensive versioning system. When a document index is modified, the previous version is retained, creating a complete audit trail. This versioning capability allows users to view the history of changes, revert to previous versions if needed, and maintain compliance with record-keeping requirements. Version history includes who made changes, when they were made, and what was modified.

Exporting

Export functionality allows users to extract data and imagery from PropertySync for use in external systems. Exports can include search results, document indexes, images, and reports in various formats (PDF, Excel, CSV, etc.). The system supports both on-demand exports and scheduled automated exports via API. Export processes include formatting, packaging, and delivery options tailored to customer needs.