TermSet Config

[mavaylon1]

Motivation

What was the reasoning behind this change? Please explain the changes briefly.

We want to integrate the TermSet class into pynwb such that we provide default termsets to validate fields within an object. The approach here is to have a config file that stores the object type, the fields within the object that uses a termset, and the path to the termset. These termsets will love within nwb-schema, along with the config file.

On the pynwb side, init_validation is a method call prior to setting the fields and calling init from the super class. This will go through the fields of the object and check the config file for fields that support termsets. These fields will have their values replaced with a TermSetWrapper.

How to test the behavior?

Show how to reproduce the new behavior (can be a bug fix or a new feature)

Checklist

• Did you update CHANGELOG.md with your changes?
• Have you checked our Contributing document?
• Have you ensured the PR clearly describes the problem and the solution?
• Is your contribution compliant with our coding style? This can be checked running flake8 from the source directory.
• Have you checked to ensure that there aren't other open Pull Requests for the same change?
• Have you included the relevant issue number using "Fix #XXX" notation where XXX is the issue number? By including "Fix #XXX" you allow GitHub to close issue #XXX when the PR is merged.

[mavaylon1]

TODO/Discussion:

1. Make the validation step a boolean.
2. Most likely move the init_validation to AbstractContainer. I kept it here for a quick proof of concept.
3. Finalize this approach in general.