name of the models tables. This is indirected to allow for databases to be owned by a different user than the wacs system runs as or for porting considerations to other database platforms. In Oracle you might call it dbowner.models rather than the normal simple models.

name of the idmapping table - this is the one that links a local model to a model name/number for a specific site.

name of the associations table, ie the one that links a model to a given set. A single set can have many associations, if it has a lot of known models in it.

name of the sets table - the main database table of the WACS system. Very little will work if the wacs programs can't find this one!

name of the download table. This is used to identify the source information for a set. Depending on status can either be a task list, or a check list of what we already have.

name of the photographer table. Where the list of known photographers is.

name of the tag table. This is the search results and bookmarking mechanism's workspace.

name of the vendor table. This contains information on various source web sites, how to parse them and download from them and how to link to them.

name of the connections table. This is the new mechanism for arbitary connections between sets, models and photographers - the key difference between tags and connections, is that the WACS applications will flag up when a set is a member of a connection.

name of the keywords table. This is used for guessing attributes and locations from key words found in the description

name of the user authentication table. This is used for storing usernames, passwords, email address and other things needed for using the database for authentication. Using the default installation authentication method of hostauth, this table will not be used. It includes many fields related to managing user information in a subscription website environment but only limited access to those features is provided in the open source variant of WACS