A simple example of using addmodel would be:
% addmodel name=Sarah hair=Redhead length=Normal titsize=Small pussy=Shaven image=Sarah-1.jpg Sarah is not known Name: Sarah Hair Colour: Redhead Hair Length: Normal Titsize: Small Attributes: Pussy: S Aliases: Usual Source: Image: Source: RefNo: OK to add (x for exclude) ? (y/n/x): y Model number is 2249 SQL: insert into models (modelno, mname, mhair, mlength, mtitsize, mattributes, maliases, musual, mimage, mstatus, mflag, mpussy, madded) values( '2249','Sarah' ,'Redhead','Normal','Small','','','','','A','N','S','9-OCT-2006') % |
| Legal Values In AddModel | |||
|---|---|---|---|
| Hair Colour | Hair Length | Titsize | Pussy |
| Blonde | Short | Tiny | Shaven |
| Brunette | Shoulder | Small | Trimmed |
| Redhead | Normal | Normal | Hairy |
| Dark | Long | Large | |
In practice, the addmodel command line is usually a bit more complex, lets consider an example from amkingdom.com.
% addmodel name=Erika hair=Brunette length=Long titsize=Tiny pussy=Shaven attrib utes='shaven tinytit tattoo' refno=eri046 altref=12475 source=AMK usual=amkingdo m.com image=amkingdom/Erika-1.jpg [...] % |
% cd image_location/redheads/smalltits/Sarah % addassoc Sarah Sarah_* 1. Sarah with Long Redhead hair and Small tits - model number=2249 Name: Sarah Hair Colour: Redhead Hair Length: Long Titsize: Small Attributes: shaven tattoo Aliases: Usual Source: Image: Sarah-1.jpg RefNo: 2249 Continue (y/n)? y DB record found: setno 10661, title: Sarah PinkDressNoPanties GardenBenchDildo Added association between Sarah (2249) and set 10661 % |
% generate redheads/smalltits/Sarah [...] COMPLETED: 12 new records inserted, 7 updated. Calling make_index() with redheads/smalltits/Sarah %all that is then needed is to do the appropriate addassoc command to associate the newly added sets with Sarah (see above). Generate can recursively scan from the top of the images tree (or from any point on the sub-tree), but probably best avoided if you have a large number of directories in the system.
The generate/updateinfo commands also possess knowledge of download records and if via a number of heuristics to do with the names, stems or name structure it determines that it knows of the set in question, it will retrieve additional information like model number, set type, source site and photographer from the download record and merge that information with what it can determine from the name of the directory and the model's attributes. The download record will be marked as having been successful and will disappear from the model's detailed page.
Additionally if the set in question has been unpacked by the web based unpack/placement tools, a file called ".unpack" will be used to pass information on the download record number from the download mechanism to the importation/catalogue system.
As was mentioned in the overview, certain keywords are recognised within
the directory name and used to define various special attributes in the
default metadata. Whether the metadata is manipulated manually, semi-
manually or automatically is controlled by the sauto flag for each set
record within the sets table. These guesses are performed by the function
guesscatinfo() in updateinfo. For now, it's probably
best to look at the source code of that function to get some idea of how
this works. Hopefully some more detailed documentation can be added in
due course.
updateinfo - work out set status and
attributes
Please see the information given in the section on generate above.
genvideo - import video files into the Wacs
system
Genvideo performs much the same functions as the combination of
generate and updateinfo for the importation of video clips into the Wacs
system. It actually also includes aspects of the updateinfo program
but re-written for the video context.
However the video naming convention is a lot simpler and
what meta data there is in inferred from the download record as very
little information can be gleaned from the name of the file itself.
Note that although the relative pathnames appear the same, genvideo
operates in a parallel space under the videos tree in the file system.
At present it requires the presence of a download record before it
will perform a new record addition - this can be created in SQL as
follows:
sql> select max(downloadno) from download; 2672 sql> insert into download (downloadno, dmodelno, dsite, dtype, dsetkey, > dsetname, darchive) > values( 2673,2249,'XYZ','V','sarah04.mpg', > 'Sarah - Pink Dress - Garden Bench','sarah04.mpg'); 1 row added. sql> commit; commit complete. sql> quit
To import a directory of Sarah's videos, you would do: genvideo
redheads/smalltits/Sarah and it will scan that directory for
.mpg, .wmv, .mov and .avi files. Note that the icons are automatically
referred to by the same pathname but in the vidicons directory. Therefore
for sarah01.mpg in videos/redheads/smallbreasts/Sarah, you
would place the corresponding icon file as sarah01.jpg in
vidicons/redheads/smallbreasts/Sarah.
updatestats - update model statistics
The model record keeps some basic statistics about the sets and types
of activity featured in those sets in order to better describe the model
and her activities (on camera). Of course, much of this information is
ultimately derived from the sets she features in; for instance, if she
features in a lesbian set, the assumption is that she does lesbian scenes
on camera! Obviously examining every set each time a model page is loaded
is unlikely to be very practical, so the schema design has this data
cached. Updatestats is the program that updates this cached attribute
data in the model record. It should be run periodically, probably nightly
via the cron command.
Populators
These commands read 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.
vendpop - populate the vendors table
This command 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.
photpop - populate the photographer table
This command 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 2006 is included in the XML file.
keywordpop - populate the keyword table
New in 0.7.3
This command reads the keywords.xml file and populates the keyword
table with some example keyword settings and priorities. There are about
eighty entries in the distributed file, which should provide some ideas
on how the system works. Basically each keyword has entries for attributes,
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.
Migrators
These commands allow the moving (or migration) of model and set details
between different installations of WACS. They also provide a way to dump
and reload the WACS database should you need to. The idea is that the
export dump file is a self-contained object which can be safely emailed
or transferred between systems of different types. An XML format container
is used, and the data objects stored inside it, including images such as
the model and set icons. Binary objects (like JPEG images) are stored
using the MIME base 64 standard.
wacsexport - export model details
This command creates an XML file containing details of a specific model
including her model record, head shot icon in both normal and big forms
if available, idmap records and the download records for all her sets that
have a known source. This file has the binary data encoded in base 64 so
that it can be safely emailed, cut-and-pasted, etc. The command is
invoked with just the model no as an argument, thus if Sarah is model no
7, running wacsexport with: wacsexport 7 will create a file
called "Sarah-7.xml" in the current directory.
wacsimport - import model details
This command imports an XML file containing details of a specific model
as exported by wacsexport above. It is invoked with the file
name of the XML export file, so following the example above, running
wacsimport with: wacsimport Sarah-7.xml would import Sarah's
details, icon(s) and idmaps into the local Wacs database. Note that
by default, a brand new model number will be issued on the new system
unless wacsimport determines that the same model already exists there,
quite possibly under another model number.
This it does by comparing the idmap entries - it assumes that if the
model is recorded by one site as being a certain ID on a remote site,
any new information about her should be loaded onto the record of a
model who has a reference to being the same ID on the same named remote
site. So, if the XML file says Sarah is "sar001" on site AMK, "55" on
site XYZ and "12789" on site TVW and we have a model who is "sar001" on
AMK, that model's records will be updated with extra ID mappings as "55"
on site XYZ and "12789" on site TVW.
wacsxmlout - export set metadata
New in O.7.3
This command creates an XML file containing the meta data relating to
a set (although not the set itself). This is used to transfer data
about a set along with the basic image zip files (or video clips) to
another Wacs installation. It also tries it's best to export something
meaningful about who the models featured in the set are.
wacsxmlin - import a set XML description and media
New in 0.7.3
This command imports a set from the combination of an XML exported by
wacsxmlout and a downloaded set in a zip/video file. It also attempts
to add any associations to models that it can deduce and find the model
numbers for.
Janitors
These are little utilities to help with cleaning out the cruft from the
Wacs system - duplicate sets, etc.
delset - delete an image set
Delset is passed a single argument of a directory name (which is assumed
to contain an image set known to Wacs) and proceeds to
delete the database records related to it in the correct order. Once
complete it moves the files into the "delset" directory of the download
directory where they can be checked on more time before the files
themselves are erased.