Consider adding 'sentinels' to avoid accidental mistyped database names.

[danielballan]

MongoDB will gladly, silently create a Database and Collections in that database if they don't exist. This makes it easy to connect to the wrong Database and start putting data in it without realizing. To avoid that, we require the user to explicitly initialize a Database for use with databroker by creating a "sentinel" collection.

Should we take this approach again in suitcase? I see one big Pro and several smaller Cons with no strong sense of how we should weigh them at this point.

Pro

• Avoid accidentally putting data in the wrong place.

Con

• Creates a hurdle for people getting set up to try this library
• Seems to me not an idiomatic usage of MongoDB
• The 'Pro' may be less relevant when MongoDB connections are managed centrally (behind an intake server) and never typed by end users.