Possible to allow for nested structure in Acquisition Container?

[arjunsridhar12345]

I have many raw hardware signals from different sources that need to be stored in the acquisition container. I would like to store them in nested modules, similar to what can be done in the processing container. Having this structure would make access much friendlier and make downstream analysis much more straightforward.

Is this something that could be added to the core schema, or is there an underlying design reason that acquisition cannot support nested structure?

I also found this extension, which seems to support this use case:
https://pypi.org/project/ndx-acquisition-module/

Is this extension considered stable and appropriate for organizing acquisition data, or would it make sense for this functionality to be supported directly in the acquisition container?

Tagging @bruno-f-cruz for any additional comments.

Sample example is shown below. Currently this is how the acqusition is structured where there are numerous signals and devices all flattened and having long names to distinguish between them:

• Behavior.HarpBehavior.AnalogData
• Behavior.HarpBehavior.AssemblyVersion
• Behavior.HarpBehavior.Camera0Frame
• Behavior.HarpBehavior.Camera0Frequency
• Behavior.HarpBehavior.Camera1Frame
• Behavior.HarpBehavior.Camera1Frequency
• Behavior.HarpBehavior.ClockConfiguration
• Behavior.HarpBehavior.CoreVersionHigh
• ...

Ideally something like below would be nice to have to organize the different streams by devices:

/acquisition
    /Behavior
        /HarpBehavior
            AnalogData
            AssemblyVersion
            Camera0Frame
            Camera0Frequency
            Camera1Frame
            Camera1Frequency
            ClockConfiguration
            CoreVersionHigh
            ...