Using the export function in Xinet

Xinet includes an export executable which will allow you to create either flat files or XMP output from your Xinet assets. This provides portability of your Xinet data for use in applications that read these formats.

There are two kinds of files that can be exported from Xinet using the export command: flat files and XMP files. Flat files are easily imported by a variety of programs, including spreadsheet applications and other databases. XMP is an XML-based standard written by Adobe and used for data storage in their more recent applications, including the Adobe Creative Suite. To learn more about XMP, visit Adobe’s XMP Web site at http://www.adobe.com/products/xmp/main.htm/.

Both flat files and XMP files may be exported for single documents, folders of documents, or the entire database. When the export command is run for a folder, export creates a single output file containing all metadata for all files inside that folder. When the export command is run for a single file, only information about that file will be exported.

For the most up-to-date information about export command options, rely on its online usage summary. (Type the command without providing any arguments.)

Note: For standardization, the export command exports all text in utf8 (Unicode) on Unix servers.

Please Note: This should be typed as a single line.

To export a flat file, the syntax is:

/usr/etc/venture/bin/export -xml [/path/to/output/file] [/path/to/file/or/directory]

By default, the flat files use a tab field separator.

A sample flat-file export for a single file looks like this:

# Export File generated by Xinet.

# To import back into WebNative, run:

# import <filename> -s09 -r0A -g232073746172743A0A "-iUnixPathName" "-iMacName" -TType -CCreator "-mModification Date'YYYY-MM-DD hh:mm:ss'" "-cCreation Date'YYYY-MM-DD hh:mm:ss'" "-b%1%"

Each of the fields in the database is represented in the flat file export, even if that field does not have a value set for this file. These flat files are not very easy for a person to read, but they are easily imported into a variety of other programs.

To export an XMP file from Xinet, the syntax is:

/usr/etc/venture/bin/export [/path/to/output/file] -xml
[/path/to/file/or/directory]

A sample XMP export for a single file looks like this:

<x:xmpmeta xmlns:x='adobe:ns:meta/'>

xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'

xmlns:rdfs='http://www.w3.org/2000/01/rdf-schema#'

xmlns:iX='http://ns.adobe.com/iX/1.0/'>

<rdf:Description
rdf:about='http://octane//chilly/files/myfile.jpg#'

xmlns:xap='http://ns.adobe.com/xap/1.0/'>

<xap:CreateDate>2004-03-26T21:52:19Z</xap:CreateDate>

<xap:ModifyDate>2004-03-26T21:52:21Z</xap:ModifyDate>

<xap:Format>application/data</xap:Format>

<xap:CreatorTool>Adobe Photoshop</xap:CreatorTool>

<rdf:Description
rdf:about='http://octane//chilly/files/myfile.jpg#'

xmlns:dc='http://purl.org/dc/elements/1.1/'>

<dc:description>This is myfile.jpg. It is a picture.</dc:description>

<dc:format>application/data</dc:format>

<dc:creator>Xinet, Inc.</dc:creator>

<dc:title>myfile.jpg</dc:title>

<rdf:li>xinet</rdf:li>

<rdf:li>fullpress</rdf:li>

<rdf:li>webnative</rdf:li>

<rdf:Description
rdf:about='http://octane//chilly/files/myfile.jpg#'

xmlns:stDsp='http://ns.adobe.com/xap/1.0/sType/FileDisposition#'

xmlns:xapS='http://ns.adobe.com/xap/1.0/s/'>

<stDsp:filename>myfile.jpg</stDsp:filename>

<stDsp:OS>Unix</stDsp:OS>

<stDsp:directoryPath>/chilly/files</stDsp:directoryPath>

<rdf:Description
rdf:about='http://octane//chilly/files/myfile.jpg#'

xmlns:photoshop='http://ns.adobe.com/photoshop/1.0/'>

<photoshop:CaptionWriter>Xinet, Inc.</photoshop:CaptionWriter>

<photoshop:SupplementalCategories>

</photoshop:SupplementalCategories>

<rdf:Description
rdf:about='http://octane//chilly/files/myfile.jpg#'

xmlns:xwnv='http://ns.northplains.com/ns/xinetschema#'

xmlns:xwnvtmp='http://ns.northplains.com/ns/xwnvtmp#'>

<xwnv:FileID>75578</xwnv:FileID>

<xwnvtmp:ObjectName>myfile.jpg</xwnvtmp:ObjectName>

<xwnvtmp:Keywords>xinet

<xwnvtmp:Byline>Xinet, Inc.</xwnvtmp:Byline>

<xwnvtmp:Caption>This is myfile.jpg. It is a picture.</xwnvtmp:Caption>

<xwnvtmp:CaptionWriter>Xinet, Inc.</xwnvtmp:CaptionWriter>

<xwnvtmp:onoroff>1</xwnvtmp:onoroff>

<xwnvtmp:boolean-check>0</xwnvtmp:boolean-check>

<rdf:Description
rdf:about='xwnvtmp:ObjectName' xmlns:
xwnv='http://ns.northplains.com/ns/xinetschema#'
xmlns:xwnvtmp='http://ns.northplains.com/ns/xwnvtmp#'>

<xwnv:string xwnv:description='IPTC-NAA Record 5' />

<rdf:Description rdf:about='xwnvtmp:Keywords'
xmlns:xwnv='http://ns.northplains.com/ns/xinetschema#'
xmlns:xwnvtmp='http://ns.northplains.com/ns/xwnvtmp#'>

<xwnv:string xwnv:description='IPTC-NAA Record 25' />

<rdf:Description
rdf:about='xwnvtmp:Byline' xmlns:xwnv='http://ns.northplains.com/ns/xinetschema#' xmlns:xwnvtmp='http://ns.northplains.com/ns/xwnvtmp#'>

<xwnv:string xwnv:description='IPTC-NAA Record 80' />

<rdf:Description
rdf:about='xwnvtmp:Caption'
xmlns:xwnv='http://ns.northplains.com/ns/xinetschema#'
xmlns:xwnvtmp='http://ns.northplains.com/ns/xwnvtmp#'>

<xwnv:string xwnv:description='IPTC-NAA Record 120' />

<rdf:Description rdf:about='xwnvtmp:CaptionWriter' xmlns:xwnv='http://ns.northplains.com/ns/xinetschema#'
xmlns:xwnvtmp='http://ns.northplains.com/ns/xwnvtmp#'>

<xwnv:string xwnv:description='IPTC-NAA Record 122' />

<rdf:Description
rdf:about='xwnvtmp:onoroff'
xmlns:xwnv='http://ns.northplains.com/ns/xinetschema#'
xmlns:xwnvtmp='http://ns.northplains.com/ns/xwnvtmp#'>

<xwnv:bool xwnv:description='on or off' xwnv:booldisplayformat='check box' />

<rdf:Description
rdf:about='xwnvtmp:boolean-check'
xmlns:xwnv='http://ns.northplains.com/ns/xinetschema#'
xmlns:xwnvtmp='http://ns.northplains.com/ns/xwnvtmp#'>

<xwnv:bool xwnv:description='' xwnv:booldisplayformat='check box' />

Because XMP is a standard based on XML, it is readable by more than just Adobe’s suite of products. You can also use this format for import into some XML-aware applications.