# DataFrames.jl: metadata

**URL:** <https://discourse.julialang.org/t/dataframes-jl-metadata/84544>\
**Category:** Data\
**Tags:** package, dataframes, metadata\
**Created:** [July 20, 2022, 3:14pm UTC](https://discourse.julialang.org/t/dataframes-jl-metadata/84544 "2022-07-20T15:14:25Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![Ronis\_BR](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ronis_br/32/50999_2.png) [@Ronis\_BR](https://discourse.julialang.org/u/Ronis_BR)\
**Post date:** [July 20, 2022, 6:17pm UTC](https://discourse.julialang.org/t/dataframes-jl-metadata/84544/15 "2022-07-20T18:17:31Z")

</div>

This seems a problem very similar the one we had in [DEDataArrays.jl](https://github.com/SciML/DEDataArrays.jl). See the discussion here: [DiffEqs: Hybrid (continuous+discrete) system / periodic callback - #19 by ChrisRackauckas](https://discourse.julialang.org/t/diffeqs-hybrid-continuous-discrete-system-periodic-callback/23791/19)

In this case, we had a structure with a state and a set of parameters. The question about how propagate those parameters at each operation is hard to answer. @ChrisRackauckas eventually deprecated DEDataArrays.jl because it will be difficult to support every corner case.

Hence, given this past experience, I would vote for no metadata in DataFrames.jl. If the community wants, then we can add things to Tables.jl or another package.

---

_[View the full topic](https://discourse.julialang.org/t/dataframes-jl-metadata/84544)._