Rafael Schouten

Edit: reading your code again: are you not talking about rebuilding the metadata, just the struct values? That is totally doable. But it wouldn't live here, instead it would be...

metadatafunctions is doable, but loading metadata isn't :) In terms of loading from dataframe - its much better get the field values as a tuple and update an existing struct...

You should be able to use Flatten.jl for that too... It's probably faster, even though it seems more complicated. Edit: or Setfield.jl

The solution is to always use a separate type parameter for every field. Whihc also has other benefits.

Ah ok the T in the first example confused me. That is an interesting problem. You could define `T

Sounds like I should be a coauthor on this paper if you are including that much about my work. This isn't easy to do with FieldMetadata.jl because functions have to...

That sounds interesting! I also work in ecology/agriculture research in Aus btw :) My reason for asking is I am writing too many packages... way ahead of what I can...

Ok I've been thinking about loading metadata from a csv. It should actually be pretty easy, something like: ```julia # Load CSV to data frame. This is psedudocode: df =...

Thats a good solution to duplicate keys. I would be happy with a PR, with a few caveats: - Mostly `flatten` compiles away and has no/little runtime cost - this...

Flatten.jl doesnt flatten Dict or Array or anything with with variable length at runtime as it breaks the symmetry of `reconstruct`. You can of course Flatten to whole `Dict` and...