dump-things-pyclient/CHANGELOG.md

# 0.2.17 (2026-03-31)

## New features

- Add `--only-if-modifying`-option to `dtc` subcommands `post-records`, and
  `auto-curate`. If this flag is provided, a record will only be store in
  curated areas, if a matching records does not already exist. If
  `--jsonpath-spec JSONPATH_SPEC` is provided two records match if they are
  identical after all elements that match `JSONPATH_SPEC` are removed. If
  `--jsonpath-spec` is not povided, two records match if they are identical.

## Improvements

- Remove unnecessary `no token provided` warning from `dtc` subcommand 
  `get-records`.


# 0.2.16 (2026-03-24)

## New features

- Add `--keep-inboxes`-option to `dtc` subcommand `auto-curate`. If this flag 
  is provided, inboxes will not be deleted on `auto-curate` (this is independent
  from the curation destination, i.e., inboxes will be kept whether
  `--create-change-set` is defined or not).


# 0.2.15 (2026-03-23)

## New features

- Add `--author-id`-option to `dtc` subcommands `auto-curate` and `post-records`.


# 0.2.14 (2026-03-10)

## Improvements

- JSON files in change sets (create by `auto-curate --create-change-set`) are
  now pretty printed with an indentation of 2.

- The directory in which the change set is created is written to stdout when
  `dtc auto-curate --create-change-set ...` exits.

- The output of git-process execution is captured and not written to stdout
  or stderr on `dtc auto-curate --create-change-set ...`.

- All records that are added to a change set are removed from their inbox.


# 0.2.13 (2026-03-10)

## New features

- The `dtc` subcommand `post-records` now accepts the class name `*`. If this
  class name is given, it will try to infer the class name from the
  `schema_type` property of the input records. `post-records` also got the new
  options `--ignore-errors` and `--dry-run`.

- The `dtc` subcommand `auto-curate` has the new options
  `--create-change-set CHANGE_SET_DIR` and `--post-change-set`. With
  `--create-change-set`, `auto-curate` will generate a
  git repository in `CHANGE_SET_DIR` that contains the changes that
  would be introduced by the curation in the git worktree. The records in the
  change set have no `annotations`-property, annotations are store separately
  in the change set. If `--post-change-set` is provided,
  `auto-curate` will post the records from the change set to the curated area 
  of the service. With
  the option `--add-annotations` the annotations that were read from the inbox
  will be added to the records before they are posted to the service.


# 0.2.12 (2026-02-11)

## New features

- Add `dtc` subcommand `version`. `version` prints the version of `dtc` and
  exits.

- Add the option `--json-error-messages` to `dtc` subcommands: `export`,
  `import`, and `delete-records`.

- Ensure that all `dtc` subcommands return an non-zero exit status on error.

## Improvements

- Improve help messages of `dtc` subcommands `delete-records` and `import`.


# 0.2.11 (2026-02-09)

## New features

- Add `dtc` subcommand `import`. `import` reads records that were written by
  the `dtc` subcommand `export` from a file system and posts them to a
  dump-things-server. This includes the curated area and the incoming areas.
  By default, the destination server URL and collection name is read from the
  file `description.json` in the exported data area.  Both can be overridden by
  command line options.

- Add option `--format` to the `dtc` subcommand `export`. This option
  supports selection of the file format for records, currently `json` and
  `yaml` are supported.


# 0.2.10 (2026-02-09)

## Bugfixes

- Fix a bug in the handling of `--first-page` in the `dtc` subcommand
  `get-records`.


# 0.2.9 (2026-02-06)

## New features

- Add option `-C/--class` to the `dtc` subcommand `delete-records`. This option
  supports deletion of all records of a specific class.

- remove erroneous warnings from `dtc` subcommand `get-pages`, that were
  triggered when `-p/--pid` was provided.


# 0.2.8 (2026-02-05)

## Bugfixes

- Ensure that JSON results of the `dtc` subcommand `auto-curate` are not marked
  up during output.

- Remove erroneous warnings from `dtc` subcommand `get-pages`, that were
  triggered when `-p/--pid` was provided.


# 0.2.7 (2026-02-05)

## Change and improvements

- The `dtc` subcommand `export` now:
  - reports progress percentage based.
  - uses pid-hashes to determine the file name of persisted records

## New features

- The `dtc` subcommand `export` now:
  - supports JSON and YAML output.
  - removes `schema_type` attributes from records by default


# 0.2.6 (2026-02-04)

## New features

- Use request sessions in `dtc` to reuse existing connections


# 0.2.5 (2026-02-03)

## New features

- Use sensible defaults for options in the `dtc` subcommand `auto-curate`.

- Improve progress and error reporting in the `dtc` subcommand `auto-curate`.


# 0.2.4 (2026-02-02)

## New features

- Add "maintenance" subcommand to `dtc`.


# 0.2.3 (2026-01-28)

## New features

- Add "delete-record" subcommand to `dtc`.
- Add "export" subcommand to `dtc`.

## Bug fixes

- Fix faulty -C/--class handling in dtc subcommand get-records
- Fix faulty -m/--matching handling in dtc subcommand get-records


# 0.2.2 (2026-01-23)

## New features

- Add a "redirect" command for the commands that were moved to `dtc`, which
  informs users about the new location of the command.


# 0.2.1 (2026-01-23)

## New features

- Use rich-click for CLI-interface implementation.


# 0.2.0 (2026-01-22)

## New features

- Add `dtc`-command. `dtc` replaces `auto-curate`, `get-records`, `post-records`,
  and `read-pages` which are now subcommands of `dtc`. It provides the new
  subcommands `list-incoming` and `clean-incoming`.


# 0.1.4 (2026-01-19)

## New features

- Add -d/--dry-run option to auto-curate. If given, auto-curate will not modify
  any data, but only print what it would do.

- Add -i/--include option to include only the given inboxes into the auto-create
  process