Newspaper Job Feed Implementation Guide

 

Overview

Newspaper partners submit job postings and Power Resume Search (PRS) 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 PRS license submissions can be made individually or can be combined.
 

Technical Skills Needed

In 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 Overview

The newspaper XML feed process is as follows:
    1. Partner collects purchase data and converts into standard Monster XML format.
    2. Partner drops off file on the Monster FTP server.
    3. Monster moves the file to a batch server where it can be processed.
    4. Monster processes the file, creating new accounts and inventory where needed.
    5. 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. 
    6. Monster populates an internal database with feed information (jobs processed, PRS licenses granted, errors found, etc.).
    7. Monster sends a success/failure email, to the feed processing notification email address provided by the partner, with a summary of the feed processing.
    8. Newspaper Admin site is updated to reflect the transaction. Note that feeds with invalid XML will not show in Newspaper Admin.
 

Account Information from Monster

Monster 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
 

Development

The newspaper partner is responsible for creating the XML feed and making sure it complies with Monster schemas. The feed can include only jobs, only PRS license submissions or a combination of both. The section of the guide needed depends on what you are doing. See below.
 

Feed Samples

Various XML feed samples can be found at URL's shown below. It's recommended that these be referenced to assist in development:
 

Creating the Job XML Feed

The 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:
    1. The feed must comply with the Monster Standard XML schemas. The schemas can be found at:
    2. 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.
    3. 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 * can be anything, but strongly recommend it includes a date and time: xmlprefix_YYYYMMDDHHMMSS.xml
      • For example, here is a properly named file: newsabc_20110225013520.xml
         
    4. A Webservice Toolkit is available to test your xml feed against Monster's schemas. See Webservice Toolkit section of this document for more information.
    5. 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.
    6. A list of common questions that have arose as part of newspaper integrations can be found at: Newspaper-FAQs
XML Field Required? Notes
JobRefCode="xxxx" YES Recruiter specific term used to uniquely identify job.
JobAction YES
    1. "addOrUpdate" - recommend using as this allows new ads to be posted and updates to active jobs.
    2. "add" - allows new ads to be posted. Updates to active jobs not allowed.
    3. "delete" - use to delete a job.
JobComplete NO Set to "true" if providing.
<UserName> YES
    1. Must be unique and contain the prefix supplied by Monster.
    2. 18 characters maximum.
    3. Valid entries include numbers, letters, dashes, underscores and plus signs.
    4. Greater than or less than signs, single or double quotes, ampersand, tab, space or any other symbols should not be used as part of a username.
    5. An example of a unique username would be to create this using a combination of <Prefix><Account>_<Email address>. Note that the email address must exclude the "@" symbol.
    6. If partner job feeds come from various sources, it is recommended that the username be the same for a particular user such that all their jobs show under one Monster account.
<CompanyXcode> YES
    1. Must be unique per user and 20 characters maximum.
    2. Must equal x's around a lowercase username (xusernamex).
<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.
<JobTitle> YES  
<JobLevel> NO A list of valid entries can be found at: JobLevel list
<JobType> NO A list of valid entries can be found at: JobType list
<JobStatus> NO A list of valid entries can 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.
HideCompanyName NO
    1. When set to "true", hides contact company name in "Job Summary" section of job view. Does NOT hide company name displayed on top portion of job.
    2. When set to "true" and HideCompanyInfo is set to "true", company name will not be displayed in job search results nor when viewing a job. Company confidential is displayed.
HideContactInfoField NO No impact.
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>/<GivenName> YES
    1. First name of contact for the job posting.
    2. All <Contact> data provided will also be used as billing information. If billing information is different than contact information, then <nis:billinginformation> should be populated.</nis:billinginformation>
<Contact>/<FamilyName> YES Last name of contact for the job posting.
<Contact>/<CompanyName> 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.

JobSearch:
    1. The company name in job search results will always be the company name on the account (see <CompanyReference>/<CompanyName> for more information) unless the company is an ad agency. In that case, <contact>/<companyname> will be displayed.</companyname></contact>
    2. If provided and if company on the account is an ad agency, <Contact> / <CompanyName> is the company name that will be displayed in job search results.
JobView:
    1. If provided, <Contact>/<CompanyName> is the company name that will be displayed when viewing a job.
    2. If not provided, the company name (<CompanyReference>/<CompanyName> provided when the account was first created) associated with the user's account will be displayed when viewing a job.
<Contact>/<StreetAddress> YES Street address of contact for the job posting.
<Contact>/<StreetAddress2> NO Secondary address of contact for the job posting.
<Contact>/<City> YES City of contact for the job posting.
<Contact>/<State> YES State of contact for the job posting.
<Contact>/<CountryCode> YES Represents country of contact for the job posting.
<Contact>/<PostalCode> See Notes
    1. This postal code or the postal code under <JobPosting>/<Location> is required.
    2. United States postal codes must only be 5 or 9 digits. No hyphens are allowed.
<Contact>/<Phone phoneType="xx"> YES Where xx has to be either "contact" or "fax" to be displayed. Other phone types can be provided but will not be displayed.
<Contact>/<E-mail> See Notes
    1. Must have valid formatting.
    2. Only one allowed per job posting
    3. Is never displayed to the seeker. The only time an email address will be displayed is if it's included in the <JobBody>.
    4. This is where account creation emails are sent. Unless an <nis:AgencyInformation> email address is provided, then the account creation email will be sent to <nis:AgencyInformation>/<Contact>/<E-mail>.
    5. This is the email address resume submissions are sent when the job seeker uses Monster apply online. No matter if the account is an ad agency or not.
<PhysicalAddress> NO
    1. Located between the <Contact> and <DisableApplyOnline> elements.
    2. Represents a job's physical location.
    3. Not used to match a seekers search criteria.
    4. If provided, this is displayed under "location" to the job seeker. If not provided, <JobPosting>/<Location> will be displayed.
    5. If provided, typically includes <City>, <State>, <CountryCode> and <PostalCode>. <StreetAddress> and <StreetAddress2> may be provided as well.
<DisableApplyOnline> NO
    1. When set to "false", allows job seekers to apply for jobs online.
    2. When set to "true" along with hideEmailAddress set to "true", job seekers will not be able to apply for a job online. In this case, the job body must contain information for seekers to apply for a job.

      Note in some cases, an email address or apply link in the job body may be copied and used as the target for the apply button.
<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 can be found at: YearsOfExperience list
<JobPostingRefCode> NO Should not be included in the XML or should be left blank if unused.
<JobPosting>/<Location> YES
    1. Represents the location/search region where the job will be advertised.
    2. This postal code or the postal code under <JobInformation>/<Contact>/<PostalCode> is required.
    3. Typically includes < City>, <State>, <CountryCode>, <PostalCode> and <Continent>.
    4. This does not have to be the same location compared to where the job is physically located (see <PhysicalAddress>).
    5. In jobview, this is displayed under "location" unless is provided, then <PhysicalAddress> will be displayed.
<JobPosting desiredDuration="xx"> See Notes
    1. Where "xx" must equal a valid Monster product (7, 14 or 30 day duration).
    2. Either this or <jobactivedate> and <jobexpiredate> or some combination of both must be provided. The valid combinations are shown in the table below. </jobactivedate>
desiredDuration <JobActiveDate> <JobExpireDate>
Provided Default to day job processed Calculated
Provided Provided Calculated
Not Provided Provided Provided
<JobCategory> YES A list of valid job categories can be found at: JobCategory list
<JobOccupation> YES
    1. Can contain a minimum of one and a maximum of three per job.
    2. A list of valid occupationId's for given job categories can be found at: JobOccupation list
    3. Recommend the use of "other" occupation be minimized.
<BoardName> YES
    1. When posting to an individual job board, set as follows:
      1. Monster board: <BoardName monsterId="1"/>
    2. When posting to multiple job boards, set as follows:
      1. Monster & Veterans <BoardName boardGroupId="1494"/>
      2. Monster, Diversity & Veterans (Complete) <BoardName boardGroupId="1495"/>
      3. Monster & Diversity <BoardName boardGroupId="42"/>.
<JobActiveDate> See Notes
    1. Either this and <jobexpiredate> or some combination of these two along with desiredDuration must be provided. See table under <JobPosting desiredDuration="xx">.
    2. Must be in this format YYYY-MM-DDT00:00:00
    3. Recommend setting the time portion of this element to T00:00:00.
    4. The difference between <JobActiveDate> and <JobExpireDate> must equal a valid Monster product (7, 14 or 30 day duration). If not, the job will fail.
    5. If used, the difference between <JobActiveDate> and <JobExpireDate> must be set to 30 days for the Gold Job posting package.
<JobExpireDate> See Notes
    1. Either this and <jobactivedate> or some combination of these two along with desiredDuration must be provided. See table under <JobPosting desiredDuration="xx">. </jobactivedate>
    2. Must be in this format YYYY-MM-DDT00:00:00
    3. Recommend setting the time portion of this element to T00:00:00.
    4. The difference between <JobActiveDate> and <JobExpireDate> must equal a valid Monster product (7, 14 or 30 day duration). If not, the job will fail.
    5. If used, the difference between <JobActiveDate> and <JobExpireDate> must be set to 30 days for the Gold Job posting package.
<IndustryName> NO If submitted, can provide a minimum of one and a maximum of three per job. Valid entries can be found at: Industry list
<nis:BillingInformation> NO
    1. Provide only if the billing information is different from the information provided under <JobInformation>/< Contact>.
    2. The information in this section of the XML should contain that of the one who is paying for the job posting.
    3. If only some of the <nis:BillingInformation> is provided then Monster will supplement the missing information by using the <JobInformation>/<Contact> data, except for the Company Name which is retrieved from <CompanyReference>/<CompanyName>.
    4. If not provided, then Monster will use the <JobInformation>/<Contact> data, except for the Company Name which is retrieved from <CompanyReference>/<CompanyName>.
<nis:PONumber> NO Providing purchase order number is highly recommended
<nis:AgencyInformation> NO
    1. Provide only if the person or company managing the job posting is different than the contact for the job posting (located under <JobInformation /> <Contact> ).
    2. The information in this section of the XML should contain that of the one who is responsible for the account.
    3. This element allows for ONLY newly created accounts to be tagged as an Ad Agency. By populating some or all of this information in this element of the XML, Monster will create a new account as an Ad Agency.
    4. If only some of the <nis:AgencyInformation> is provided then Monster will supplement the missing information by using the <JobInformation>/<Contact> data, except for the Company Name which is retrieved from <CompanyReference>/<CompanyName>, to create the Ad Agency account.
    5. Jobs posted for Ad Agency accounts will have the <JobInformation>/<Contact>/ <CompanyName> displayed (unless <HideCompanyInfo> is set to true) in job search results. If <JobInformation>/<Contact>/<CompanyName> is not provided, then the company name on the account will be displayed in job search results.
    6. Resumes are sent (when Monster's apply online is used) to the email address located under <JobInformation>/<Contact>/<E-mail> no matter if the account is an ad agency or not.
    7. Account creation emails are sent to <nis:AgencyInformation>/<nis:Contact>/<E-mail> (if provided). Otherwise, if not provided, account creation emails go to <JobInformation>/<Contact>/<E-mail>.
    8. Existing accounts cannot be tagged as an agency through the NIS feed. Please contact Monster Customer Central.
<nis:Autorefresh desired="xx">
<Frequency> 14 </Frequency>
NO
    1. The values for xx are "true" or "false". A true value makes the job refresh (move to the top of job search results) after 14 days.
    2. The only option for frequency value is 14.
    3. Not available on 7 or 14 day job postings.
    4. This is a billable option.
<nis:CareerAdNetwork desired="xx">
<Duration> yy </Duration>
NO
    1. The values for xx are "true" or "false". A true value will set CAN (Career Ad Network) on the job. CAN allows one to enhance Monster Job Posting with targeted advertising on the Monster network and its diverse partner websites.
    2. The values for yy are 7, 14 and 30 days.
    3. This is a billable option.
<nis:Bolding desired="xx"> NO
    1. The values for xx are "true" or "false". A true value will bold the job title in job search results.
    2. This is a billable option.
<nis:TwitterSingleCard desired="xx"> NO
      Where xx are "true" or "false". A true value will create a single TwitterCard.
<nis:NISPackage monsterId="xx"> NO
      Where xx = 1 for Gold and 2 for Platinum.
 

Webservice Toolkit

Monster'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 can be used as follows:
    1. HOME PAGE - Select REALTIME POSTING on the top menu to return to this page.
    2. INSERT YOUR REQUEST TEXT
      • In the window below this, newspaper partners can either paste XML in here to be validated or can 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".
    3. SEND - Not used for newspaper integrations.
    4. VALIDATE - Used to validate XML. Select once XML is pasted in the window above.
    5. ENVELOPE - Not used for newspaper integrations.
    6. SAVE - Allows the XML pasted in the "Insert your request text" box to be saved.
    7. CLEAR - used to clear content of window.
    8. ENUMERATIONS - used for job postings
      • This is located at the top of the page with a drop down menu where you can 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.
    9. DOCUMENTATION - Not used for newspaper integrations.
 

Testing the XML Feed

    1. 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.
    2. Test using Monster's test environment
      • Email Monster's Business Integration team (mabiz@monster.com) with a success/failure email address that will be used for test purposes.
      • Unless otherwise specified, drop test file off in TEST\INBOUND folder of your FTP account and email mabiz@monster.com stating a test file is available.
      • The test file will automatically process through MITE (Monster's Integrated Test Environment) and a success/failure email (feed processing results) will be sent to the email address provided. The email body will contain the results and an attached CSV file (sample located here) will provide additional details about add on features and PRS licenses.
RefCode Product Monster Id Result Duration Diversity Veteran Bolding Auto Refresh CAN CAN Duration Twitter Card Gold Pack Platinum Pack Search Postal Code Error Warning
200-4123 Job 191234598 Pass 30 Yes Yes Yes Yes No x Yes No No x    
210-4100 Job 191234597 Pass 7 Yes Yes Yes No No x Yes No No x    
220-4160 Job 191234596 Pass 30 Yes Yes Yes Yes Yes 30 Yes No Yes x    
MW765432 PRS 266438635 Pass 30 x x x x x x x x x Local (02493)    
MW765433 PRS 266438636 Pass 14 x x x x x x x x x Local (02493)    
  • When testing, it's recommend you limit the number of jobs/PRS licenses as for each successful posting, you can receive up to two (account creation, PRS 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 can be caused by one or multiple job/PRS 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's not required to resubmit an entire feed.
 

Common Newspaper Errors

A list of common newspaper errors can be found here.

 

 

Project Deliverables

 

Account Creation Email

Once a job processes successfully, a standard Monster email is sent to clients when a new account is created. Within this email, the client is provided with their login credentials (username and password). This letter is not configurable by the newspaper partner but can be viewed by the partner if desired. 


Job Feed Processing Notification

This email address represents where the feeds success/failure notification will be sent. The recommended email address is "monsterfeeds@newspapername.com". 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 monsterfeeds@maynardtimes.com. Please email mabiz@monster.com with this information.
 

Newspaper Admin and User Guide

Newspaper Admin is a tool available to the newspaper partner. This provides the ability to view the status of job/PRS feeds and their content, preview/edit/expire jobs and 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 can 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 newspaperteam@monster.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 will need to send an email to newspaperteam@monster.com with their name and email address to get a new account created.

 

Transition to Production

 

Partner Checklist

  • 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 transition to production.
  • Set Implementation date with Monster.
  • Transition to Production.
 

Contacts

Test issues: mabiz@monster.com
Production issues: newspaperteam@monster.com.
 

Appendix A: 2013.05.0 Release

As part of Monster's 2013.05.0 release, the newspaper integration service now supports 1) posting jobs to multiple jobs boards via one job submission and 2) the ability to post jobs to the Monster Veterans job board. Also, there are now two new job posting packages. In order to implement these new job posting capabilities, one must be using the <nis:Jobs> schema. Details can be found here
 

Posting to the Multiple Job Boards

As part of this release, Monster now provides the ability to post jobs to multiple job boards by using the <BoardName> element within the job XML. The supported board groups are shown in the table below.
Job Board(s) Board or group or package in XML Supported Packages
Monster only <BoardName monsterId="1"/>  
Monster & Diversity (*see note) <BoardName boardGroupId="42"/>  
Monster & Veterans <BoardName boardGroupId="1494"/>  
Monster, Diversity & Veterans <BoardName boardGroupId="1495"/> Complete
Monster, Diversity & Veterans <nis:AdditionalProducts>
    <nis:NISPackage monsterId="1"/>
<nis:AdditionalProducts>
Gold
Gold & Single Twitter Card <nis:AdditionalProducts>
    <nis:NISPackage monsterId="2"/>
<nis:AdditionalProducts>
Platinum
*Notes:
For pre-existing integrations, providing <BoardName monsterId="1"/> and setting <nis:Diversity desired="true"/> is still supported and equivalent to <BoardName boardGroupId="42"/>. <nis:Diversity desired="true"/> only works when <BoardName monsterId="1"/>
 

Posting to the Veterans Job Board

Posting a job to the Veterans job board must be done in conjunction with a job posting to the Monster board. The job duration and CAN duration will be the same for the Monster and Veterans job postings. Shown below is how the impacted parts of the XML should be set to post to both job boards.

BoardName
<BoardName boardGroupId="1494"/>
Job Duration The job duration can be provided in one of two ways. Either 1) as part of the <JobPostingDates > element of the XML. This allows one to set the <JobActiveDate> and <JobExpireDate> of the job posting or option 2) set the desiredDuration to the desired length of the job posting. This can be set to 7, 14 or 30 days. One benefit of using this method is that only the job duration needs to be provided and the active and expire dates will be automatically determined based on when the job is successfully posted to Monster. More details on this option can be found here.

Option 1
	<JobPostingDates>
     <JobActiveDate>2013-04-15T00:00:00</JobActiveDate>
     <JobExpireDate>2013-05-15T00:00:00</JobExpireDate>
 </JobPostingDates>
 
Option 2
<JobPosting desiredDuration="14"/>
 

Gold Job Posting Package

The Gold job posting package includes a job posting to the Monster, Diversity and Veterans job boards. Each posting has a 30 day duration, has a CAN duration of 30 days, has autorefresh and bolding. Instead of populating the individual XML elements mentioned above, a package (that sets the appropriate elements) has been created and the XML job submission should include the following.
  <nis:AdditionalProducts>
     <nis:NISPackage monsterId="1"/>
  </nis:AdditionalProducts>
Even though the NIS package will populate the board name, the process will produce a warning about a missing board name. Please disregard this warning. To make the warning disappear, populate the board name with 1495.

Complete Job Posting Package

The Complete job posting package includes a job posting to the Monster, Diversity and Veterans job boards. Each posting will have the same duration and the option to add any of the following: CAN (7, 14 or 30 days), autorefresh and bolding. The following shows how the impacted parts of the XML should be set.

BoardName
<BoardName boardGroupId="1495"/>
Job Duration This can be provided in one of two ways. Either 1) as part of the <JobPostingDates> element of the XML. This allows one to set the <JobActiveDate> and <JobExpireDate> of the jobs posting or 2) set the desiredDuration to the desired length of the job posting. This can be set to 7, 14 or 30 days. One benefit of using this method is that only the job duration needs to be provided and the active and expired dates will automatically be determined based on when the job is successfully posted to Monster. More details on this option can be found here.

Option 1
	<JobPostingDates>
     <JobActiveDate>2013-04-15T00:00:00</JobActiveDate>
     <JobExpireDate>2013-05-15T00:00:00</JobExpireDate>
 </JobPostingDates>
 
Option 2
<JobPosting desiredDuration="30"/>

AdditionalProducts If purchased, autorefresh, CAN and bolding can be provided in this section of the XML. See example below
<nis:AdditionalProducts"/>
     <nis:Autorefresh desired="true"/>
         <Frequency"/>14</Frequency"/>
     <nis:Autorefresh/>
     <nis:CareerAdNetwork desired="true"/>
         <Duration"/>7</Duration"/>
     <nis:CareerAdNetwork/>
     <nis:Bolding desired="true"/>
 </nis:AdditionalProducts/>
Note that the <nis:Diversity desired> tag does not need to be provided as posting to the Diversity job board is part of the <BoardName> above. However, if provided, it will be ignored.
 

Feed Processing Results Improvements

As part of this release, the contents of the CSV file attached to the success/failure email has been improved. Now the results include confirmation whether a job was also posted to the Diversity and Veteran job boards and what additional products (bold, CAN, autorefresh) were part of the posting. Below is a sample CSV file, displayed in table format, showing the changes.
JobRefCode Monster Job Id Result Duration Diversity Veterans Bolding Auto Refresh CAN Error message
11111 117823434 Pass 30 Yes Yes Yes Yes Yes  
22222 117823437 Pass 14 Yes Yes No No Yes  
33333 117823440 Pass 30 No Yes No No Yes  
44444 117823442 Pass 30 Yes No Yes No Yes  
 

Appendix B: 2013.09.0 Release

As part of Monster's 2013.09.0 release, the newspaper integration service now supports the ability to fulfill 14 or 30 day local (postal code with a 100 mile radius) or national Power Resume Search (PRS) 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 can be submitted in a feed by themselves or together with job postings. License requests do not have to be linked to a job posting.
 

Creating the PRS XML Feed

The rules for creating a PRS XML submission are similar to submitting a job posting. The specifics are discussed below. Samples can be found here.

NOTE: Populating the PRS 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.

Key points in this area:
XML Field Required? Notes
<nis:License licenseRefCode="xx"> YES Recruiter specific term used to uniquely identify PRS 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 PRS.
<nis:SearchPostalCode> See notes
  1. If not provided, a "national" license with be granted.
  2. If provided, a "local" license (postal code with a 100 mile radius) will be granted. Note that the postal code must be valid.
<nis:Duration> YES Must be set to 14 or 30 as these are the available options.
<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
 

Testing the PRS XML Feed

Please refer to the section of this document titled "Testing the XML Feed" in order to confirm your PRS XML is working as expected.
 

Feed Processing Results

As part of this release, the success/failure email and the contents of the CSV file now include the results of PRS feed processing. Here is a sample file showing a local and national PRS submission and a success/failure email with feed results.

Summary:

Filename: monster_prs_20130715-02.xml
Total number of jobs: 0
Number of new job postings: 0
Number of jobs failed: 0
Number of duplicate/updated jobs: 0
Number of jobs deleted: 0

Total number of Power Resume Search licenses: 2
Number of new Power Resume Search licenses: 2
Number of Power Resume Search licenses failed: 0
Number of duplicate Power Resume Search licenses: 0

Detailed Log:
===========================================================================================================
Click here for information on how to resolve errors
Jobs - failed (0)
Jobs - new postings (0)
Duplicate/Updated jobs (0)
Jobs - deleted (0)
Power Resume Search - failed (0)
Power Resume Search - new (2)
PRS_20130715_02
PRS_20130715_03
Duplicate Power Resume Search (0)

Warnings:
>>>>>>>>>>>>>>>>>>>>>>>>> End of Message >>>>>>>>>>>>>>>>>>>>>>>>>
 

Emails - Account Creation & Confirmation

If a new account is created as part of a PRS submission, the standard account creation email will be sent to the user. For successful PRS license submissions, a confirmation email will be sent letting the user know they purchased a PRS license and details about the license.
 

Newspaper Admin

PRS submissions can be viewed in newspaper admin by selecting "PRS Feeds" in the main screen. Once there, one can see the different PRS feed submissions, date of submission and processing results. Note that the look and feel of the results is similar to that of jobs feeds and specific job information.

When a feed contains both jobs and PRS license submissions, the feed file name will show up under both "Job Feeds" and "PRS Feed". However, the content in these areas will only include jobs or PRS licenses and not both.


 

Appendix C: 2014.11.15 Release

As part of Monster's 2014.11.15 release, the newspaper integration service now supports 1) Single Twitter Cards and 2) the newly created Platinum package (Gold Package + Single Twitter Card). Also, a new XML element (<nis:NISPackage>) has been added in order to simplify Gold and Platinum packages.

Single Twitter Cards

Single Twitter Cards can be included in a new job posting or added to an existing job posting. In order to add this onto a job posting, <nis:TwitterSingleCard desired="true"/> must be added under the <nis:AdditionalProducts> section of the XML. This entry would be in addition to any other additional products associated with the job submission. See example below.

<nis:AdditionalProducts>
    <nis:Autorefresh desired="true">
        <Frequency>14</Frequency>
    </nis:Autorefresh>
    <nis:CareerAdNetwork desired="true">
        <Duration>30</Duration>
    </nis:CareerAdNetwork>
    <nis:Bolding desired="true"/>
    <nis:TwitterSingleCard desired="true"/>
</nis:AdditionalProducts>

NIS XML Package Element


In order to simplify jobs submissions that include the Gold and Platinum packages, an element named <nis:NISPackage> has been created. When used, this must be added under the <nis:AdditionalProducts> section of the XML. There are two options; 1= Gold Package and 2 = Platinum package. By setting the NISPackage in the XML, there’s no need to provide board name, job duration, CAN, autorefresh and bold. The job processing will populate these fields. See examples below.

Gold Package

<nis:AdditionalProducts>
    <nis:NISPackage monsterId="1"/>
</nis:AdditionalProducts>

Platinum Package

<nis:AdditionalProducts>
    <nis:NISPackage monsterId="2"/>
</nis:AdditionalProducts>


Even though the NIS package will populate the board name, the process will produce a warning about a missing board name. Please disregard this warning. To make the warning disappear, populate the board name with 1495.

Feed Processing Results


The CSV file attached to the feed processing results will now include whether a Single Twitter Card was included in the job posting.
 

Newspaper FAQs

What is the unique identifier for a job?
The unique identifier for a job is the combination of jobRefCode and UserName.
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.
Can 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.
Can I resend the same job in successive feed files?
Yes, you can resend the same job, but the jobAction=”addOrUpdate” signifies that t he data you send should override 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.