Feed Processing Reports
Common Feed Processing Errors
Newspaper Admin and User Guide
Transition To Production
Newspaper Feed Implementation Guide
OverviewNewspaper partners submit job postings and SearchMonster license requests to Monster's Newspaper Integration Service (NIS). Submissions are made in Monster XML format and do not require pre-existing user accounts or inventory. Job and SearchMonster license submissions may be made separately or combined.
Technical Skills NeededIn order for the implementation to be successful, the client's development team should have the following basic technical skills:
- General knowledge of the client's own intranet and systems
- XML coding and schema understanding
- FTP posting skills
Feed Processing OverviewThe newspaper XML feed process is as follows:
- Partner collects purchase data and converts into standard Monster XML format
- Partner drops off file on the Monster FTP server
- Monster moves the file to a batch server where it may be processed
- Monster processes the file, creating new accounts and inventory where needed
- Each valid posting may generate an account creation email (if a new account was created), with login information, to the address associated with the job/license. This is to notify the user that a Monster account was created for them.
- Monster populates an internal database with feed information (jobs processed, SearchMonster licenses granted, errors found, etc.)
- Monster sends a success/failure email to the feed processing notification email address provided by the partner, with a summary of the feed processing
- Newspaper Admin site is updated to reflect the transaction. Note that feeds with invalid XML will not show in Newspaper Admin.
Account Information from MonsterMonster will provide the following information so partners know where to drop off newspaper feeds with partner specific XML job feed information.
- FTP account information – login credentials
- Channel ID
- Username prefix
- File name format
DevelopmentThe newspaper partner is responsible for creating the XML feed and making sure it complies with Monster schemas. The feed may include only jobs, only SearchMonster license submissions or a combination of both. The section of the guide needed depends on what you are doing. See below.
- Job submissions only
- SearchMonster submissions only
- Job and SearchMonster submissions within the same Feed
Feed SamplesVarious XML feed samples may be found at URLs shown below. It is recommended that these be referenced to assist in development:
- Minimum required job fields:
- Standard XML job feed:
- Job feed with NIS Packages:
- Advanced XML job feed with Agency, Billing, Additional Products and SearchMonster license:
- SearchMonster standalone submission:
Creating the Job XML FeedThe XML job feed must be compliant with Monster schemas and the NIS process requirements. Failure to do so will cause feeds not to process. Note that there are some XML job elements required for the NIS process whereas in the schemas they may not be required. This is due to the NIS process having the ability to create accounts and inventory as part of feed processing. Those elements are highlighted within this document.
Key points in this area:
- The feed must comply with the Monster Standard XML schemas. The schemas may be found at:
- The table below provides:
- NIS specifics as some of the newspaper job XML field requirements are different than those for jobs posted directly to Monster's Business Gateway
- Hyperlinks to Monster schemas. Select XML field.
- Hyperlinks to lists of valid XML field entries, shown in comments column
- The XML file name has to be in the following format or else the entire file will not process and no emails will be sent out:
- Format: xmlprefix_*.xml
- Monster provides the value of xmlprefix
- The * may be anything, but it is strongly recommend that it include a date and time such as xmlprefix_YYYYMMDDHHMMSS.xml
- For example, here is a properly named file: newsabc_20110225013520.xml
- A Webservice Toolkit is available to test your xml feed against Monster's schemas. See Webservice Toolkit section of this document for more information.
- CDATA wrapper - when text includes special characters in XML, including HTML markup characters, (ex. <li>One</li>) it is recommended that the text be surrounded with the CDATA tag. If text uses XML/ HTML entities (ex. > < &) instead, then the CDATA tag should not be used.
- A list of common questions that have arisen as part of newspaper integrations may be found at: Newspaper-FAQs
|JobRefCode="xxxx"||YES||Recruiter specific term used to uniquely identify a job.
The combination of UserName and JobRefCode should be unique. That is, for each user, JobRefCode may not be used for more than one job board, except in job board groups. For example, a job was submitted with UserName = "username1", JobRefCode = "jrc1" and BoardName monsterId="1". If another job with UserName = "username1", JobRefCode = "jrc1" and BoardName monsterId="7190" is submitted, the submission will fail.
|JobComplete||NO||Set to "true" if providing.|
|<CompanyReference> /<CompanyName>||YES||This is the company name set on an account when initially created.|
|<Channel>||YES||Must be populated with the specific newspaper partner channel ID.|
|<JobLevel>||NO||A list of valid entries may be found at: JobLevel list|
|<JobType>||NO||A list of valid entries may be found at: JobType list|
|<JobStatus>||NO||A list of valid entries may be found at: JobStatus list|
|HideAll||NO||When set to "true", hides contact given and family name, company name, street address, street address2, city, state, postal code, phone, fax when viewing a job.|
|HideAddress||NO||When set to "true", hides contact street address, street address2, city, state and postal code when viewing a job.|
|HideStreetAddress||NO||When set to "true", hides street address only (NOT street address2) when viewing a job.|
|HideCity||NO||When set to "true", hides city when viewing a job.|
|HideState||NO||When set to "true", hides State when viewing a job.|
|HidePostalCode||NO||When set to "true", hides postalcode when viewing a job.|
|HideCountry||NO||No impact as country is not shown in standard job template.|
|HideEmailAddress||NO||Must be set to "true" along with setting DisableApplyOnline to "true" in order for apply button to be hidden. Note that email address is not displayed when viewing a job.|
|HideFax||NO||When set to "true", hides fax number when viewing a job.|
|HideName||NO||When set to "true", hides given name and family name when viewing a job.|
|HidePhone||NO||When set to "true", hides phone number when viewing the job.|
|<Contact>/<FamilyName>||YES||Last name of contact for the job posting.|
||NO||If one does not want the Company Name to be displayed in job search results and when viewing the job, set <hideCompanyName>="true" and <HideCompanyInfo>="true".
JobSearch: Shown below is what company name will be displayed in job search results and when viewing a job.
||YES||Street address of contact for the job posting.|
|<Contact>/<StreetAddress2< span>>||NO||Secondary address of contact for the job posting.|
|<Contact>/<City>< /span>||YES||City of contact for the job posting.|
|<Contact>/<State>||YES||State of contact for the job posting.|
||YES||Represents country of contact for the job posting.|
|<Contact>/<Phone phoneType="xx">||YES||Where xx has to be either "contact" or "fax" to be displayed. Other phone types may be provided but will not be displayed.|
|<Contact>/<E- mail>||See Notes||
|<HideCompanyInfo>||NO||When set to "true", company name in job search results and top portion of job view show as confidential. In addition, hides company name in "Job Summary" and "Contact Information" sections of job view.|
|<JobBody>||YES||Must be 25 characters minimum.|
|<YearsOfExperience>||NO||A list of valid years of experience entries may be found at: YearsOfExperience list|
|<CustomApplyOnlineURL>||NO||A valid url for ATS apply.|
|<JobPostingRefCode>||NO||Should not be included in the XML or should be left blank if unused.|
|<JobPosting desiredDuration="xx">||See Notes||
|<JobCategory>||YES||A list of valid job categories may be found at: JobCategory list|
|<IndustryName>||NO||A maximum of three may be submitted per job. Valid entries may be found at: Industry list|
|<nis:PONumber>||NO||Providing purchase order number is highly recommended|
<Frequency> 14 </Frequency>
<Duration> yy </Duration>
Creating the SearchMonster XML FeedThe newspaper integration service supports the ability to fulfill a 30-day national SearchMonster license purchases via newspaper partners. The XML format is similar to a newspaper job posting and is submitted the same way as newspaper job postings. License requests may be submitted in a feed by themselves or together with job postings. License requests do not have to be linked to a job posting. The rules for creating a SearchMonster XML submission are similar to submitting a job posting. The specifics are discussed below. Samples may be found here.
NOTE: Populating the SearchMonster XML requirements with default or non-valid information may produce errors. Please ensure valid user and customer contact information is provided. Failure to do so may result in the order not being processed.
The XML feed must be compliant with Monster schemas and the NIS process requirements. Failure to do so will cause feeds not to process.
- The feed must comply with the Monster Standard XML schemas. The schemas may be found at:
- The table below provides:
- SearchMonster license submission requirements
- Hyperlinks to Monster schemas. Select XML field.
- Various XML feed samples may be found at URLs shown below. It is recommended that these be referenced to assist in development:
- As with job postings, SearchMonster submissions require users to have a Monster account. If the user does not currently have an account with Monster, one will be created and an account creation email will be sent to the users email address provided in the feed.
- Only individual SearchMonster submissions that have failed need to be resubmitted for processing
|<nis:License licenseRefCode="xx">||YES||Recruiter specific term used to uniquely identify SearchMonster license.|
|<nis:UserName>||YES||Same requirements as for a job posting|
|<nis:CompanyReference> /<CompanyXCode>||YES||Same requirements as for a job posting|
|<nis:CompanyReference> / <CompanyName>||YES||Same requirements as for a job posting|
|<nis:Channel monsterId="xxxx">||YES||Same requirements as for a job posting|
|<nis:LicenseName>||YES||Must be set to SearchMonster.|
|<nis:Contact> / <GivenName>||YES||Same requirements as for a job posting|
|<nis:Contact> / <FamilyName>||YES||Must have ≥ 2 characters.|
|<nis:Contact> / <CompanyName>||YES||Must have ≥ 2 characters.|
|<nis:Contact> / <StreetAddress>||YES||Must have ≥ 5 characters.|
|<nis:Contact> / <StreetAddress2>||NO||Same requirements as for a job posting|
|<nis:Contact> / <City>||YES||Must have ≥ 3 characters.|
|<nis:Contact> / <State>||YES||Same requirements as for a job posting|
|<nis:Contact> / <CountryCode>||YES||Same requirements as for a job posting|
|<nis:Contact> / <PostalCode>||YES||Must have ≥ 4 characters.|
|<nis:Contact> / <Phone phoneType="xx">||YES||Must have ≥ 10 characters.|
|<nis:Contact> / <E-mail>||YES||Same requirements as for a job posting|
Webservice ToolkitMonster's Webservice Toolkit (http://integrations.monster.com/Toolkit) allows partners to test their XML against Monster schemas and find various enumerations that may be used within a job posting.
For newspaper integrations, the Webservice Toolkit may be used as follows:
- HOME PAGE - Select REALTIME POSTING on the top menu to return to this page
- INSERT YOUR REQUEST TEXT
- In the window below this, newspaper partners may either paste XML in here to be validated or may upload XML by using the "upload an XML document" link
- On the right hand side of the page, there's a list of XML job samples; the only ones applicable for newspaper integrations are located under "newspapers"
- SEND - Not used for newspaper integrations
- VALIDATE - Used to validate XML. Select once XML is pasted in the window above.
- ENVELOPE - Not used for newspaper integrations
- SAVE - Allows the XML pasted in the "Insert your request text" box to be saved
- CLEAR - used to clear content of window
- ENUMERATIONS - used for job postings
- This is located at the top of the page with a drop down menu where you may obtain information on Monster locations, industries, categories and various job attributes (job type, job level and job status are commonly used for newspapers).
- The default for all these items when first selected is Country = US and Language = English. For integrations outside of the US, on the lower right hand side of the page select the "Country" and the "Language" to display the valid country/language enumerations.
- These items will help you select what to populate in these XML fields
- DOCUMENTATION - Not used for newspaper integrations
Testing the XML Feed
- Test locally using Monster's Webservice Toolkit (http://integrations.monster.com/Toolkit)
- Validate the XML job feed by pasting the XML in the open window and select "Validate". Note that this validator is limited and may not identify some problems due to various NIS specific requirements not being met in a file. Please see next bullet about additional testing assistance.
- Test in production
- Name the test feed file *_test.xml, e.g. monster_20181012_test.xml
- Drop test file in the same FTP location as for production files
- The jobs will be created in Monster's test job boards
- The RefCode of a test job or SearchMonster license will be the submitted RefCode + "t". Since the maximum length of RefCode in the database is 50 characters, if the submitted RefCode of a test job or SearchMonster license is at least 50 characters, an error message will be issued and the test will fail.
- SearchMonster licenses will be created with duration of 0
- Emails will be sent to the same email addresses as for production files
- When testing, it is recommended that you limit the number of jobs/SearchMonster licenses as for each successful posting, you may receive up to two (account creation, SearchMonster confirmation) emails. These emails are for test purposes only and should be deleted.
- Evaluating the test feedback
- The newspaper partner should review the test file results, make the appropriate changes and drop off additional test files as needed
- Invalid XML may be caused by one or multiple job/SearchMonster license submissions within a feed. These types of failures cause the entire feed to fail. Once the cause is identified, the whole file must be resubmitted for processing.
- For valid XML feeds, only resubmit individual jobs that have failed for reprocessing. It is not required to resubmit an entire feed.
Feed Processing Reports
Account Creation EmailOnce a file processes successfully, a standard Monster email is sent to clients when a new account is created. This email provides the client with login credentials (username and password). Click here for a sample of this email.
Feed Processing Results EmailThis report includes a summary email as well as an attached csv file containing details of the processing done on the submitted xml file.
Click here for a sample of a feed processing result email.
Click here for a sample of the attached csv file.
The recommended email address is "firstname.lastname@example.org". The newspaper partner will need to supply Monster with this address with the correct "newspapername" inserted. Also, this email address must be set up at newspaper partner's site, with the appropriate email distribution list, that a partner can manage and make changes locally.
An example of an email address is email@example.com. Please email firstname.lastname@example.org with this information.
SearchMonster Purchase Receipt EmailIf a feed file contains a request for a SearchMonster license, a SearchMonster purchase receipt is created. Click here for a sample of this email.
Common Feed Processing ErrorsA list of common newspaper errors may be found here.
Newspaper Admin and User GuideNewspaper Admin is a tool available to the newspaper partner. This provides the ability to view the status of job/SearchMonster feeds and their content, preview/edit/expire jobs, find companies or users and manage their jobs. Partners are required to provide a list of names and email addresses of those who need access. Monster will set up Newspaper Admin accounts and email the login credentials directly to the users. A user guide may be found here.
About Newspaper Admin security:
- If the last login date is 30 days prior, the users account will be automatically disabled. The user would need to send an email to email@example.com to get the account re-enabled.
- If the last login date is 60 days prior, the users account will be automatically deleted. The user would need to send an email to firstname.lastname@example.org with their name and email address to get a new account created.
Transition to Production
- Review Feed Spec and Documentation
- Provide Monster with feed source machine IP address(es)
- Provide Monster with a job feed processing success/failure email address
- Provide Monster with a list of contacts for Newspaper Admin access
- Create and provide XML test feeds
- Complete Testing – require three successful feeds prior to transitioning to production
- Set Implementation date with Monster
- Transition to Production
ContactsTest issues: email@example.com
Production issues: firstname.lastname@example.org
- What is the unique identifier for a job?
- The unique identifier for a job is the combination of UserName and JobRefCode.
- Are jobs locked once they are edited online?
- No. All information sent through the Newspaper Integration Service will be applied to the postings. The jobAction attribute value controls the action performed. The "addOrUpdate" value will add a job if the given “JobRefCode and UserName” is not in the system or update the job if it is found. The "add" value will add a new posting unless the job attribute enforceUniqueness="true". That attribute will cause an ad to fail if the job is already in the system.
- What is the difference between JobRefCode and JobPostingRefCode?
- The JobRefCode is required to interface with the Business Gateway. It is the unique identifier for the job under the given UserName. The JobPostingRefCode is an extended reference code that allows the interface to search on another unique string.
- May I create a list that matches the Monster job category list to our AdBaseE category list?
- Yes. Monster’s partner, Philly.com, may be able to provide this mapping.
- What happens if my email address is not deliverable?
- If the email is correctly formatted, but undeliverable, no error will be returned.
- May I resend the same job in successive feed files?
- Yes, but the jobAction=”addOrUpdate” signifies that the data you are sending overrides what is currently in the database. This means that any changes made by an online User through the UI will be wiped out by the feed. Another option is to send jobAction=”add” for all jobs in the file. This will disable updates through the feed interface. Monster suggests that you send only new or updated jobs through the feed and keep jobAction=”addOrUpdate”. Remember, every job successfully run through the service will trigger a thank you letter to your client.
- What text must be included in CDATA sections?
- Any text that includes invalid XML characters without HTML encoding, e.g. "&"
- Are job expiration dates different if the job comes through the newspaper integration service versus through the Monster user interface?
- Jobs submitted through the Monster user interface typically expire in 60 days. Jobs submitted through the newspaper integration service process expire in the number of days communicated in the xml feed, thirty days or less.
- If the same feed is sent twice, how does Monster know to charge only once for the job?
- Jobs that come through the feed process are charged based on JobID. The JobID’s will not change unless the file contains a different Username/JobRefCode combination.