Should FormKiQ Ingest a File or Keep a Deep Link?

A project team needs an engineering drawing and a signed acceptance record in the same business file. Engineering owns the live drawing in its existing repository. The acceptance PDF must preserve the approved record through the project's retention period. These documents can share a business context without sharing the same content-storage model.

Ingest a file when FormKiQ should manage the preserved content and its configured lifecycle. Keep a deep link when another repository should remain the authority for the bytes. Decide separately whether users need the current source file or the exact version used in a decision.

Separate the document record from its content

FormKiQ's document model supports managed file content, metadata-only records, and references through deepLinkPath. A deep-linked record can have its own FormKiQ identity, path, attributes, and relationships while the file remains elsewhere.

A metadata-only record serves a third purpose: it describes a business item without asserting that a file is attached or retrievable. Make that state clear in the application rather than displaying a download action with no content behind it.

Choose by the required control

File size is an upload-design question as well as a storage consideration. FormKiQ's Document Storage guide documents a presigned S3 upload flow for large files. Use the API-provided upload location and completion path; direct writes into the permanent documents bucket bypass the supported intake process.

Distinguish a source link from an access grant

An external HTTPS link may open another application with its own sign-in and permissions. An S3 deep link refers to an object that the configured FormKiQ service path can access. Confirm which behaviour the user interface and integration will provide; registering a URI does not define the entire retrieval experience.

For cross-account S3 content, scope source-bucket access to the intended role and objects. Where the file uses SSE-KMS, the retrieval path also needs the appropriate key permissions. AWS documents the decrypt permission needed to download KMS-encrypted objects. Include both bucket and key owners in the access and recovery plan.

Store a durable source identifier, not an expiring download credential, as the record reference. S3 presigned URLs grant time-limited access using the signer's credentials. Generate such access through the authorised retrieval path when needed, and treat the URL as a credential while it remains valid.

Bind processing results to the file that was read

External content can participate in processing when the configured integration and service permissions provide access to it. Specify the required operations, such as download, scan, OCR, indexing, or preview generation, then test each one against the actual source and selected modules. A working browser link proves a different path from a background worker reading the same file.

Record which source version produced extracted text, a thumbnail, or a classification. If the source changes, decide whether to refresh the derived content, preserve the earlier result, or require a new review. This keeps a search result or approval tied to the intended evidence rather than silently pairing old text with a new file.

For S3, version IDs distinguish retained object versions when versioning is enabled. Use an appropriate checksum to verify content integrity. An ETag can be useful change information, but it is not a universal full-file checksum; AWS's integrity guidance explains how upload and encryption choices affect it. Record the algorithm and checksum type alongside the value.

Work through the engineering project file

In this fictional project, engineering maintains the current drawing, while the project owner preserves the signed acceptance PDF and the drawing revision used for acceptance. The integration team makes three explicit decisions.

1. 1 · Reference

   Keep the live drawing authoritative

   Register its source identity and owner. Opening the live reference follows the engineering repository's approved access path.

2. 2 · Preserve

   Capture the approved evidence

   Ingest the acceptance PDF and an authorised snapshot of the accepted drawing revision, with source identity and integrity evidence.

3. 3 · Relate

   Connect both views

   Relate the live reference and preserved evidence to the same project. Label their purposes so users can distinguish current design from accepted history.

When engineering publishes a new drawing, the live source reflects its current state. The acceptance package continues to identify the revision that was approved. The project owner can explain which file was used, while engineers can still reach the current design. Copying the acceptance evidence does not transfer ownership of the live engineering repository.

Plan lifecycle changes and eventual transfer

For an ongoing reference, assign the source owner responsibility for content retention, holds, deletion, and recovery, and configure the integration to coordinate relevant lifecycle decisions. Include derived text, previews, exports, and managed snapshots in those rules. A metadata decision in one repository should have an explicit execution and acknowledgement path wherever the controlled content lives.

For a migration, FormKiQ's migration guidance includes S3 references as a supported approach when source storage remains governed. Track each record as referenced, transfer pending, transferred, or reconciled in your migration inventory. Preserve source identifiers and business relationships when transferring content, and reconcile the old and new retrieval paths before cutover. Plan document-ID mapping according to the supported import or update flow rather than assuming every conversion preserves identifiers automatically.

The related migration-verification guide explains why counts alone do not prove completeness. Reconcile content, attributes, access, retrieval, and exceptions before retiring the source.

Test one representative document class

• Name the content authority and specify whether users need the current file, a fixed revision, or both.
• Record the durable source identity, version, owner, region, access method, and checksum details where applicable.
• Test user retrieval and background processing separately, including missing bucket and KMS permissions.
• Change the source and verify that derived text, previews, and approval evidence follow the intended version rule.
• Exercise source deletion, expired access, a hold request, and recovery; confirm the responsible owner and visible exception.
• Transfer a sample through the supported ingestion flow and reconcile identity mappings, content integrity, metadata, access, and related records.

Choose the storage relationship the workflow needs

Deep links and managed content serve different ownership decisions. Keep an external source authoritative when that matches the workflow, and preserve a controlled copy when the business needs independently retrievable evidence. Make version, access, processing, and lifecycle responsibilities visible for both.

Technical guidance reviewed: November 13, 2026, against the linked FormKiQ and AWS documentation. The project and migration states illustrate application and integration design.