Document (legacy type)
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 | |
|---|---|
| Type | document |
| Settings | storage_bucket, document_type, filter_prefix |
| Credentials | none: this type reads no secret |
The test connection
Bills of lading (legacy document)
| Setting | Test value |
|---|---|
storage_bucket | quillmere-bol |
document_type | bill_of_lading |
filter_prefix | bol/ |
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.
- Download
document.zipand unzip it. It holds three bill-of-lading PDFs underdocument/bol/andexpected.json. - Upload
document/bol/to a bucket namedquillmere-bolin a store you own. - 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.
| Dataset | Kind | Domain | Primary key | Rows | Fields |
|---|---|---|---|---|---|
quillmere-bol/bol/.bill_of_lading | shipments | bol_number | 3 | 5 |
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 entity | Fields here | Also in |
|---|---|---|
| carrier | bill_of_lading.carrier | d365, files, guidewire, mysql, objectstore, postgres, redshift, sharepoint, tms, yms |
| order | bill_of_lading.order_number | files, hubspot, kafka, oms, postgres, sap, snowflake |
| shipment | bill_of_lading.bol_number | bigquery, d365, databricks, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, sap, servicenow, sharepoint, tms, whs, yms |
| trailer | bill_of_lading.trailer | cctv, 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
document.zip: 4 files,expected.jsonincluded.
This is one of 25 zips: the 7 streaming types ship as replay recordings instead.
What is in the zip
document/bol/SHP-50001.pdfdocument/bol/SHP-50002.pdfdocument/bol/SHP-50003.pdfdocument/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.