A clear database structure helps keep your archive tidy and effective. Tip: the ⌘1 - ⌘9 shortcut buttons allow you to switch between the first 9 databases on the list.
Create a database for each of these categories. We recommend that you use the template 'Music And FX' for the creation of the database. I will explain the reasons for this in more detail later on. In a nutshell: this establishes all available fields for music and sound databases. The reason why we recommend this approach is because it is no longer possible to ‘update' a table later in the process.
For performance reasons, Soundminer only allows you to search for files within a single database, so we make use of a database that contains everything we need for work. Into the first database we therefore put all the sounds that are currently in use. This includes all sounds that you are using for your work, e.g. purchases sound archives, your own sounds, your own sound archive and anything else connected to your work.
A second database is used for all purchased archives and a third one for your own sounds. For the latter, we recommend that you distinguish between raw material and edited/processed material. If you do a lot of recording, it pays to have a separate archive for raw material (with iXML fields). This way your material is clearly arranged and won't get lost (as long as all new recordings are imported and properly labelled, of course).
Furthermore, we recommend that you use separate databases for all music as well as for sounds from other projects.