Table of Contents
The task of the database population tool, wacspop is to read the XML files which come as part of the distribution and use the contents of those files to populate some of the database tables with some sensible initial values. At present it will create any new records that have not been previously seen but will not update existing records in any way.
![[Note]](images/note.png) | Note |
|---|---|
The wacspop is new in WACS 0.8.6 and replaces three previous seperate commands - vendpop, photpop and keywordpop. It is not 100% compatible with the older files as they had insufficent data in them for a single combined loading program. It is easy enough to convert the files, see the section called “Updating XML Files For wacspop” below. |
There are currently four XML file types that understood by the wacspop command and they are:
- vendors.xml- Vendor database initial load
- photographers.xml- Photographer database initial load
- keywords.xml- Keyword database initial load
- attrib.xml- Attributes database initial load
Here wacspop reads the vendors.xml file and populates the vendors table with some useful example site (aka vendor) description records. These provide examples on how to configure the automatic download system as embodied in the chkmodel and getarc programmes, and should be directly usuable for any of the sites listed as soon as you add an appropriate username, password and subscription expiry date and set the subscription active.
Here wacspop reads the photographer.xml file and populates the photographer table with some useful example records. These will typically be photographers whose work has been encountered on a number of different websites and who have a “corporate” presence on the web. An initial selection of the most active circa 2009 is included in the XML file.
Here wacspop reads the keywords.xml file and populates the keyword table with some example keyword settings and priorities. There are about one hundred and fifty entries in the distributed file, which should provide some ideas on how the system works. Basically each keyword has entries for attributes, attire, locations and set types that it may provide clues to - each one of these is scored. The trick is to set the scores such that the presence of a sofa implies it's in a lounge, unless something else which binds stronger is also there. So if a photographer drags a sofa out into a garden for a given shoot, the "Garden" means Garden, Outside and takes preference over the "Sofa" means lounge rule. Take a look at Chapter 4, Naming Sets In WACS for more information and also use the wacskeywordmgr to have a look at the definitions we have already created for you.
This is a bit of an odd one as the attributes table isn't actually used by any other application in Wacs 0.8.6; this is here in preparation for the upcoming Wacs 0.9.0 release and contains incomplete sample data to aid in the testing and development of the Wacs 0.9.x code. Still, the files are here to serve as a guide as to what is coming in Wacs 0.9.x.