search

datalad / datalad-metalad

Next generation metadata handling
Other
11 stars 11 forks source link

Hackathon 2023-02 topic board #335

Open christian-monch opened 1 year ago

christian-monch commented 1 year ago

The 2023-02 metalad hackathon

The goal of this hackathon is three-fold:

Docs

Documentation can be found in a few different places. First, in the datalad handbook, and in the --help messages of the individual datalad-metalad commands. There is also an first steps gist here: MetaLad: first steps

Issues

The following issues are on the shortlist for the metalad 2023-02 hackathon

Added 2023/02/25

Added 2023/02/28

Feel free to suggest other issues or topics (create new issues) on which you would like to work.

christian-monch commented 1 year ago

As a result of our discussion in the morning, we would like to highlight that currently the file-level extractor paradigm leads to a large number of per-extraction subprocess invocations when running meta-conduct. There is an issue datalad/datalad-metalad#268 and a related branch https://github.com/datalad/datalad-metalad/pull/298

asmacdo commented 1 year ago

ENH: Add "container extractor": https://github.com/datalad/datalad-container/issues/198

christian-monch commented 1 year ago

Hackathon summary

The hackathon was held on 28th of February from 9:00 CET to 22:00 CET with four participants from Europe and three participants from the USA.

The desired results for this hackathon were:

The hackathon provided progress in all of those items.

The team was introduced to metalad in two interactive demo-sessions (9:00 and 14:00) which lead to a number of discussions and questions. That provided a good basic understanding of metalad. Following those introductions, the team worked with the code base and its documentation.

During the hackathon the team worked in the areas documentation, improvement identification and implementation, and extractor implementation. Generally it seems that the team has gained a good understanding of metalad and its basic usage, and is able to identify its utility for new and existing projects.

Detailed outcome

Documentation

Improvement identification and implementation:

Extractor implementation: