Feature/store metadata methods

[jhamman]

This PR takes adds the option for stores to store metadata in whatever container makes sense for the store.

• adds Store.set_metadata and Store.get_metadata methods
  • moves json serialization/deserialization to Store ABC.
  • these methods can be overridden by stores that don't want to store metadata as JSON. For now, I've illustrated this with the MemoryStore that now keeps metadata objects as plain dictionaries.

toward #1755

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[jhamman]

I threw this in because it makes the test pass but its really not what we want. We were previously letting json.dumps do a lot of work to serialize Python objects. I think this means that we now need to push more of that logic into the to_dict() methods on the Metadata objects.

cc @d-v-b

[jhamman]

This PR takes adds the option for stores to store metadata in whatever container makes sense for the store.

• adds Store.set_metadata and Store.get_metadata methods
  • moves json serialization/deserialization to Store ABC.
  • these methods can be overridden by stores that don't want to store metadata as JSON. For now, I've illustrated this with the MemoryStore that now keeps metadata objects as plain dictionaries.

toward #1755

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[jhamman]

I threw this in because it makes the test pass but its really not what we want. We were previously letting json.dumps do a lot of work to serialize Python objects. I think this means that we now need to push more of that logic into the to_dict() methods on the Metadata objects.

cc @d-v-b

[jhamman]

This PR takes adds the option for stores to store metadata in whatever container makes sense for the store.

• adds Store.set_metadata and Store.get_metadata methods
  • moves json serialization/deserialization to Store ABC.
  • these methods can be overridden by stores that don't want to store metadata as JSON. For now, I've illustrated this with the MemoryStore that now keeps metadata objects as plain dictionaries.

toward #1755

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[jhamman]

I threw this in because it makes the test pass but its really not what we want. We were previously letting json.dumps do a lot of work to serialize Python objects. I think this means that we now need to push more of that logic into the to_dict() methods on the Metadata objects.

cc @d-v-b

[jhamman]

This PR takes adds the option for stores to store metadata in whatever container makes sense for the store.

• adds Store.set_metadata and Store.get_metadata methods
  • moves json serialization/deserialization to Store ABC.
  • these methods can be overridden by stores that don't want to store metadata as JSON. For now, I've illustrated this with the MemoryStore that now keeps metadata objects as plain dictionaries.

toward #1755

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[jhamman]

I threw this in because it makes the test pass but its really not what we want. We were previously letting json.dumps do a lot of work to serialize Python objects. I think this means that we now need to push more of that logic into the to_dict() methods on the Metadata objects.

cc @d-v-b

[jhamman]

This PR takes adds the option for stores to store metadata in whatever container makes sense for the store.

• adds Store.set_metadata and Store.get_metadata methods
  • moves json serialization/deserialization to Store ABC.
  • these methods can be overridden by stores that don't want to store metadata as JSON. For now, I've illustrated this with the MemoryStore that now keeps metadata objects as plain dictionaries.

toward #1755

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[jhamman]

I threw this in because it makes the test pass but its really not what we want. We were previously letting json.dumps do a lot of work to serialize Python objects. I think this means that we now need to push more of that logic into the to_dict() methods on the Metadata objects.

cc @d-v-b

[jhamman]

This PR takes adds the option for stores to store metadata in whatever container makes sense for the store.

• adds Store.set_metadata and Store.get_metadata methods
  • moves json serialization/deserialization to Store ABC.
  • these methods can be overridden by stores that don't want to store metadata as JSON. For now, I've illustrated this with the MemoryStore that now keeps metadata objects as plain dictionaries.

toward #1755

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[jhamman]

I threw this in because it makes the test pass but its really not what we want. We were previously letting json.dumps do a lot of work to serialize Python objects. I think this means that we now need to push more of that logic into the to_dict() methods on the Metadata objects.

cc @d-v-b

[jhamman]

This PR takes adds the option for stores to store metadata in whatever container makes sense for the store.

• adds Store.set_metadata and Store.get_metadata methods
  • moves json serialization/deserialization to Store ABC.
  • these methods can be overridden by stores that don't want to store metadata as JSON. For now, I've illustrated this with the MemoryStore that now keeps metadata objects as plain dictionaries.

toward #1755

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[jhamman]

I threw this in because it makes the test pass but its really not what we want. We were previously letting json.dumps do a lot of work to serialize Python objects. I think this means that we now need to push more of that logic into the to_dict() methods on the Metadata objects.

cc @d-v-b

[jhamman]

This PR takes adds the option for stores to store metadata in whatever container makes sense for the store.

• adds Store.set_metadata and Store.get_metadata methods
  • moves json serialization/deserialization to Store ABC.
  • these methods can be overridden by stores that don't want to store metadata as JSON. For now, I've illustrated this with the MemoryStore that now keeps metadata objects as plain dictionaries.

toward #1755

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[jhamman]

I threw this in because it makes the test pass but its really not what we want. We were previously letting json.dumps do a lot of work to serialize Python objects. I think this means that we now need to push more of that logic into the to_dict() methods on the Metadata objects.

cc @d-v-b