align terminology -> dataset != version

[m1ci]

The terminology used by the client is not aligned with the databus terminology.

The client uses:

  --title TEXT        Dataset title  [required]
  --abstract TEXT     Dataset abstract max 200 chars  [required]
  --description TEXT  Dataset description  [required]

which is actually an artifact version.

[DhanashreePetare]

Greetings @m1ci . I am interested to work on this issue. Can you please assign me the same. Thankyou.

[Tahoora-Tabassum]

Thanks for pointing this out — I agree this is a terminology mismatch.

From my understanding, the current CLI options (--title, --abstract, --description) actually describe artifact/version metadata, not dataset-level metadata, which makes the naming confusing for users.

I see two possible ways to address this:

1. Non-breaking approach: keep the existing CLI arguments but, update the help text and documentation to clearly state that these fields belong to the artifact/version (e.g. “artifact version title/abstract/description”).

2. Breaking but cleaner approach: rename the CLI arguments to version-specific names to fully align with Databus terminology.

I’d prefer to start with option 1 to avoid breaking existing workflows, unless maintainers would rather go for the cleaner but breaking change.

Please let me know which approach you’d like — I’m happy to prepare a PR accordingly