enumeray model create

Create a model resource and import optional author metadata.

Use when: You need a stable catalogue model before initializing its first release.

Role and prerequisites: Authenticated model author with models:manage authority. 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 model create example --file publication.json
# Manual metadata instead of a file
enumeray model create another-model --name 'Another model' --description 'Scientific model description'

Inputs and options

Input	Meaning and use
<ID>	New stable model ID; must match model.id when importing a file.
--name <NAME>	Manual display name, required unless --file is supplied.
--description <DESCRIPTION>	Optional manual catalogue description, defaults to empty; conflicts with --file.
--file <FILE>	Editable publication.json; imports only model metadata. An incomplete execution draft is allowed. Conflicts with manual --name and --description.

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

Result and next step

Creates ownership and catalogue ID/name/description only. Does not install, register, activate or update an existing model.

Complete and validate publication.json, then initialize a saved release.

Exact syntax, defaults and accepted values

Create model catalogue metadata from explicit fields or a publication source

Usage: enumeray model create [OPTIONS] <ID>

Arguments:
  <ID>  New stable catalogue model ID; must match --file when importing metadata

Options:
      --api <API>                  User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --name <NAME>                Catalogue display name; required unless --file supplies model metadata
      --description <DESCRIPTION>  Catalogue description; defaults to empty and cannot be combined with --file [default: ""]
      --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
      --file <FILE>                Import catalogue metadata from the editable publication source
      --json                       Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>          User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help                       Print help