Dan Allan

[This was discussed on a call but I'll summarize here in case someone else hits this issue.] Starting in 1.0, the recommended way to handle configuration is with "intake-style" config...

Yeah, I have bumped into this too. This currently shows at the search paths for v2-, intake-style config files. It does not show the search paths for v0-style config files....

:+1: for relying on appdirs here

@ambarb's report is for v1.2.3, but this same issue applies to the `tiled-refactor` (upstream) branch, and the fix should be targeted there, because that is the "secure-able databroker" that will...

As an additional hint @tacaswell this is where `Broker.get_documents` implements this. https://github.com/bluesky/databroker/blob/970e9148dfab5e77101d40f059ecb30d064eac81/databroker/v1.py#L383-L435

I think the main blocker on this is thinking through how and whether we can implement it in other layouts beside mongo normalized.

Thanks for the report @st3107. This looks like a bug in `databroker` or `intake`. Your `setup.py` looks correct to me, and you are right to expect `db.name` to match the...

If we are calling the contents of the 'start' document `metadata` I feel we are under no obligation to call the contents of the 'stop' document `stop_doc`. Proposals for what...

Just noting this so we don't forget: @dylanmcreynolds suggested `run.summary` for the stop doc, since it summarizes number of events and so on.

We are developing a specification for both the Python API and HTTP API along with a proof of concept implementation over at https://github.com/danielballan/catalog-server-from-scratch. Once we validate that the performance is...