Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List extractor capabilities, e.g. in datalad wtf-output #365

Open
christian-monch opened this issue Mar 8, 2023 · 0 comments
Open

List extractor capabilities, e.g. in datalad wtf-output #365

christian-monch opened this issue Mar 8, 2023 · 0 comments

Comments

@christian-monch
Copy link
Collaborator

christian-monch commented Mar 8, 2023

This is a follow up of PR #351

In addition to the "interface-generation" that is made explicit in extractors with PR #351, we should make the capabilities explicit. More precisely, extractors should be able to state whether they support file-level, dataset-level, or file-level and dataset-level extraction.

As outlined here, we can add a class property named __extraction_modes__, that would be a non-empty subset of {'file', 'dataset'}. This could be, for example, reported in datalad wtf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant