enumeray collection upload

Freeze and upload a directory or explicit member manifest.

Use when: You need a reusable verified input collection.

Role and prerequisites: Authenticated model user with access to the resource. Install enumeray, configure the API and log in. Use an account or delegated token with the required permissions. Example IDs must be replaced with IDs from your service.

Example

enumeray collection upload --directory mesh --name mesh --media-type application/octet-stream --state mesh-upload

Inputs and options

Input	Meaning and use
--directory <DIRECTORY>	Source tree of regular files. Symlinks and unsafe paths are rejected; a uniform --media-type is required.
--manifest <MANIFEST>	JSON array of selected relative paths, media_type and optional scientific_metadata objects. Paths are relative to --root or this manifest’s parent.
--root <ROOT>	Existing source root for an explicit manifest.
--name <NAME>	Logical collection name, independent of staged paths.
--media-type <MEDIA_TYPE>	Uniform bare media type for directory upload.
--state <STATE>	New private operation directory outside the source tree; never replace it on retry.

Every command also accepts the profile, API, JSON and timeout options.

Result and next step

Saves private source evidence, freezes membership and seals the collection after all members verify. Retain the state directory for retries.

Use the returned collection_id in a declared collection input, or repeat collection resume.

Exact syntax, defaults and accepted values

Freeze and upload a directory or explicit member manifest. Retain --state for retries

Usage: enumeray collection upload [OPTIONS] --name <NAME> --state <STATE>

Options:
      --api <API>                User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --directory <DIRECTORY>    Source tree of regular files; alternative to --manifest and requires a uniform --media-type
      --manifest <MANIFEST>      JSON array of relative member paths, media_type and optional scientific_metadata; alternative to --directory
      --profile <PROFILE>        Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>          Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --root <ROOT>              Manifest paths are relative to this root; defaults to the manifest's parent
      --json                     Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --name <NAME>              Logical collection name; independent of member paths
      --media-type <MEDIA_TYPE>  Uniform media type for a directory upload; manifest entries declare their own types
      --timeout <TIMEOUT>        User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
      --state <STATE>            New private upload-operation directory outside the source tree; retain for retries
  -h, --help                     Print help