Storing your museum's data in its own database

By default, a CollectionSpace server stores data for one or more museums or collections ("tenants") intermingled in a single nuxeo database.

If more than one tenant is present - and by default, sample core and lifesci tenants are present, as well as any tenants you might yourself create - the data (rows in database tables) belonging to any one tenant can be distinguished from data belonging to other tenants only via database queries which include JOINs, in part based on tenant IDs.

This default behavior can compel more effort to isolate the data belonging just to a single museum or collection, for backups or other purposes. (In practice, however, most or all CollectionSpace installations to date have featured just a single tenant, plus the two sample tenants - which are typically unused in that scenario - so only data relevant to that single tenant is present in the database, making this concern more theoretical than practical.)

Still, there may be scenarios in which you may yet want to store your museum or collection's data in its own database, perhaps one named after your institution. If so, you can make this configuration change at the time you set up a new tenant for your museum. See the relevant instructions in Creating your new tenant how to do this via configuration.