Skip to content

Document (legacy type)

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade D · dataset: Files (real PDFs, images, video and sheets) · type document

What it is

Documents in a storage bucket. document stays in the catalogue so existing connections keep resolving. In the test estate it holds bills of lading. The connector reference is Files and object storage.

Grade

D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typedocument
Settingsstorage_bucket, document_type, filter_prefix
Credentialsnone: this type reads no secret

The test connection

Bills of lading (legacy document)

SettingTest value
storage_bucketquillmere-bol
document_typebill_of_lading
filter_prefixbol/

This connection takes no credential.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. Download document.zip and unzip it. It holds three bill-of-lading PDFs under document/bol/ and expected.json.
  2. Upload document/bol/ to a bucket named quillmere-bol in a store you own.
  3. For a new connection, prefer files.

What FACE finds

document resolves in the catalogue and has no FACE registry case. The expected model is what the PDFs yield as text.

DatasetKindDomainPrimary keyRowsFields
quillmere-bol/bol/.bill_of_ladingpdfshipmentsbol_number35

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 4 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
carrierbill_of_lading.carrierd365, files, guidewire, mysql, objectstore, postgres, redshift, sharepoint, tms, yms
orderbill_of_lading.order_numberfiles, hubspot, kafka, oms, postgres, sap, snowflake
shipmentbill_of_lading.bol_numberbigquery, d365, databricks, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, sap, servicenow, sharepoint, tms, whs, yms
trailerbill_of_lading.trailercctv, databricks, excel, iot, kafka, mqtt, postgres, servicenow, tms, yms

It holds no evidence for the six planted anomalies. It is context: it makes the shared keys resolve.

See all connectors at once for the walkthrough across every source.

Download

This is one of 25 zips: the 7 streaming types ship as replay recordings instead.

What is in the zip
  • document/bol/SHP-50001.pdf
  • document/bol/SHP-50002.pdf
  • document/bol/SHP-50003.pdf
  • document/expected.json

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.