Skip to content

[Documentation]: Create a guide for upgrading legacy behavior / data organization to new #2198

Description

@rly

What would you like changed or added to the documentation and why?

Changes between NWB schema 2.0 to 2.10 have recommended or required users to upgrade how data is organized in the NWB file for compatibility with the latest schema (all data are still readable though). Some of this upgrading happens automatically on read and subsequent write/export. It would be helpful to users to document all of these cases and centralize them into a guide for how to upgrade, especially around edge cases like the one described in #2186.

Do you have any interest in helping write or edit the documentation?

Yes.

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: lowalternative solution already working and/or relevant to only specific user(s)topic: docsissues related to documentation

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions