JSON on a Catalog screen is a view. It is not a form, an import file, or a download.

Read the JSON

JSON on a Catalog screen is a view. It is not a form, an import file, or a download.

What you can open

Chunking parameters on Contract are the stored chunk settings. Structured metadata on a search hit is the fields attached to that hit. A result record carries content and provenance. A publication manifest is the catalog record of a published result. Read the keys beside the human labels. An empty object is present and blank. A missing key was not written. Null is a written empty. Those three are different.

Present and Missing

Some review surfaces mark an artifact Present or Missing: extraction schema, retrieval config, and corpus config. Collection detail mounts that review only while a review is open. After approval, that pane may not be reachable again. Use Contract and the result record instead. Do not force a review state just to photograph the pane.

What is not a Catalog pane

A Context Policy snapshot is the JSON the next Search or Answer sends. It is not the chunking JSON. An API-only parity report is not drawn in the product. Internal engine objects that never reach the page are not documented as screens.

There is no Catalog JSON editor, importer, or export button.

Related documentation