Publish project metadata

Publishes project metadata to a NADA catalog. The server loads the exported project JSON (generated for the project), then merges each property from the request body into that object as top-level keys. The combined JSON is sent to the catalog as POST {catalog_url}/index.php/api/datasets/create/{type} with header x-api-key, where {type} is derived from the project (e.g. survey, timeseries, timeseries-db). Typical merge fields from the Metadata Editor UI are overwrite, published, access_policy, data_remote_url, and repositoryid (see schema). Omit the body or send {} to publish without overriding those fields.

post/publish/{sid}/{catalog_connection_id}

Path parameters

sidstring required

Project ID or IDNO

catalog_connection_idinteger required

Catalog connection ID

Request body

overwrite'yes' | 'no'

If yes, allows replacing an existing study in the catalog with the same IDNO. Merged as top-level overwrite on the dataset JSON sent to NADA.

published0 | 1

Catalog visibility — 0 draft, 1 published (merged as published).

Data access / access policy code merged as access_policy on the payload. Allowed values match the Metadata Editor publish form; NADA may validate against codes returned by GET .../index.php/api/catalog/data_access_codes on the catalog.

data_remote_urlstring

URL for remote / external data access; merged as data_remote_url. Used when access_policy is remote or enclave (per catalog configuration).

repositoryidstring

Target collection (repository) code in NADA; merged as repositoryid. Options are typically populated from GET .../index.php/api/collections on the catalog (see /publish/catalog_info/...).

Example request

{
  "overwrite": "yes",
  "published": 1,
  "access_policy": "licensed",
  "data_remote_url": "",
  "repositoryid": "MY_COLLECTION"
}

Response

Project metadata published successfully (response shape follows NADA API)

Changes

Changed in 2 of the 12 revisions of this API.46

Apr 20, 20269d1903944c5923See the full diff
- ▲
  removed the enum value data_enclave of the request property
  request-property-enum-value-removed
- ▲
  the request property format changed from no format to int32
  request-property-type-changed
- ○
  the request property default value data_na was added
  request-property-default-value-added
- ○
  added the new enum value to the request property
  request-property-enum-value-added
- ○
  added the new enclave enum value to the request property
  request-property-enum-value-added
Feb 23, 20265bfc4d9dc1c823See the full diff
- ▲
  removed the enum value of the request property
  request-property-enum-value-removed
- ▲
  removed the enum value enclave of the request property
  request-property-enum-value-removed
- ○
  the request property default value data_na was removed
  request-property-default-value-removed
- ○
  added the new data_enclave enum value to the request property
  request-property-enum-value-added
- ○
  the request property format was generalized from int32 to no format
  request-property-type-generalized
This revision also has 37 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history