rp hcmrs verity

Verity in Recruiting Solutions 8.9 By: Darren Guilbert April 2005

PeopleSoft Red Paper Series

Verity in Recruiting Solutions 8.9

Copyright © 2005, Oracle. All rights reserved. The information contained in this document is proprietary and confidential to Oracle. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Oracle. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

.

3

Table of Contents

TABLE OF CONTENTS............................................................................................................................................................. 3

INTRODUCTION........................................................................................................................................................................ 5

STRUCTURE OF THIS RED PAPER ...................................................................................................................................... 5

RELATED MATERIALS ........................................................................................................................................................... 5

UNDERSTANDING VERITY IN RECRUITING SOLUTIONS HISTORY........................................................................ 7

FUNCTIONAL OVERVIEW ..................................................................................................................................................... 8 The Search Collections ................................................................................................................................................................ 8 Find Applicants Search ............................................................................................................................................................... 9

General Search Hints ................................................................................................................................................................. 9 Basic Vs Advanced Searches ................................................................................................................................................... 10 Basic Searches using Resume Text and Date Fields ................................................................................................................ 10 Advanced Searches .................................................................................................................................................................. 11

Recruiter Job Postings Search .................................................................................................................................................. 14 Basic Vs Advanced Searches ................................................................................................................................................... 14 Basic Searches using Text and Date Fields.............................................................................................................................. 14 Advanced Searches .................................................................................................................................................................. 15

Careers Job Search .................................................................................................................................................................... 17 Basic Vs Advanced Searches ................................................................................................................................................... 17 Basic Searches using Text and Date Fields.............................................................................................................................. 17 Advanced Searches .................................................................................................................................................................. 18 Advanced Searches using the Text Fields................................................................................................................................ 20 Using Zones in the Applicant Index......................................................................................................................................... 21 The Score ................................................................................................................................................................................. 22

Auto-Match................................................................................................................................................................................. 22 Job Agent .................................................................................................................................................................................... 23 Languages ................................................................................................................................................................................... 24

TECHNICAL OVERVIEW...................................................................................................................................................... 26 Installing Verity.......................................................................................................................................................................... 26 Applicant Index Builder ............................................................................................................................................................ 26

Description ............................................................................................................................................................................... 26 Pseudo-Code ............................................................................................................................................................................ 26 Result ....................................................................................................................................................................................... 27 Collection Builder .................................................................................................................................................................... 31

Auto-Match Application Engine............................................................................................................................................... 31 Description ............................................................................................................................................................................... 31

Verity in Recruiting Solutions 8.9 6/20/2005

Pseudo-Code ............................................................................................................................................................................ 32 Applicant Search Implementation............................................................................................................................................ 32

Method Signatures ................................................................................................................................................................... 32 Description ............................................................................................................................................................................... 32 Output ...................................................................................................................................................................................... 33 Input ......................................................................................................................................................................................... 33

Job Index Builder....................................................................................................................................................................... 33 Description ............................................................................................................................................................................... 33 Pseudo-Code ............................................................................................................................................................................ 33 Result ....................................................................................................................................................................................... 34 Collection Builder .................................................................................................................................................................... 36

Job Agent Application Engine .................................................................................................................................................. 37 Description ............................................................................................................................................................................... 37 Pseudo-Code ............................................................................................................................................................................ 37

Job Search Implementation ...................................................................................................................................................... 38 Method Signatures ................................................................................................................................................................... 38 Description ............................................................................................................................................................................... 38 Output ...................................................................................................................................................................................... 38 Input ......................................................................................................................................................................................... 39

The Style Files............................................................................................................................................................................. 39 Customization............................................................................................................................................................................. 39

APPENDIX................................................................................................................................................................................. 43 Glossary of Terms ...................................................................................................................................................................... 43 Frequently Asked Questions ..................................................................................................................................................... 43 Language Support...................................................................................................................................................................... 45 Installation Steps ........................................................................................................................................................................ 47 Operator Reference.................................................................................................................................................................... 48

ACCRUE Operator .................................................................................................................................................................. 48 AND Operator.......................................................................................................................................................................... 49 = (EQUALS) Operator............................................................................................................................................................. 49 > (GREATER THAN) Operator .............................................................................................................................................. 49 >= (GREATER THAN OR EQUAL TO) Operator ................................................................................................................ 50 < (LESS THAN) Operator ....................................................................................................................................................... 50 <= (LESS THAN OR EQUAL TO) Operator.......................................................................................................................... 50 IN Operator .............................................................................................................................................................................. 50 NEAR Operator........................................................................................................................................................................ 51 NEAR/N Operator.................................................................................................................................................................... 51 OR Operator............................................................................................................................................................................. 52 PARAGRAPH Operator .......................................................................................................................................................... 53 PHRASE Operator ................................................................................................................................................................... 53 SENTENCE Operator .............................................................................................................................................................. 54 SOUNDEX Operator ............................................................................................................................................................... 54 THESAURUS Operator ........................................................................................................................................................... 55 WILDCARD Operator ............................................................................................................................................................. 55 WORD Operator ...................................................................................................................................................................... 56

© Copyright Oracle Corporation 2005. All rights reserved. 5


Introduction

This Red Paper is a practical guide for technical users, installers, system administrators, and programmers who implement, maintain, or develop applications for your PeopleSoft system. In this Red Paper, we discuss guidelines on how to diagnose a PeopleSoft Online Transaction environment, including PeopleSoft Internet Architecture and Portal configuration. Configuration of Batch processes is not covered in this document.

Much of the information contained in this document originated within the PeopleSoft Global Support Center and is therefore based on "real-life" problems encountered in the field. Although every conceivable problem that one could encounter with Tuxedo, the PeopleSoft Application Server, or your web server is not addressed in this document, the issues that appear in this document are the problems that prove to be the most common or troublesome.

Structure of this Red Paper

This document provides a brief history of Verity introduction into Recruiting Solutions and discusses how Recruiting Solutions uses the Verity technology:

� Functionally

� Technically

This document is intended for anyone who wants a more thorough understanding of how the Recruiting Solutions product leverages the Verity technology and is organized according to the role a person might fill within a team using the Recruiting Solutions product.

The functional analyst will learn about Find Applicant Search, Auto-Match Saved Searches, Applicant and Recruiter Job searches and how to create queries that meet the organization’s needs. The technical analyst will learn about the different components used and areas where some customers have chosen to customize.

This document focuses on the 8.9 Recruiting Solutions’ releases and assumes that the reader has some familiarity with the Recruiting Solutions product, particularly the Find Applicants, Job Search, Auto-Match and Job Agent Saved Search features. Screen shots are from the 8.9 release of the Recruiting Solutions product. It also assumes that responsibilities of the technical analyst includes setting up the search collections and might be responsible for customizations to the index processes and query function.

Keep in mind that PeopleSoft updates this document as needed so that it reflects the most current feedback we receive from the field. Therefore, the structure, headings, content, and length of this document is likely to vary with each posted version. To see if the document has been updated since you last downloaded it, compare the date of your version to the date of the version posted on Customer Connection.

Related Materials

This paper is not a general introduction to environment tuning and we assume that our readers are experienced IT professionals, with a good understanding of PeopleSoft’s Internet Architecture. To take full advantage of the information covered in this document, we recommend that you have a basic understanding of system administration, basic Internet architecture, relational database concepts/SQL, and how to use PeopleSoft applications.

This document is not intended to replace the documentation delivered with the PeopleTools 8 or 8.14 PeopleBooks. We recommend that before you read this document, you read the PIA related information in the PeopleTools PeopleBooks to ensure that you have a well-rounded understanding of our PIA technology. Note: Much of the information in this document eventually gets incorporated into subsequent versions of the PeopleBooks.



Many of the fundamental concepts related to PIA are discussed in the following PeopleSoft PeopleBooks:

• PeopleSoft Internet Architecture Administration (PeopleTools|Administration Tools|PeopleSoft Internet Architecture Administration)

• Application Designer (Development Tools|Application Designer)

• Application Messaging (Integration Tools|Application Messaging)

• PeopleCode (Development Tools|PeopleCode Reference)

• PeopleSoft Installation and Administration

• PeopleSoft Hardware and Software Requirements

Additionally, we recommend that you read the BEA documentation (in HTML format) delivered with the BEA CD-ROM, to gain a thorough understanding of the BEA products that PeopleSoft uses, Tuxedo, Jolt, and WebLogic Server 5.1. Refer to your PeopleSoft Installation and Administration book for directions on accessing the delivered BEA documentation.



Understanding Verity in Recruiting Solutions History

PeopleTools introduced the Verity functionality into its product line in the 8.x product family to satisfy the needs of applications wanting search functionality above and beyond searches afforded by SQL. It was no longer enough to have the ability to query the database using SQL Like statements.

Starting in HRMS 8.01, the Recruiting Solutions product offered a feature called Applicant Search. This feature enables users to query the pool of applicant resumes with more options.

Find ApplicantSearch Introduced

Tools IntroducesVerity API in

PeopleTools 8.1X

Auto-MatchIntroduced

Applicant-Specified Resume

Language

PeopleTools 8.44with Verity

HRMS8.01

HRMS8.31

HRMS8.81

Usabilityenhancements toall search facilities

HRMS8.9

Job Posting IndexIntroduced

Timeline for HRMS and PeopleTools releases

This table outlines the coordination of HRMS, PeopleTools, and Verity releases.

Application Release PeopleTools Release Verity Release

8.01 8.20 2.71

8.31 8.20 2.71

8.81 8.44 5

8.9 8.46 5.01



Functional Overview

This section discusses:

The Search Collections

Find Applicants Search

Job Searches

Auto-Match Process

Job Agent Process

Languages

THE SEARCH COLLECTIONS

One verity collection is built to house applicant application data and another for Job Posting data.

After an applicant is created through either the “Apply On-Line Careers” or “Add Applicant” transactions the applicant’s information is not immediately searchable through “Find Applicants”. The applicant’s information becomes accessible when the applicant becomes part of the Applicant search collection, which is the indexed pool of resumes. The search collection is created after the “Build Applicant Index” transaction completes.

Similarly for Job Posting data the “Build Job Index” process must complete before a Job Posting can be located via the “Careers Job Search” or the “Search Postings” functions.

Recruiting – Administration – Build Applicant Index.

Recruiting – Administration – Build Job Index.



Build Applicant Index run control page

You can run the Applicant Index process once or at reoccurring intervals. To run the program at reoccurring intervals, attach a recurrence definition to the Process Definition HRS_SRCH_IDX. Once this process successfully runs, the applicant information is available through the Find Applicants process.

The Segment Size is a newly introduced (optional) parameter in release 8.9 to accommodate situations where a high volume of applicant data needs to be indexed. This value represents the size (in days) and is used to form the basis of a date range segment. Each Verity collection built will hold all application data falling within the given date range segment. In effect, the entire range of application data (from first to last application) will be split into date segments of the given size and each segment will be indexed in its own Verity collection. This results in 1 or more Verity collections being built according to the segment size chosen (smaller segment size will mean more collections for a given set of data, larger segment size gives fewer collections).

This is extremely useful in high data volume situations where a multi-processor machine is available and results in a reduction in build time for the Applicant Index on such hardware. Choice of an effective segment size depends on several factors including expected number and distribution of incoming applications. When making this decision some analysis of the ‘expected’ mean distribution of incoming applications is required. For example:

Company XYZ “expects” based on industry knowledge and past experience that they will receive approx 100 resumes per day over a 6 month period. Company XYZ is equiped with hardware to enable the use of segmenting during the Applicant Index build and based on this distribution of data chooses a segment size of 20 days. This choice results in approx (100 x 20) applications being indexed per index collection and (6 x 30)/20 collections being created for this periods data.

Build Job Index run control page

Similarly to the Applicant Index you can run the Job Index process once or at reoccurring intervals. Once this process successfully runs, the Job Posting information is available through the Recruiter Search Postings, Applicant and Self Service Careers Job search processes.

FIND APPLICANTS SEARCH

The Find Applicants function was designed to provide an interface into Verity and supplements the structured-search functionality delivered by the Job Opening Screening process. The key to a successful applicant search is understanding the keywords provided by Verity.

See Also “Appendix”, Operator Reference

General Search Hints

Here are some general search hints to assist you in writing the best queries.

1. Enclose any Verity operators, like AND or OR or ACCRUE in open and closed brackets.



Database <AND> Design

Unless you enclose the words in your query in quotation marks, the Verity search engine will look for derivatives of the word as well as the word itself. The above query will return documents that contain the word designer as well as the word design.

2. The score is important only in relation to other applicants included in the result set. This is especially true when searching against a job opening. When searching against the job opening, the query engine tries to match the text in the Requirements, Responsibilities and other job opening related details against Resumes that have been indexed. This is not an exact science and correct interpretation of the results is important.

3. The Resume Text field triggers a search of the entire resume attachment or resume text. For instance, if the term Oracle is entered in the Resume Text field, applicants whose resumes contain the word Oracle anywhere in their resume will be included in the result set. You cannot distinguish between the applicant having worked at Oracle or having experience with the Oracle database platform.

4. If you enter text into the Accomplishments, Competencies, Education, and Work Experience fields, you are instructing Verity to only look for words in those zones (see the Glossary for definition). Using zones, you can create a more intelligent search. Continuing with the Oracle example, you can now instruct Verity to only retrieve documents where an applicant worked at Oracle by entering the word “Oracle” in the “Work Experience” field.

Basic Vs Advanced Searches

The Find Applicants Verity search process is split into both Basic and Advanced variants. The intent here is to distinguish simple searches (usually simple text or date range driven) from more complex multiple criteria based searches. This offers both novice and advanced users ease of use.

Basic Searches using Resume Text and Date Fields

The most basic type of search is one in which a word or words are entered in the Resume Text field and an optional date range is provided. When the Resume Text field is used, the Verity query searches over the entire text of the applicant’s resume, even when a resume has not been submitted. If the applicant has not submitted a resume with his or her application, then a search using this field will return no results for that applicant.

Search Query

Queries against the Applicant Collection are triggered from the “Find Applicants” page. From this page there are several options available to the User.

• Perform a “database driven” search by specifying criteria in the top Applicant Search groupbox : This search criteria is used to search the Recruiting database tables only (not the verity collection) and will not be covered further in this paper – please see PeopleBooks for further information

• Perform a Basic “Verity driven” search by specifying criteria in the lower Resume and Application Search groupbox : This search criteria is used to search the Verity Applicant Index

• Initiate an external search for applicants using the AIRS search station

• Select a “saved search” from the Saved Resume And Applicant Search dropdown listbox : this is a search criteria that had been previously created and saved

The Basic “Find Applicant” search allows you to specify both Resume keywords and/or an Application Received date range. By default any criteria specified are linked using AND boolean logic.



Recruiting – “Find Applicants” – Basic Search

Advanced Searches

The most advanced type of search is one in which a combination of words, date ranges and other applicant application related criteria can be specified. When more than one form of criteria is specified the user can select to link the criteria using either AND or OR boolean logic by specifying an option from the Match Applicants Using dropdown listbox.

Search Query

Queries against the Applicant Collection are triggered from the “Find Applicants” Advanced Search page. This page is reached by clicking the Advanced Search hyperlink on the Basic Search groupbox. From this page there are several options available to the User.



Perform an Advanced “Verity driven” search by specifying any number and combination of criteria : This search criteria is used to search the Verity Applicant Index

Initiate an external search for applicants using the AIRS search station

Select a “saved search” from the Saved Resume And Applicant Search dropdown listbox : this is a search criteria that had been previously created and saved

Recruiting – “Find Applicants” – Advanced Search



Search Results

Using either the Basic or Advanced searches, the Verity search engine will weight the results returned based on the frequency of words in the resume or the presence of other specified criteria.

The more a particular word occurs in the document, the higher the score. The below results grid was generated by entering the keyword “ORACLE” in the “Resume Text” field of the Basic Search page and clicking the “Find Applicants” button.

The table below illustrates how many occurrences of the word “ORACLE” appeared in the corresponding Applicant’s resume. In general, the “Score” column is reflective of key word frequency, though this changes drastically when building complex queries containing other criteria.



Applicant ID “ORACLE” Occurrences

100024 1

112 1

Search Results

Variations on the keyword search include using the “<AND>” , “<OR>”, or “<ACCRUE>” operator.

See Also “Appendix,” Verity Operators

RECRUITER JOB POSTINGS SEARCH

The Recruiter Search Postings function was designed to provide an interface into the Verity Job Posting Index. This function replaces the previously available database driven job postings search.


The Recruiter Search Postings process is split into both Basic and Advanced variants. The intent here is to distinguish simple searches (usually simple text or date range driven) from more complex multiple criteria based searches. This offers both novice and advanced users ease of use.

Basic Searches using Text and Date Fields

The most basic type of search is one in which a word or words are entered in the Search For field and an optional date range is provided. When the Search For field is used, the Verity query searches over the text of the job opening posting title as well as the posting description of all postings associated with the opening.

Search Query

Queries against the Job Collection are triggered from the “Recruiter Search Postings” page.

From the “Applicant Careers Find Jobs” page there are several options available to the Applicant or Self Service user.

Perform a Basic “Verity driven” search by specifying criteria in the Basic Job Search groupbox : This search criteria is used to search the Verity Job Index

Perform a Advanced “Verity driven” search by specifying criteria in the Advanced Job Search groupbox : This search criteria is used to search the Verity Job Index



Recruiter – “Search Postings” – Basic Search

Advanced Searches

The most advanced type of search is one in which a combination of words, date ranges and other job posting related criteria can be specified. When more than one form of criteria is specified the criteria is linked using AND boolean logic.

Search Query

Queries against the Job Collection are triggered from the “Recruiter Search Postings” Advanced Search page. This page is reached by clicking the Advanced Search hyperlink on the Basic Search groupbox. From this page the following option is available to the User.

Perform an Advanced “Verity driven” search by specifying any number and combination of criteria : This search criteria is used to search the Verity Job Index

Recruiting – “Search Postings” – Advanced Search



Search Results

Using either the Basic or Advanced searches, the Verity search engine will weight the results returned based on the frequency of words in the Job Posting description or the presence of other specified criteria.

The more a particular word occurs in the verity indexed document, the higher the score. The below results grid was generated by entering the keyword “Administrator” in the “Enter Keywords” field of the Advanced Search page and clicking the “Search” button.



CAREERS JOB SEARCH

The Applicant Careers Job Posting search function function was designed to provide an interface into the Verity Job Posting Index for Self Service or External applicant usage. These functions replace the previously available database driven job postings search for Self Service employees and external applicants.


The Applicant Careers Find Job Verity search process is split into both Basic and Advanced variants. The intent here is to distinguish simple searches (usually simple text or date range driven) from more complex multiple criteria based searches. This offers both novice and advanced users ease of use particularly where external applicants are concerned.

Basic Searches using Text and Date Fields

The most basic type of search is one in which a word or words are entered in the Search For field and an optional date range is provided. When the Search For field is used, the Verity query searches over the text of the job opening posting title as well as the posting description of all postings associated with the opening.



Search Query

Queries against the Job Collection are triggered from the “Applicant Careers Find Jobs” page.

From the “Applicant Careers Find Jobs” page there are several options available to the Applicant or Self Service user.

Perform a Basic “Verity driven” search by specifying criteria in the Basic Job Search groupbox : This search criteria is used to search the Verity Job Index


Select a “saved search” from the Use Saved Search dropdown listbox : this is a search criteria that had been previously created and saved

Careers – “Job Search” – Basic Search

Advanced Searches

The most advanced type of search is one in which a combination of words, date ranges and other applicant application related criteria can be specified. When more than one form of criteria is specified the criteria is applied using AND boolean logic.

Search Query

Queries against the Job Collection are triggered from the “Applicant Careers Advanced Job Search” page. This page is reached by clicking the Advanced Search hyperlink on the Careers hompage. From this page there are several options available to the User.

Perform an Advanced “Verity driven” search by specifying criteria in the Advanced Job Search groupbox : This search criteria is used to search the Verity Job Index


Select a “saved search” from the Use Saved Search dropdown listbox : this is a search criteria that had been previously created and saved



Recruiting – “Find Applicants” – Advanced Search

Search Results

Using either the Basic or Advanced searches, the Verity search engine will weight the results returned based on the frequency of words in the job posting description or the presence of other specified criteria.

The below results grid was generated by entering the keyword “Human Resource” in the “Enter Keywords” field of the Advanced Search page and clicking the “Search” button.



Advanced Searches using the Text Fields

Operators can be an effective tool to achieve the desired results required by your organization. For instance, if the intended result of a search is to find people who have exposure of some form to Education in the Welfare area, consider the following Basic search query.

Figure 6

This query will return results where the word Education is in the same sentence as the word Welfare. This would be useful in the case where you want people who have had exposure to Welfare Education rather than those who have had Political Education.



<SENTENCE> is one of the many operators that will allow you to tailor searches to a specific case.

Using Zones in the Applicant Index

Zones refer to areas of information an applicant provides when using Apply for Job, when an administrator enters the applicant information on the Applicant Information page, or if you are using Resume Load Processing. These areas include:

� Competencies

� Accomplishments

� Education

� Work Experience

� Referral Source

� Location

� Job Family and Location Preferences

� Application Details

Note: The Applicant Indexing process does NOT automatically create zones from resume text or resume attachments.

The zones are particularly useful when a word in a resume may have ambiguous meaning. For example, if the intent is to find someone who worked at University of California, Davis, you would not know when entering the search query into the Keywords text field whether that a matching applicant returned by Verity attended University of California, Davis or worked there. Here is how you would make that distinction.



Example of advanced searching

By adding Davis to the work experience field, this query returned an applicant who worked at UC Davis and not attended UC Davis:

Applicant’s Resume

The Score

The algorithm for computing the score is proprietary Verity technology.

When considering the score of the returned results set, keep the following in mind:

1. The actual score does not contain much meaning. The relative score is what is important in the search results.

2. Generally, when using any basic Keyword text search, the score reflects the term frequency in the document returned in the search results.

3. Some of the operators listed in the appendix have a substantial effect on how Verity computes the score of the matching document. Again, using the score as a relative indicator of success is recommended.

AUTO-MATCH Auto-Match allows the Find applicants process to occur in an automated fashion. In release 8.9 the auto-match functionality has been incorporated into the Find Applicants process. Any search criteria saved by a recruiter during the Find Applicants process can be nominated as being an Auto-match search also. In addition, a job opening may be specified for an auto-match search should the recruiter desire to link the auto-match results with a particular opening. Note that in release 8.9, an auto-match search (or the results from an auto-match search) do not necessarily need to be associated with any job opening – this differs from previous releases and offers further flexibility in managing and tracking openings and related applicants.

When an auto-match search is run, the recruiter will receive a workflow email notifying them of any newly added (potential) candidates which match the recruiters original search criteria. Note that a recruiter may have several searches flagged as auto-match at the same time giving maximum flexibility in mining for the most suitable applicants across several different openings.



Recruiter – Find Applicants– Save Auto-Match Search.

JOB AGENT Job Agent searches allow the applicant or Self Service user to nominate a search criteria for automated on-going use. Any search criteria saved by a user during the Job search process can be nominated as being a Job Agent search. In release 8.9 any number of job search criteria can be nominated as a job agent (up to a pre-determined maximum as defined in the the Recruiting Installation table). In addition, a notification email address may be specified during the save of the job search criteria. This email address is used to inform the applicant of any new job openings that are found sebsequently that match their criteria.



Careers – Job Search – Save Search.

LANGUAGES

In 8.31, the resume language was determined by the logged-in language of the user attaching the resume. This may or may not be the actual language of the resume.

In 8.9, the applicant or power user creating the application will always be able to specify the language code associated with a resume. The languages from which the applicant or power use can choose is determined by what languages exist (they do not need to be installed) on the “Manage Installed Languages” transaction.

Navigation: PeopleTools – Utilities – International - Languages

Manage Installed Languages



Note: The languages will appear to the applicant in the Apply On-Line transaction whether they are installed or not.



Technical Overview

This section discusses:

Installing Verity.

Applicant and Job Posting Index Builder.

Auto-Match Application Engine.

Job Agent Application Engine.

Find Applicant Function

Job Search Functions

The Style Files.

Customization.

INSTALLING VERITY

The installation for 8.9 is straightforward. During the installation of PeopleTools, all Verity libraries are copied to the appropriate locations. Installation of PeopleSoft Recruiting Solutions will copy the style files needed to build the applicant collection into the data folder in Tools home. At this point, the index is ready to be run.

APPLICANT INDEX BUILDER

Object Name: HRS_SRCH_IDX

Object Type: Application Engine

Description

This Application Engine program calls a Verity collection-building tool to create the applicant collection. Fairly significant differences exist between 8.31 and 8.9, particularly with respect to three areas: Building the different locale collections and utilizing the incremental search capabilities developed in 8.8 and utilising the segmenting capabilities developed in 8.9. This Application Engine should be run periodically so that the collection closely represents the data in the applicant tables.

Pseudo-Code

Get Collection Information; Create and open empty pointer files for input; Create and open empty data files for input; Create and open empty pointer files for delete if required; Create and open empty data files for delete if required; Loop Through All Applicant Records

Get Data From HRS_APP_PROFILE, HRS_APPLICANT, HRS_APP_NAMES and related records;

Write Data to Data Files; /* These are the input_langcd.dat files*/



Write Pointer data to files; /* These are the input_langcd.bif files */ End-Loop; Close Files; Loop through PSLANGUAGES record

For each language call the Verity collection builder utility Every tenth update of each collection causes an optimization;

End-Loop;

Result

Input Data Files

The following is an excerpt from the Input_Eng.dat file that will be created by the HRS_SRCH_IDX Application Engine. See the discussion on the style files for additional information on how these files are created with the style* files in mind.

<RECORD744>

<PERSON_ID>42</PERSON_ID>

<PROFILE_SEQ>1</PROFILE_SEQ>

<SUBMIT_DT>2001-02-15</SUBMIT_DT>

<SUBMIT_DT_DSP>2001-02-15</SUBMIT_DT_DSP>

<RESUME_TEXT>Seeking a Managerial position that requires strong communication and creative skills for both the challenging management of a marketing and sales force as well as the day-to-day emulation of a technical team.

Preference for a US-based operation, from start-up ventures to established corporations, but also interested by any European proposal in a rapidely growing entity with international business expectations in Europe and in the USA.

Work Experience

1987 - 1999 - International Software Solutions - USA. UK, Germany & France.

Founder, President and CEO.

1987 - Created International Software Solutions France SA, a software company based in Grenoble, France. President and CEO of ISSF. ISSF was awarded multiple times for its two main products: Turbo-Texte (over 250,000 copies sold in Europe in 3 years) and Ordifacture (over 50,000 copies sold in France in 3 years). Primary designer of different software including: Turbo-DB (Dbase 3 compatible), Turbo-Desk (Sidekick clone), Turbo-Calc, Turbo-Graph, PolyPUS/2 (multi-user system for OS/2), PolyWrite/2 (OS/2 word processor) and PolyZip/2 (general purpose compression product). Wrote all the User Manuals of these different products. Created and managed the ISS Help-Desk service. Managed the sales force as well as the PR activities. Awarded by Le Figaro Magazine as the "first spiritual son" of the legendary and successful CEO of Borland Philippe Kahn, to deliver the first French professional software product priced under $100.00.

1988 - Created International Software Solutions Inc., a Delaware corporation with its office in Boulder, Colorado. President of ISS Inc. Managed the relationship with Polyglot Inc., a software company that provided add-on products to ISSF such as the multi-lingual speller and the thesaurus included in Turbo-Texte.

1991 - Co-founder of International Software Solutions France Diffusion, a Grenoble, France based corporation with the main purpose of focusing its sales of the new ISS Products to the French market. Designer of the new ISS



multiple award-winning remote control software for OS/2 named PolyPM/2.

1993 - Co-founder of International Software Solutions LP, a Las Vegas, Nevada based Limited Partnership, with the main purpose of managing the relationships with SCA, the ISS American distributor. Developing OEM relationships with other American software companies. Designer of the DOS and Windows 3.x versions of PolyPM/2.

1994 - Co-founder of International Software Solutions UK Ltd., the British subsidiary of ISS LP based in Basingstoke. Started the UK business.

1995 - Co-founder of International Software Solutions GmbH, the German subsidiary of ISS LP based in Heidelberg. Started the German business. Designer of the Windows 95 version of PolyPM/2.

Received two IBM awards for PolyPM/2 as best ISV OS/2 product two years in a row in 1994 and 1995. Up to now, PolyPM/2, renamed Remote Services Management (RSM) in early 1996, has sold over 2 million copies in more than 30 different countries.

1996 - Co-founder of International Software Solutions USA, the American subsidiary of ISS LP, based in West Palm Beach, Florida. Moved to Florida and manage actively this entity on the US market. Designer of the Windows NT version of PolyPM/2.

1997 - Managed the relationship with IBM and concentrated on the future of ISS in terms of financial and marketing aspects, technical development directions, and strategic alliances.

1998 - ISS represented a small multi-national group of 40 people, with offices in four different locations (USA, France, Germany and England) and a yearly gross revenue of over $4 million generating an average benefit of over $1 million per year for the last four years of his management. That was the time yo move on.

Third quarter 1998 - The ISS main asset PolyPM/2-RSM is sold to a major US software company for an amount of $15 millions.

1999 up to now - Took a long break. Now research for an opportunity to share his skills in a growing international corporation with business expectations in Europe and in the USA.

1984 - 1986 - NIS International - Grenoble, France.

Co-Founder, Vice President.

Co-founder of NIS International, a software company based in Grenoble, France. NIS International was awarded a multiple of times by the French press for its word processor product named "Le Texte" (over 50,000 copies sold in France in 3 years). Vice President of NIS International. Principal designer of other different software including Starbone, a medical oriented database selected by over 100 doctors and surgeons in the French Alps. Wrote the different User Manuals and managed all the sales operations.

Sold his NIS International shares to his partners to create his own new company: International Software Solutions.

1982 - 1983 - SG2 - Lyon, France.

Branch Manager.

Recruited by SG2 as Branch Manager of their second largest National Division

Responsible for the recruitment of sales representatives as well as developers.

Managed complex commercial operations such as Facilities Management.

Successfully achieved the buyout of the largest SG2 regional competitor.

Resigned from SG2 to create its own company since, in 1983, none of the big computer services companies use to trust in a future business related to the emerging technology called Micro Computers.

1979 - 1981 - GSI - Grenoble, France.

National Account Sales Representative.



Recruited by GSI as National Account Sales Representative.

Best overall quota three years in a row.

Managed national sales operations.

Left GSI, "Head Hunted" by SG2.

1975 - 1978 - Olivetti - Paris, France.

Sales Representative.

Recruited by Olivetti as Sales Representative.

Finished first ranked over 75 people attending the mandatory three-month education program at the National Olivetti School.

"Best National Sales Representative" three years in a row.

Departed Olivetti, "Head Hunted" by GSI.

Education

1973 - 1974 - French Navy - France.

French Navy Fighter Pilot.

Recruited with the ranking of 19 over 2500 candidates.

Training as Fighter Pilot in Saint-Raphael, Aulnat and Nimes-Garron.

Resigned from the Navy in 1974 for "humor imcompatibiliy"!.

1964 - 1972 - Lycée Jean De La Fontaine - Chateau-Thierry, France.

Terminale C (Math & Physics).

Left the school in the middle of the year for the huge opportunity to become a Fighter Pilot in the French Navy.

Languages

American-English (fluent),

French (mother tongue).</RESUME_TEXT>

<REFERRAL_SOURCE>0</REFERRAL_SOURCE>

<REFERRAL_SUBSOURCE>0</REFERRAL_SUBSOURCE>

<APP_PER_STS>A</APP_PER_STS>

<STATUS_CODE>010</STATUS_CODE>

<CITY>Oklahoma City</CITY>

<COUNTRY>USA United States</COUNTRY>

<STATE>OK Oklahoma</STATE>

<JOB_FAM_PRF></JOB_FAM_PRF>

<REC_LOCID_PRF></REC_LOCID_PRF>

<RECLOC_DESCR></RECLOC_DESCR>

<APPLIED_FOR></APPLIED_FOR>

<APP_NAME>Samuel Biddles</APP_NAME>



<WORK></WORK>

<EDUCATION></EDUCATION>

<COMPETENCIES></COMPETENCIES>

<ACCOMPLISHMENTS></ACCOMPLISHMENTS>

</RECORD744>

Input Pointer File

Below is an excerpt from the Input_Eng.bif file that corresponds to the Input_Eng.dat file from the above example. This file is created in the HRS_SRCH_IDX Application Engine program.

VdkVgwKey:{42}{1}

DOC_FN:C:/PT846/data/search/HRS_ResumeText/DG890260/input_ENG.dat

DOC_OF:46470

DOC_SZ:7323

PERSON_ID:42

PROFILE_SEQ:1

APP_NAME:Samuel Biddles

SUBMIT_DT_DSP:2001-02-15

RECLOC_DESCR:

APP_PER_STS:A

SUBMIT_DT:2001-02-15

RESUME_FN:C:\\TEMP\\VerityDummy.txt

<<EOD>>

There are a couple of fields to note:

VdkVgwKey – This is the high-level key that is used for the Verity Index.

DOC_OF – This is the position in the input_dat file where this Verity “Document” begins.

DOC_SZ – This tells Verity how many characters to proceed in the input_dat file before considering this “document” to be finished.

RESUME_FN – This field tells verity where to look for the attachment. See the note below for differences between 8.9 and 8.31. If the RESUME_FN field points to VerityDummy.txt, then no resume attachment exists for this applicant.

Note: In 8.9, attachments are handled differently during the HRS_SRCH_IDX process. The process uses the CopyAttachments function to copy all resume attachments to a local directory. In 8.31, the location of the attachment directory relative to the process scheduler is one of the options that is entered on the Applicant Index run control page.



Collection Builder

When building the Applicant index Verity references the input_<language_code>.dat and input_<language_code>.bif files. Since there is no direct line of communication between AE and Verity, it is possible that the Application Engine will have run to success but Verity did not actually successfully finish building the collection. If Verity has successfully run, the following directory structure is created and the parts folder will be populated with the collection files.

AUTO-MATCH APPLICATION ENGINE

Object Name: HRS_AM


Description

To get the most benefit from the Auto-Match feature, the Applicant Index needs to be re-run prior to the Auto-Match run. Both jobs should be run on a recurring basis and on the same frequency depending on the volume of applicants that come into the system. Daily is recommended.

In addition, Applicant Index should be run if large amounts of applicants are purged or merged and purged using Duplicate Applicant Processing. This will prevent retrieving applicants during the search process that are no longer in the database.



Pseudo-Code

HRS_AM

1. MAIN

a. Delete expired search results

b. For each search criteria declared as auto-match:

i. Call SchLOOP

c. Delete expired or non-qualifying results

d. Notify Recruiter of new results

e. Check for expired searches

2. SchLOOP

a. Search applicant index based on search criteria

b. Update last run time of search criteria

APPLICANT SEARCH IMPLEMENTATION

Object Name: HRS_COMMON:SEARCH:BUS:VerityAppSchProvider application class PeopleCode

This class houses the functions used to retrieve search results from the Applicant Collection. The function is called from the Find Applicants page and from Auto-match batch processing.

Method Signatures

method search(&searchStartNbr As number, &searchPageChunk As number, &langCd As string) Returns Rowset;

method searchCollection(&searchStartNbr As number, &searchPageChunk As number, &langCd As string) Returns ApiObject;

Description

The search method uses as inputs the fields that have been placed as either zones or fields into the Applicant Search Collection. The function then builds the query based on the values contained within the properties of the VerityAppSchProvider object and executes the query, returning a Rowset collection.

The searchCollection method performs an identical function but returns a PeopleTools Verity Collection object.

Note: For a full discussion of the PeopleTools Search Class and all available methods and properties, see your PeopleTools documentation.



The collection that is built in the HRS_SRCH_IDX Application Engine by calling Verity consists of both fields and zones. A zone is a region of a document, like the Work Experience or Education experience. A field differs from zones in that field operators can be used (like > or < or = ). Examples of fields in the Applicant Index are the From Date and To Date.

Output

Either:

Rowset – An PeopleTools Rowset that contains a collection of all the search results.

ApiObject – An ApiObject that contains a collection of all the search results. To navigate through the Search Results Collection, see PeopleBooks documentation on the Search class.

Input

&SearchStartNbr – The document number at which to start in the Verity Collection

&SearchPageChunk – The maximum number of results to bring back. &Lang_Cd – The collection over which to search. VerityAppSchProvider object properties – The criteria which Is used to construct the verity

search string.

JOB INDEX BUILDER

Object Name: HRS_JSCH_IDX


Description

This Application Engine program calls a Verity collection-building tool to create the job posting collection. This process is new as of release 8.9. This Application Engine should be run periodically so that the collection closely represents the data in the job opening tables.

Pseudo-Code

Get Collection Information; Create and open empty pointer files for input; Create and open empty data files for input; Create and open empty pointer files for delete if required; Create and open empty data files for delete if required; Loop Through All Job Opening Records

Get Data From HRS_JOB_OPENING, HRS_JO_POSTING, HRS_JO_PST_DST and related records;

Write Data to Data Files; /* These are the input_langcd.dat files*/ Write Pointer data to files; /* These are the input_langcd.bif files */

End-Loop; Close Files; Loop through PSLANGUAGES record



For each language call the Verity collection builder utility Every tenth update of each collection causes an optimization;

End-Loop;

Result

Input Data Files

The following is an excerpt from the Input_Eng.dat file that will be created by the HRS_JSCH_IDX Application Engine. See the discussion on the style files for additional information on how these files are created with the style files in mind.



<RECORD1>

<JOB_OPENING_ID>100000</JOB_OPENING_ID>

<JOB_POSTING_ID>1</JOB_POSTING_ID>

<JOB_BUSUNIT>NSWBU</JOB_BUSUNIT>

<OPENING_STATUS>010</OPENING_STATUS>

<POST_OPEN_DT_DSP>2001-02-23</POST_OPEN_DT_DSP>

<POST_OPEN_DT>2001-02-23</POST_OPEN_DT>

<POST_CLOSE_DT></POST_CLOSE_DT>

<FULL_PART>F</FULL_PART>

<REG_TEMP>R</REG_TEMP>

<MIN_SALARY>34000</MIN_SALARY>

<MAX_SALARY>39000</MAX_SALARY>

<SALARY_CURR>USD</SALARY_CURR>

<SALARY_FREQ>A</SALARY_FREQ>

<POST_TYPE>E</POST_TYPE>

<POSTING_DESC>Would you like to join a professional team? Be responsible for all aspects of Guest Services?

Are you outgoing, friendly and wonderful with people? Must be willing to work a variety of day/night and weekend shifts.

Able to be on your feet for long periods of time.

Able to lift at least 50 pounds.

Excellent people skills.

Must have impeccable grooming standards.

Meet/exceed customer expectations.

Computer experience strongly desired.

An energetic personality.</POSTING_DESC>

<POSTING_TITLE>Guest Services Manager</POSTING_TITLE>

<JOB_FAMILY>N40000</JOB_FAMILY>

<COUNTRY>USA </COUNTRY>

<CITY> </CITY>

<STATE>NY </STATE>

<RCMNT_LOCATION>16</RCMNT_LOCATION>

<RCMNT_LOC_DESCR>New York</RCMNT_LOC_DESCR>

<RECR_NAME>Elizabeth Ferstgrad</RECR_NAME>

<HIRER_NAME>Stephanie Jorgensen</HIRER_NAME>

<DEPT_NAME>Customer Services</DEPT_NAME>

<ROWSECCLASS>HCDPALL HCDPALLPOI HCDPFED HCPPALL HCDPALL HCDPFED HCDPRSBU</ROWSECCLASS>

</RECORD1>



Input Pointer File

Below is an excerpt from the Input_Eng.bif file that corresponds to the Input_Eng.dat file from the above example. This file is created in the HRS_JSCH_IDX Application Engine program.

VdkVgwKey:{100000}{E}

DOC_FN:C:/PT846/data/search/HRS_JobPosting/DG890262//input_ENG.dat

DOC_OF:0

DOC_SZ:1554

JOB_OPENING_ID:100000

JOB_POSTING_ID:1

POST_TYPE:E

POSTING_TITLE:Guest Services Manager

JOB_FAMILY:N40000

RCMNT_LOC_DESCR:New York

HIRER_NAME:Stephanie Jorgensen

DEPT_NAME:Customer Services

HOT_JOB:N

MIN_SALARY:34000

MAX_SALARY:39000

POST_OPEN_DT_DSP:2001-02-23

POST_OPEN_DT:2001-02-23

<<EOD>>

There are a couple of fields to note:

VdkVgwKey – This is the high-level key that is used for the Verity Index.

DOC_OF – This is the position in the input_dat file where this Verity “Document” begins.

DOC_SZ – This tells Verity how many characters to proceed in the input_dat file before considering this “document” to be finished.

Collection Builder

When building the Job Posting index Verity references the input_<language_code>.dat and input_<language_code>.bif files. Since there is no direct line of communication between AE and Verity, it is possible that the Application Engine will have run to success but Verity did not actually successfully finish building the collection. If Verity has successfully run, the following directory structure is created and the parts folder will be populated with the collection files.



JOB AGENT APPLICATION ENGINE

Object Name: HRS_JOB_AGNT


Description

Release 8.9 introduces the flexibility for self service users and applicants to create any number of Job Agents (up to a limit defined in the Recruiting Installation table). The HRS_JOB_AGNT process is a process that should be automated as a scheduled task. Its purpose is to match job critieria against the Job Posting Verity index and record matching jobs. The Self Service user or applicant is then notified by these jobs via email (if they have nominated for this to occur).

Pseudo-Code

HRS_JOB_AGNT

1. MAIN

c. Delete expired Job Agentsearch criteria

d. Delete expired job agent results

e. For each search criteria declared as auto-match:

i. Call SrchIdx

f. Delete previously found jobs from notification temp table



g. Save new results

h. Notify users of new results

2. SrchIdx

i. Search job posting index based on search criteria

j. Update last run time of search criteria

JOB SEARCH IMPLEMENTATION

Object Name: HRS_COMMON:SEARCH:BUS:VerityJobSchProvider application class PeopleCode

This class houses the functions used to retrieve search results from the Job Posting Collection. The function is called from the Recruiter Job Postings page, the Careers Job Search pages and the Job Agent batch processing.

Method Signatures

method search(&searchStartNbr As number, &searchPageChunk As number, &langCd As string) Returns Rowset;

method searchCollection(&searchStartNbr As number, &searchPageChunk As number, &langCd As string) Returns ApiObject;

Description

The search method uses as inputs the fields that have been placed as either zones or fields into the Job Posting Search Collection. The function then builds the query based on the values contained within the properties of the VerityJobSchProvider object and executes the query, returning a Rowset collection.

The searchCollection method performs an identical function but returns a PeopleTools Verity Collection object.

Note: For a full discussion of the PeopleTools Search Class and all available methods and properties, see your PeopleTools documentation.

Output

Either:

Rowset – An PeopleTools Rowset that contains a collection of all the search results.

ApiObject – An ApiObject that contains a collection of all the search results. To navigate through the Search Results Collection, see PeopleBooks documentation on the Search class.



Input

&SearchStartNbr – The document number at which to start in the Verity Collection

&SearchPageChunk – The maximum number of results to bring back. &Lang_Cd – The collection over which to search. VerityJobSchProvider object properties – The criteria which Is used to construct the verity

search string.

THE STYLE FILES

Verity creates indexes based on the rules established in the style files. Recruiting Solutions development modified two of the files to deliver the framework for the Application Index.

Style File Name Description

Style.ufl This file was modified and contains some of the recruitment-specific fields. Fields included in the documents table

Style.dft This file was modified so that the zone resume can be built. Filters used to format source documents for indexing and display..

Style.ddd Not customized by Recruitment Solutions. Fields included in the documents table. Do not edit this file.

Style.did Not customized by Recruitment Solutions

Style.ngm Not customized by Recruitment Solutions

Style.pdd Not customized by Recruitment Solutions

Style.prm Not customized by Recruitment Solutions. Additional data about the collections.

Style.sfl Not customized by Recruitment Solutions. Fields included in the documents table

Style.sid Not customized by Recruitment Solutions

Style.uni Not customized by Recruitment Solutions. Filters used to format source documents for indexing and display

Style.wld Not customized by Recruitment Solutions

Vgw* Pertains to 8.44 Tools <<Get more information here>>

CUSTOMIZATION

Let’s assume that you want to expose an additional field to Verity in the Applicant Index. Remember that fields, defined in the style.ufl file, differ from zones in that field operators can be used on them. In our hypothetical example, let’s assume that you want to add highest education level to the Find Applicants functionality. In order, you would perform the following steps:

a) Modify the Applicant Index peoplecode that creates the style.ufl file. This is only used if you are going to use fields. If you just want to add an additional zone, go to step 2.



PeopleCode: HRS_COMMON: SEARCH:BUS:ApplicantIndex

/**

* UpdateStyleFiles

*

* As of 8.44 tools, style files are required to be written by the application.

*/

method updateStyleFiles

…..

&styleFile.WriteLine(" dispatch: RESUME");

&styleFile.WriteLine(" varwidth: RESUME_FN ido");

&styleFile.WriteLine(" fixwidth: SUBMIT_DT 4 date");

&styleFile.WriteLine(" varwidth: HIGHEST_EDUC number");

&styleFile.WriteLine(")");

&styleFile.Close();

b) Modfy the HRS_APPI_ALL_VW and the HRS_APPI_UPD_VW to include the HIGHEST_EDUC_LVL field from HRS_APP_PROF_I View.

c) Modify the HRS_COMMON: SEARCH:BUS:AppIndexEntry PeopleCode to include an object attribute to store the new field and corresponding get/set methods

…………

/* The Highest Education Level in this profile */

instance string &highestEducLvl;

………..

method getEducLvl

/+ Returns String +/

Return &highestEducLvl;

end-method;

method setEducLvl

/+ &newValue as String +/

&highestEducLvl = &newValue;

end-method;



Also, modify the writeZoneRecord() method to incorporate the new field:

&arrLangfile [&fileIndex][1].WriteLine(" <ACCOMPLISHMENTS>" | &accomp | "</ACCOMPLISHMENTS>");

&arrLangfile [&fileIndex][1].WriteLine(" <HIGHEST_EDUC_LVL>" | &highestEducLvl | "</HIGHEST_EDUC_LVL>");

&arrLangfile [&fileIndex][1].WriteLine("</RECORD" | String(&recordNbr) | ">");

d) Modify the HRS_COMMON: SEARCH:BUS:ApplicantIndex PeopleCode.

The buildInput() method would be modified like this:

&entry.setAppPerStatus(&rec.APP_PER_STATUS.Value);

&entry.setStatusCode(&rec.STATUS_CODE.Value);

&entry.setLogID(&rec.HRS_AL_LOG_ID.Value);

&entry.setHighestEducLvl(&rec.HIGHEST_EDUC_LVL.Value);

e) Modify the HRS_REC_SCHAP_A_SP sub-page.

Add a derived field to the HRS_REC_SCHAP_A_SP sub-page to collect the minimum highest education level that the end-user desires..

f) Modify the HRS_COMMON:SEARCH:BUS:VerityAppSchProvider PeopleCode.

Add a new Highest Education Level attribute to this class. Modify the BuildAppQueryText() method to recognise the new the highest education level object attribute.

g) Modify the HRS_COMMON:CMP_HRS_REC_SCH_APP:UI:UIUtils PeopleCode retrieveCriteria() method to retireive the new field from the page:

/* Country Description */

If All(HRS_SCH_WRK.COUNTRY.Value) And

( Not &isBasicSearch) Then

&criteria.country = HRS_SCH_WRK.COUNTRY.Value;

&criteriaExists = True;

End-If;

/* Highest Education Level */

If All(HRS_SCH_WRK.HIGHEST_EDUC_LVL.Value) And

( Not &isBasicSearch) Then

&criteria.highestEducLvl = HRS_SCH_WRK.HIGHEST_EDUC_LVL.Value;



&criteriaExists = True;

End-If;



Appendix

GLOSSARY OF TERMS Collection Verity terminology that is equivalent to an searchable

index.

Document In this paper, the word “document” generally refers to the Verity document, which includes the Resume Text, accomplishments (from Applicant Data), competencies (from Applicant Data), work experience (from Applicant Data), and education experience (from Applicant Data).

Locale Verity libraries that are used to build collections and perform searches with language-specific rules

Operator A verity key word that is used to alter the nature of a query.

Zone An area of the document that contains well-defined data. For example, Education experience is a zone, since only data that is specific to an applicant’s education experience is indexed there.

FREQUENTLY ASKED QUESTIONS Q. Process Monitor tells me that the Applicant Index Application Engine has run to success, but when I

try to perform an applicant search, the system issues the following error:

A. This is the most common symptom encountered when setting up a search collection. Perform the following checks:

Verity has been installed on the machines that house my application server domain AND process scheduler domain.

The paths entered on the Applicant Index run control page are correct. If this is true, double-check that the paths are accessible to the Process Scheduler used for the Application Engine process and the Application Server (e.g. a shared filesystem).

Verify that the following directory structure exists. Verity’s would have created this structure if it ran successfully. Assuming an installation directory of C:\PTHOME, the new directory structure would be: c:\PTHOME\data\search\<dtabase>\HRS_ResumeText\Eng\parts. There are other directories at this level also, but the collection was successfully created if there are two files in the parts directory. The files are: *.ddd and *.did. If these files exist, then the most likely problem is that the Application Server Domain has not been correctly configured.



Q. When I perform a search, I get the following error message: “Cannot access property IndexName on Null Object.”

A. Verity has not been installed on the Application Server machine. Consult your PeopleTools documentation and install Verity on the Application Server machine.

Q. The Process Monitor indicates that the Application Engine ran to an “Error” status.

A. Check the Process Scheduler logs for the Run Control instance. One of the more common problems is that a “File Cannot be Open or Found.”

i) Ensure that the following paths have read and write access: <ToolsHome>\data\search\HRS_ResumeText and Attachment Root Directory.

Q. Verity returns unexpected results. Applicants are not being returned that I would expect to be returned, and applicants that ARE being returned have been removed from the system.

A. The collection and the data in your database are out of sync. A collection is a snapshot of your applicant data at the time that the Applicant Index Application Engine has been run, so you will want to schedule the Applicant Index Application Engine to run on a periodic basis.



LANGUAGE SUPPORT

A PeopleSoft “Provided” Language is one for which PeopleSoft provides the translations. These must be licensed.

A PeopleSoft “Supported” Language is one for which PeopleSoft allows data entry but does not provide translations.

Languages are supported on 8.20 and 8.44 Tools unless otherwise noted.

PeopleSoft Provided Languages – based on Rel Defns (must be licensed)

PeopleSoft Supported Languages

Verity Languages available

Arabic (limited support) Arabic (8.44 Tools)

Bulgarian Bulgarian

Chinese (Simplified) Chinese (Simplified) Chinese (Simplified)

Chinese (Traditional) Chinese (Traditional) Chinese (Traditional)

Czech Czech (8.44 Tools)

Danish (8.44 Tools) Danish Danish

Dutch Dutch Dutch

English English English

Finnish Finnish Finnish

French French French

French (Canadian) French (Canadian) French

German German German

Greek Greek (8.44 Tools)

Hebrew (limited support) Hebrew (8.44 Tools)

Hungarian Hungarian (8.44 Tools)

Italian Italian Italian

Japanese Japanese Japanese

Korean Korean

Norwegian (Bokmal) Norwegian (Bokmal)

Norwegian (Nynorsk) Norwegian (Nynorsk)

Polish (8.44 Tools) Polish Polish

Portuguese Portuguese Portuguese

Russian Russian (8.44 Tools)

Spanish Spanish Spanish

Swedish Swedish Swedish



Thai Thai

Turkish Turkish (8.44 Tools)



INSTALLATION STEPS

Set up your search collection and configure the application server domains that will access the search collection. The following is a summary of the set up steps.

Install Verity on Process Scheduler Machines and Application Server Machines

Consult your PeopleTools documentation for Verity installation. Collection-building is an Application Engine process, so make sure that you have installed Verity on all machines that will be used as Process Schedulers for this process.

Set up directories for Search Collection

One to many application servers may access the search collection. Determine an appropriate location for the search collection based on the application server(s) that will reference the collection during a search. As at release 8.9, all required directories are automatically created during the index build – no further manual configuration is required.

Run the Applicant Search Collection Builder

1. Navigate to Recruiting > Administration > Build Applicant Index

Figure 1

2. Select “Run”. 3. Choose the appropriate Server that corresponds to the values entered in Step

1.



Figure 2

OPERATOR REFERENCE

This section describes each Verity operator in detail. Where appropriate, each description includes an example of simple syntax and explicit syntax. Operators are listed alphabetically.

ACCRUE Operator

The ACCRUE operator selects documents that include at least one of the search elements you specify. Valid search elements are two or more words or phrases. Retrieved documents are relevance-ranked.

The ACCRUE operator scores retrieved documents according to the presence of each search element in the document using "the more, the better" approach: the more search elements found in the document, the better the document's score. Following are examples of search syntax.

Simple Syntax

To select documents containing stemmed variations of the words "computers" and "laptops," you can enter the following:

computers <ACCRUE> laptops

computers, laptops



Explicit Syntax

To select documents containing any of the literal words "IBM," "Apple," and "Sun," you can enter the following:

<ACCRUE>("ibm","apple","sun")

AND Operator

The AND operator selects documents that contain all of the search elements you specify. Documents retrieved using the AND operator are relevance-ranked. Following are examples of search syntax.

Simple Syntax

To select documents which contain stemmed variations of the phrase "pharmaceutical companies" and stemmed variations of the word "stock," you can enter the following:

pharmaceutical companies AND stock

Only those documents which contain both search elements, or stemmed variations of them (for example, pharmaceutical company; stocks, etc.), are retrieved and ranked according to their score.

Explicit Syntax

To select documents that contain both the literal phrase "pharmaceutical companies" and the literal word "stock," you can enter the following:

"pharmaceutical companies" AND "stock"

Since the phrase "pharmaceutical companies" and the word "stock," are enclosed in double-quotation marks, documents containing these words will not be relevance-ranked.

= (EQUALS) Operator

The EQUALS operator selects documents whose document field values are exactly the same as the search string you specify. For example, assume a document field named DATE has been defined. To select only those documents dated October 24, 1992, you can enter the following:

DATE = 10-24-92

> (GREATER THAN) Operator

The GREATER THAN operator selects documents whose document field values are greater than the search string you specify. For example, assume a document field named DATE has been defined. To select only those documents dated after October 24, 1992, you can enter the following:

DATE > 10-24-92



>= (GREATER THAN OR EQUAL TO) Operator

The GREATER THAN OR EQUAL TO operator selects documents whose document field values are greater than or equal to the search string you specify. For example, assume a document field named DATE has been defined. To select only those documents dated on or after October 24, 1992, you can enter the following:

DATE >= 10-24-92

< (LESS THAN) Operator

The LESS THAN operator selects documents whose document field values are less than the search string you specify. For example, assume a document field named DATE has been defined. To select only those documents dated before February 14, 1991, you can enter the following:

DATE < 02-14-91

<= (LESS THAN OR EQUAL TO) Operator

The LESS THAN OR EQUAL TO operator selects documents whose document field values are less than or equal to the search string you specify. For example, assume a document field named DATE has been defined. To select only those documents dated prior to and including February 14, 1991, you can enter the following:

DATE <= 02-14-91

IN Operator

The IN operator selects documents that contain specified values in one or more document zones. A document zone represents a region of a document, such as the document's summary, date, or body text. The IN operator only works if document zones have been defined in your collections. If you use the IN operator to search collections for which zones are not defined, no documents will be selected. In addition, the zone name you specify must match the zone names defined in your collections. Consult your collection administrator to determine what zones have been defined for what collections.

The following query expression searches document zones named "summary" using a topic named "safety."

(safety <IN> summary)

To search with multiple words, phrases, or topics enclose them in parentheses. The next query expression searches document zones named "summary" using a topic named "safety" and stemmed variations of the word "warning."

((safety, warning) <IN> summary)

To search multiple zones, separate them with commas and enclose them in parentheses. The next query expressions search both the "summary" zone and the "title" zone using the "safety" topic and stemmed variations of the word "warning."

((safety, warning) <IN> summary, title)

(safety, warning) <IN> (summary, title)

Note that you must enclose query expressions containing commas, in parentheses. The following example searches the "summary" zone using the topic "safety" and the phrase "environmental regulation."

(safety, environmental regulation) <IN> summary

The next example use the topic "safety" and the phrase "environmental regulation" again to search both the "summary" zone and the "title" zone.



(safety, environmental regulation) <IN> (summary, title)

NEAR Operator

The NEAR operator selects documents containing specified search terms within close proximity to each other. Document scores are calculated based on the relative number of words between search terms. For example, if the search expression includes two words, and those words occur next to each other in a document (so that the region size is two words long), then the score assigned to that document is 1.0. Thus, the document with the smallest region containing all search terms always receives the highest score. Documents whose search terms are not within 1000 words of each other are not selected, since the search terms are probably too far apart to be meaningful within the context of the document.

The NEAR operator is similar to the other proximity operators in the sense that the search words you enter must be found within close proximity of one another. However, unlike other proximity operators, the NEAR operator calculates relative proximity and assigns scores based on its calculations. Following are examples of search syntax.

Simple Syntax

Use simple syntax to retrieve relevance-ranked documents based on word stem variations and relative proximity. For example, to retrieve relevance-ranked documents which contain stemmed variations of the words "war" and "peace" within close proximity to each other, you can enter the following:

war <NEAR> peace

Explicit Syntax

Use explicit syntax to retrieve relevance-ranked documents based on relative proximity only. To retrieve relevance-ranked documents which contain the literal words "war", "and", "peace" within close proximity to each other, you can enter the following:

<NEAR>("war", "and", "peace")

NEAR/N Operator

The NEAR/N operator selects documents containing two or more words within N number of words of each other, where N is an integer. Document scores are calculated based on the relative distance of the specified words when they are separated by N words or less. Documents containing the specified words separated by more than N words are not selected. For example, if the search expression NEAR/5 is used to find two words within five words of each other, a document that has the specified words within three words of each other is scored higher than a document that has the specified words within five words of each other.

The N variable can be an integer between 1 and 1,024, where NEAR/1 searches for two words that are next to each other. If N is 1,000 or above, you must specify its value without commas, as in NEAR/1000.

The NEAR/N operator is similar to the other proximity operators in the sense that the search words you enter must be found within a relative proximity of one another. However, unlike NEAR, the NEAR/N operator assigns scores based on relative proximity. Following are examples of search syntax.

Simple Syntax

Use simple syntax to retrieve relevance-ranked documents based on word stem variations and relative proximity. For example, to retrieve relevance-ranked documents which contain stemmed variations of the words "commute," "bicycle," "train," and "bus" within N words of each other, you can enter the following:

commute <NEAR/10> bicycle <NEAR/10> train <NEAR/10> bus



The value of N must be the same in all instances.

Explicit Syntax

Use explicit syntax to retrieve relevance-ranked documents based on relative proximity only. To retrieve relevance-ranked documents which contain the literal words "commute," "bicycle," "train," and "bus" within N words of each other, you can enter the following:

<NEAR/10>("commute", "bicycle", "train", "bus")

Using the ORDER Modifier

You can use the NEAR/N operator with the ORDER modifier to perform ordered proximity searches. For more information about the ORDER modifier, see "ORDER Modifier" in this chapter.

The following syntax examples search for documents containing the words "diver," "kills," "shark" in that order within a 20-word proximity to each other.

Simple syntax:

diver <ORDER><NEAR/20> kills <ORDER><NEAR/20> shark

Explicit syntax:

<ORDER><NEAR/20>("diver", "kills", "shark")

You can also use the NEAR/N operator with the ORDER modifier to duplicate the behavior of the PHRASE operator. For example, to search for documents containing the phrase "world wide web," you can use the following syntax:

Simple syntax:

world <ORDER><NEAR/1> wide <ORDER><NEAR/1> web

Explicit syntax:

<ORDER><NEAR/1> ("world", "wide", "web")

OR Operator

The OR operator selects documents that show evidence of at least one of your search elements. Documents selected using the OR operator are relevance-ranked. Following are examples of search syntax.

Simple Syntax

To select documents which contain stemmed variations of the word "election" or the phrases "national elections" or "senatorial race" you can enter the following:

election OR national elections OR senatorial race



Only those documents which contain at least on of the search elements, or a stemmed variation of at least one of them, are retrieved and ranked according to their score.

Explicit Syntax

To retrieve documents that contain either the literal word "computer" or the literal word "security," you can enter the following:

"computer" OR "security"

PARAGRAPH Operator

The PARAGRAPH operator selects documents that include all of the search elements you specify within a paragraph. Valid search elements are two or more words or phrases. You can specify search elements in a sequential or a random order. Documents are retrieved as long as search elements appear in the same paragraph. Following are examples of search syntax.

Simple Syntax

To retrieve relevance-ranked documents which contain stemmed variations of the word "drug" and the phrase "cancer treating" in the same paragraph, you can enter the following:

drug <PARAGRAPH> cancer treating

To search for three or more words or phrases, you must use the PARAGRAPH operator between each word or phrase.

Explicit Syntax

To retrieve documents which contain the literal words "activity" and "management" in the same paragraph, you can enter the following:

<PARAGRAPH>("activity", "management")

Documents are not relevance-ranked with explicit syntax unless you use the MANY modifier, as in:

<MANY><PARAGRAPH>("activity", "management")

PHRASE Operator

The PHRASE operator selects documents that include a phrase you specify. A phrase is a grouping of two or more words that occur in a specific order. Following are examples of search syntax.

Simple Syntax

By default, two or more words separated by a space are considered to be a phrase in simple syntax. In addition, two or more words enclosed in double quotation marks are considered to be a phrase. To retrieve relevance-ranked documents that contain the phrase "mission oak," you can enter any of the following:

mission oak

"mission oak"

mission <PHRASE> oak



Explicit Syntax

To retrieve documents containing the phrase "black and white," you can enter the following:

<PHRASE>(black "and" white)


<MANY><PHRASE>(black "and" white)

SENTENCE Operator

The SENTENCE operator selects documents that include all of the words you specify within a sentence. You can specify search elements in a sequential or a random order. Documents are retrieved as long as search elements appear in the same sentence. Following are examples of search syntax.

Simple Syntax

To retrieve relevance -ranked documents which contain stemmed variations of the words "American," and "innovation" within the same sentence, you can enter the following:

american <SENTENCE> innovation

Explicit Syntax

To retrieve documents containing the literal words "merge," "annual," and "purchases" when they appear in the same sentence, you can enter the following:

<SENTENCE>("merge", "annual", "purchases")


<MANY><SENTENCE>("merge", "annual", "purchases")

SOUNDEX Operator

The SOUNDEX operator selects documents that include one or more words that "sound like," or whose letter pattern is similar to, the word specified. Words have to start with the same letter as the word you specify to be selected. For example, to retrieve documents containing a word that is close in structure to the word "sale," you can enter the following:

<SOUNDEX> sale

The documents retrieved will include words such as, "sale," "sell," "seal," "shell," "soul," and "scale." Documents are not relevance-ranked unless the MANY modifier is used, as in:

<MANY><SOUNDEX> sale

Your collection administrator must have configured collections to support the SOUNDEX operator. See your collection administrator for information.



THESAURUS Operator

The THESAURUS operator selects documents that contain one or more synonyms of the word you specify. For example, to retrieve documents containing synonyms of the word "altitude" you can enter the following:

<THESAURUS> altitude

The documents retrieved will include words such as, "loftiness," "tallness," "pitch," "height," or "elevation." Documents are not relevance-ranked unless the MANY modifier is used, as in:

<MANY><THESAURUS> altitude

WILDCARD Operator

The WILDCARD operator selects documents that contain matches to a character string containing variables. The WILDCARD operator lets you define a search string with variables, which can be used to locate related word matches in documents. For example, to retrieve documents that contain words such as, "pharmaceutical," "pharmacology," and "pharmacodynamics," you can enter the following:

pharmac*

Documents are not relevance-ranked unless the MANY modifier is used, as in:

<MANY> pharmac*

You can use the following wildcard characters to represent variable portions of search strings with the WILDCARD operator.

Character

Function

?

Specifies one of any alphanumeric character, as in ?an, which locates "ran," "pan," "can," and "ban." It is not necessary to specify the WILDCARD operator when you use the question mark. The question mark is ignored in a set ([ ]) or in an alternative pattern ({ }).

*

Specifies zero or more of any alphanumeric character, as in corp*, which locates "corporate," "corporation," "corporal," and "corpulent." It is not necessary to specify the WILDCARD operator when you use the asterisk, and you should not use the asterisk to specify the first character of a wildcard string. The asterisk is ignored in a set ([ ]) or in an alternative pattern ({ }).

[ ]

Specifies one of any character in a set, as in <WILDCARD> `c[auo]t`, which locates "cat," "cut," and "cot." You must enclose the word that includes a set in backquotes (`), and there can be no spaces in a set.

{ }

Specifies one of each pattern separated by a comma, as in <WILDCARD> `bank{s,er,ing}`, which locates "banks," "banker," and "banking." You must enclose the word that includes a pattern in backquotes (`), and there can be no spaces in a set.

^

Specifies one of any character not in the set, as in <WILDCARD> `st[^oa]ck`, which excludes "stock" and stack but locates "stick" and "stuck." The caret (^) must be the first character after the left bracket ([) that introduces a set.



-

Specifies a range of characters in a set, as in <WILDCARD> `c[a-r]t`, which locates every three-letter word from "cat" to "crt."

WORD Operator

Selects documents that include one or more instances of a word you specify. For example, to search for documents that contain the word "rhetoric," without also considering the words "rhetorical" and "rhetorician," you can enter the following:

<WORD> rhetoric

Documents are not relevance-ranked unless the MANY modifier is used, as in:

<MANY><WORD> rhetoric