Search and metadata
Choose query patterns, stable identifiers, result projections, and date semantics before adding search infrastructure.
Start here
- Metadata vs. Full-Text Document Search
Match business queries to metadata or full-text search.
- Composite Keys or OpenSearch for Your Document Queries?
Work through multi-attribute lookup patterns and their trade-offs.
- Document Search Screens Without N+1 API Calls
Return useful result rows without a separate request for each document.
More on search and metadata
- Change Metadata Schemas Without Breaking Integrations
Plan document metadata changes with compatible field definitions, historical migration, supplier identity lookup, access tests, and consumer reconciliation.
- Cloud Records Retention: Why Metadata Matters
Use metadata to connect cloud records with retention schedules, legal holds, immutable storage, disposition review, and audit evidence.
- Composite Keys or OpenSearch for Your Document Queries?
Choose composite keys or OpenSearch for multi-attribute document queries, considering query shape, filtering, pagination, and operating cost.
- Document Applications: Metadata, Schemas, and Workflows
FormKiQ connects documents with the business context needed to act on them: metadata, schemas, relationships, and workflows.
- Document Dates: Preserve Instants and Local Meaning
Model instants, local dates, time zones, and deadlines so document workflows preserve business meaning across regions.
- Document Schemas: Validate Metadata and Improve Discovery
A document schema defines the metadata structure a workflow expects.
- Document Search Screens Without N+1 API Calls
Build document search screens with suitable result projections, batch retrieval, pagination, authorisation, and measured request counts.
- Finding the Right Manual by Part Number
Find the correct service manual with FormKiQ metadata search, approved part-number aliases and clear revision context for similar-looking identifiers.
- How Should ABAC Handle Missing or Stale Metadata?
Handle missing, invalid or stale metadata in FormKiQ ABAC policies with restricted intake, governed correction, freshness checks and access-path testing.
- Introducing Exasift: Search and Reporting for DynamoDB
Meet Exasift, a new product from the FormKiQ team for serverless DynamoDB search and reporting in your AWS account. Join the early-access waitlist.
- Metadata vs. Full-Text Document Search
Choose metadata, composite-key, OCR, or full-text search by query shape, permissions, freshness, relevance, and operating cost.
- Object Storage: Keys, Objects, and Application Metadata
Object storage holds file-like data as objects addressed through an API.
- Stable Document IDs Across Folder Moves
Keep integrations connected through folder moves with stable document IDs, site context, and retrieval checks.
- The FormKiQ Console: Find, Review, and Govern Documents
The FormKiQ Console gives people a visual way to find documents and participate in document workflows while applications use the same platform through APIs.
- When a Knowledge Base Cannot Answer
Handle unanswered document questions with clarification, an owned review queue and verified fixes using FormKiQ KnowledgeBase.
- When Document Search Results Change
Paginate FormKiQ document search while staff update records. Preserve continuation tokens, track review progress and recheck documents before acting.
- When Should OCR and Derived Text Be Rebuilt?
Decide when to rerun OCR, remap fields or rebuild search and AI outputs. Track source versions, reject stale runs and verify downstream publication.
- When Supplier Records Merge
Keep supplier documents connected when ERP records merge. Confirm the mapping, preserve original references and review access, evidence and unfinished work.
- Who Should Issue Your Business Numbers?
Choose when FormKiQ issues case or permit numbers, with one numbering authority, site-scoped sequences, yearly resets, and safe retries.