Documentation

Back to Import

XML File upload

• Max. 1 upload (first file will be overwritten if second upload is started)
• Possible XSD Schema validation-errors will be shown straight after upload
• Semantic errors in the XML code will be recorded during XML processing and the upload will be marked as faulty

XML Processing

• The key <importId>...</importId> is a required key. If an importId is set, the key "hasChanges" must be set to true ( <hasChanges>true</hasChanges> ), otherwise, the listing will not be updated
• Has the listing a importID but can’t be found in our system (mapped), a new listing will be created independently of the “hasChanges” status
• Car (CarDB) will be mapped through the user’s plain text input. If there is a match, the respective car will be used, if not, a new entry will be created which will have to be reviewed by the editors before publication
• If a new CarDB type with a construction year between multiple CarDB types, the latest CarDB type will be selected
• As soon as a listing was added to the system via the XML import, changes on the CarDB type will not be overwritten with the next XML (CarDB is App Master)
• Pictures/Files must have accessible URLs. Assignment of pictures happens via Hash on the Binary. Therefore, if there’s a file stored on http://www.picture.com/picture1 that was initially used to create a listing, another picture will later be stored at the same URL. If the picture for the respective listing changes with the next XML upload (when <hasChanges>true</hasChanges> is on the listing)
• If a listing has the status “published”, it will be validated before publication. If this fails, the listing will be saved as “draft”
• The position of pictures within the listing are determined by the order of pictures in the XML file, descending from top to bottom.

XSD Schemas

The following asset types can be uploaded

• application/msword
• application/rtc
• application/rtf
• text/plain
• text/richtext
• application/pdf
• image/png
• image/jpeg
• image/jpg
• image/gif