Padraic Shafer

I'd like to submit a PR for this, but will wait until the [ophyd v2 docs are removed](https://github.com/bluesky/ophyd/pull/1162).

At some point, we’ll need to consider what’s needed to facilitate schema evolution for forward/backward compatibility. It might be worthwhile to already add a `version` field to the tag definition.

> We would need to make `table` a reserved word in the `data_keys` namespace of the event model. Ahh, now I'm seeing where these two worlds currently clash. Event model...

Here are some use cases I think that we want to handle. Some of them are already implemented, at least in part. I'm hoping that this helps frame the changes...

I think `FullText` conveys more authoritatively than `Text` that all of the metadata is being queried. As far as `FuzzyFullText` and variants go, maybe an import alias is the right...

...or maybe `Search` and `FuzzySearch` are both simple and well understood?

Here's my best guess so far.. (I haven't had a chance to test any of this. Documenting it here for whenever someone has time.) https://github.com/bluesky/tiled/blob/7c6a8dd06d5eb23fac8402a68aedc467983831f2/tiled/adapters/files.py#L287-L318 * Should line 290 have...

From my point of view, specifying which files/directories to match is just as valid as which ones to ignore. So the simple fix might be to just rename the parameter...

> Here is the relevant code from watchgod.watcher.RegExpWatcher [0.8.2](https://pypi.org/project/watchgod/0.8.2/#files) Btw, at some point will probably need to [migrate from `watchgod` to `watchfiles`](https://watchfiles.helpmanual.io/migrating/). https://github.com/bluesky/tiled/blob/23cde094b737987e5ec30d497c87563a5d6dd0d5/requirements-server.txt#L30

A couple of subtleties are worth noting: * CLI args could include a config file as well as switches that correspond to a parameter within a config file; * There...