Datalad-metalad

Latest version: v0.4.22

Safety actively analyzes 714973 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 5

0.3.2

This release fixes two bugs:

1. Issue 245: `get_required_content()` was not called in dataset-level metadata extractors
2. Issue 247: module `datalad_metalad.extractors.studyminimeta` was not found.

0.3.1

Minimal release to add a missing requirement of "six"

0.3.0

This is a new suite of datalad commands to handle metadata. It includes a new storage backend, that does not interfere (and does not inter-operate) with the metadata storage system used in versions < `0.3.0`.

New commands:

The following commands are new, or have a changed syntax and semantic

* `meta-add`: add metadata to a repository
* `meta-dump`: dump metadata stored in a repository.
* `meta-aggregate`: aggregate metadata stored in sub-datasets and store it in the super-dataset
* `meta-extract`: run extractors to create metadata from repository-content
* `meta-filter`: run filter over all or parts of the metadata stored in a repository
* `meta-conduct`: execute pipelines that process metadata, e.g. extract metadata from all files in a dataset and add it to the repository. A few pipelines are provided with the release.

New extractors and idexers:

* `studyminimeta`-extractor: creates metadata from studyminimeta-files, i.e. `<dataset-root>/.studyminimeta.yaml`.
* `studyminimeta`-indexer: creates key-value sets from `studyminimeta`-metadata that is optimized for `datalad search`.

Note

This new suite of metadata commands is more or less a complete rewrite of the previous version. The concept has evolved, the syntax and semantics of the commands have changed, and the documentation is still growing.

At the moment there is no tool to import old metadata into the new system (although that is possible by reading the old metadata, converting each entry to a metadata record and add it to the new system via `meta-add`). The next release is intended to provide a tool for that.


**Full Changelog**: https://github.com/datalad/datalad-metalad/compare/0.2.1...0.3.0

0.2.1

- Minor release to rectify a few general things before development restarts.
- Discontinue support for Python 2
- `custom` extractor now reports files IDs
- Various internal changes to keep pace with DataLad development
- Prevent needless re-extraction of metadata (thanks to adswa and bpoldrack for analysis and fix)

0.2.0

- New `runprov` metadata extractor for `datalad run` record metadata as W3C PROV
- `meta_report()` was renamed to `meta_dump()` to better reflect its purpose and capabilities
- Various smallish changes for more robust and streamlined behavior

0.1.0

Born from the ashes of a revolution.... Metadata for the win!

Page 5 of 5

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.