Your listings should comply with the following:
In addition we ask that all organizations:
We reserve the right to remove any organization or feed from our index if they fail to adhere to the above guidelines.
We accept feeds only in XML format.
XML feeds should be well-formed and follow W3C requirements on well formed XML document. The best way to ensure this is to run your prospective feed through an xml validator.
All job content must be inside CDATA sections to avoid issues processing your XML feed.
Please provide the proper character encoding for your feed in the XML header. If you're not specifying the proper encoding your listings may come through with weird characters.
JobInventory can fetch feeds from your site via HTTP, HTTPS, or FTP. We only download your feed as often as it updates, but we check often.
Document should have root tag <listing> and the following tags under it.
Each job listings should contain required and optional fields defined below. We like as much information about the listing as possible. The more information we have, the more likely a user is to find the listing. To that end, we accept a lot of fields with different information. Additionally, *some fields are required *and you can't submit your feed without them (the field has to be present and there has to be content in it).
Each job listing should include these fields.
The location fields indicate the location of the item being listed. For location-based search to work, it is highly recommended that each listing specify its location at least down to the city or zip/postal code level.
Location information should be defined under location tag and might contain the following field.
The more of these additional fields that are included for a listing, the more likely that listing is to be found in searches.
The occupation of the job being listed. We strongly advise to use one of the accepted values for category field.
Format: text
Accepted Values:
The title of the listing
Format: text. Maximum length is 500 chars.
The description of the listing
Format: text. Maximum length is 20,000 chars.
The date/time at which the listing was created. If not specified then time of feed file generetion used by default.
Format: YYYY-MM-DD, or RSS format (i.e. 2004-07-16T14:00:00-07:00).
The URL of the details page for this listing. This URL must have relevent information about the listing. The URL must be unique in the feed, two different listings are not allowed to have the same URL.
Format: Fully qualified url.
The location of the listing. We highly recommend define location at least up to city level by including country, state and city information.
Format:
Unique ID for this listing. You must use the same id with a listing in subsequent versions of the feed.
Format: Text.
The characteristics of the employment being offered. We strongly advise to use one of the accepted values for jobtype field.
Format: Text.
Accepted Values:
Education required for the job position. We strongly advise to use one of the accepted values for education field.
Format: Text.
Accepted Values:
Experience required for the job position. We strongly advise to use one of the accepted values for experience field.
Format: Text
Accepted Values:
Listing publisher name.
Format: Text.
<?xml version="1.0" encoding="utf-8"?> <listing> <ctime>2011-03-01T14:00:00-07:00</ctime> <entry> <id><![CDATA[101647600000100]]></id> <title><![CDATA[Example title]]></title> <location> <country><![CDATA[US]]></country> <state><![CDATA[CA]]></state> <city><![CDATA[Sacramento]]></city> <postalcode><![CDATA[95814]]></postalcode> </location> <description><![CDATA[Example description]]></description> <date><![CDATA[2011-03-01T14:00:00-07:00]]></date> <url><![CDATA[http://www.example.com/listing-url.html]]></url> <category><![CDATA[Community and Social Service]]></category> <company><![CDATA[Example Company]]></company> <jobtype><![CDATA[Contract]]></jobtype> <education><![CDATA[Doctorate]]></education> <experience><![CDATA[5-7 years]]></experience> </entry> </listing>