wacsxmlin — imports set details from a WACS XML export file
wacsxmlin [modifiers] XML_file_name
--defaultspecifies that the set should be stored in the calculated default location for this WACS server instead of it's location on the original server.
--clonespecifies that this should be an EXACT copy of the original - same location, set number, etc. Useful in creating clone web servers for resilience, etc.
--asnewtells wacsxmlin to mark this as a newly created set so it appears in the new sets/videos index.
The wacsxmlin command is a tool to import a WACS
set export XML file containing information about a set to allow it to be
transported between different WACS installations.
wacsxmlin is invoked with the name of the set XML file
created previously by the wacsxmlout command on another
WACS installation.
For a set numbered 123 on the originating site, the inputs to
wacsxmlin would be set123.xml and
set123.zip.
This set will normally recieve a new set number on importation into the
new WACS installation.
Sine the XML file wacsxmlin reads contains the set information, all associated download records, associations and idmap records for all of the models featured in the set, wacsxmlin does it's best efforts to find and associate the set being added to those models who feature in it on the new WACS installation. If the export file contained them, wacsxmlin will unpack the thumbnail icon, official icon and any additional icons related to the set.
Sample XML files can be downloaded from the resources section on our demonstration site www.pinkmetallic.com as they become available and can be used to import our sets into your own installation. Since these sets are released under the Creative Commons license, you are free to import them into your WACS server and even include them on a commercial site if you wish to, providing the PinkMetallic.com branding remains intact. We can provide proof of age documentation to US-based sites in order to conform to 18 USC 2257 for a small fee.
wacsxmlin in WACS 0.9.0 and higher understands both version 1 (version 0.8.6 and earlier) and version 2 (version 0.9.0 and later) files. Either type may be used on an installation providing the database schema is up to date.