Introduction
Wonderkind now allows XML uploads in Standard and Advanced formats. This change is significant for users who previously faced compatibility issues with these two different XML formats.
Key Differences
Standard XML
Indeed XML: Standard XML is widely recognized and used across various platforms.
Language Flexibility: It differs mainly in language, which you need to add manually when using Wonderkind.
Advanced XML
Customized for Wonderkind: It's specifically tailored to fit the unique requirements of the Wonderkind platform.
Unique Fields: Contains specific fields that align with the functionalities of Wonderkind.
Benefits of the Update
Enhanced Compatibility: You can now upload the Standard XML files directly to Wonderkind, making the process smoother.
Expanded Functionality: This update allows you to leverage the Standard format, broadening Wonderkind's applicability.
Simplified Workflow: The integration simplifies the process, making it more user-friendly.
XML Element Comparison
Advanced XML | Standard XML |
<job> <title> <referencenumber> <url> <company> <location> (used twice) <country> <postal_code> <street_address> <ad_description> <salary> <education> <category> <experience> <language> <benefits> <po number> <cpc_cap> <cpa_cap> <clicks_cap> <budget> <image>
| <?xml ?> <source> <publisher> (ATS developers only) <publisherurl> (ATS developers only) <job> <title> <date> <referencenumber> <requisitionid> <apijobid> <url> <company> <sourcename> (ATS developers only) <city> <state> <country> <postalcode> <streetaddress> <email> <description> <salary> <education> <jobtype> <category> <experience> <expirationdate> <tracking_url> <remotetype> <lastactivitydate> |
Notes
N/A Data: If a cell is left empty in the Advanced XML, the data is considered N/A.
City and State Elements: Wonderkind does not use
<city>
or<state>
elements; it uses<location>
instead.Multilingual Posting on Standard XML: For posting the same job in multiple languages, the Standard format requires creating a unique job in the XML for every language.
Conclusion
Wonderkind's move to accommodate a Standard XML marks a significant step towards user convenience and platform versatility. This integration bridges the gap between two different XML formats, enhancing the overall user experience.
β