The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.

NAME

WWW::Search::Jobserve - backend for searching www.jobserve.com

SYNOPSIS

    use WWW::Search;
    my $oSearch = new WWW::Search('Jobserve');
    my $sQuery = WWW::Search::escape_query("(Fast Food Operative) and PERL");
    $oSearch->native_query($sQuery, { job_category => 'it' });
    while (my $oResult = $oSearch->next_result())
      { 
        print $oResult->url, "\n"; 
        print $oResult->title, "\n";
        print $oResult->description, "\n";
      }

                                      

DESCRIPTION

This class is a Jobserve specialisation of WWW::Search. It handles making, retrieving and interpreting Jobserve searches http://www.jobserve.com.

This class exports no public interface; all interaction should be done through WWW::Search objects.

NOTES

This class can be used to query both the UK and Australian Jobserve sites, see below.

The search will terminate unless job_category is set in the native_query options.

The results are ordered Best Match first (unless 'job_order' => 'DateTime' is specified).

OPTIONS

    Parameters Available:

    job_category job_type job_lookahead job_order jobserve_site

    Job Category

    Job Categories must be specified by setting job_category in the native_query options:

      $oSearch->native_query($sQuery, { job_category => 'it' });
      

    The value of this is simply the prefix you see jobserve insert into the url once you've clicked beyond the front page. E.g.

      http://www.it.jobserve.com            { job_category => 'it' }
      http://www.engineering.jobserve.com   { job_category => 'engineering' }
      

    etc.

    Job Type

    Job Types are (Any|Contract|Permanent). To specifically search for one contract type, set 'job_type' => (*|C|P) to the query options:

      $oSearch->native_query($sQuery, { job_type => 'C',  job_category => 'it' } );

    The search defaults to All

    Days Ahead

    Choices of how many days to look ahead are (5|4|3|2|1|0). To specifically search for x working days ahead, set 'job_lookahead' => (5|4|3|2|1|0) to the query options:

      $oSearch->native_query($sQuery, { job_lookahead => '2', job_category => 'it' } );
      

    The search defaults to 5

    Result Order

    Choices of how to order results are (Best Match|Latest Job). To alter the result order, set 'job_order' => (Rank|DateTime) to the query options:

      $oSearch->native_query($sQuery, { job_order => 'DateTime', job_category => 'it' } );

    The search defaults to Best Match.

    Different Jobserve Sites

    There are currently two Jobserve websites supported by this module namely United Kingdom and Australia. The search will default to the UK site unless the parameter, 'jobserve_site' => (uk|au) is set in the query options:

      $oSearch->native_query($sQuery, { jobserve_site => 'au', job_category => 'it' } );
      

    The search defaults to uk

    Invoke all parameters like so:

        $oSearch->native_query($sQuery, { job_category  => 'it', 
                                          job_type      => 'C',
                                          job_lookahead => '2',
                                          job_order     => 'DateTime',
                                          jobserve_site => 'au', } );
        

SEE ALSO

To make new back-ends, see WWW::Search.

BUGS

Doubt it. Please tell me if you find any! Better still have a go at fixing them.

AUTHOR

WWW::Search::Jobserve was written by Andy Pritchard (pilchkinstein@hotmail.com).

WWW::Search::Jobserve is maintained by Andy Pritchard

LEGALESE

THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

VERSION HISTORY

1.02

Altered parse_tree for cases where another href link is inserted before the job title and link

1.01

Altered POD and added a README

1.00

Released to the public.

1 POD Error

The following errors were encountered while parsing the POD:

Around line 236:

You can't have =items (as at line 246) unless the first thing after the =over is an =item