1
|
<?php
|
2
|
#############################################################################
|
3
|
# File containing all the paramaters that could potentially need to be
|
4
|
# configured for the job.
|
5
|
#
|
6
|
# $url: The url for the desired Taiper service
|
7
|
# $seperator: The delimiter for the flat file.
|
8
|
# buildFilter(): Function to specify the search paramaters.
|
9
|
# desiredConcepts: Desired data to be returned by the service.
|
10
|
#
|
11
|
#############################################################################
|
12
|
|
13
|
# The url of the desired Taiper service
|
14
|
$url = 'http://tapir.cria.org.br/tapirlink/tapir.php/specieslink';
|
15
|
|
16
|
# The seperator to be used in the flat file to seperate the
|
17
|
# data fields of each record.
|
18
|
$seperator = '`';
|
19
|
|
20
|
# Tapir services have an extremely flexable syntax to search for
|
21
|
# records with the desired properties. However, this flexibility
|
22
|
# makes it rather difficult to generalize the search possibilities
|
23
|
# and quickly come up with appropriate xml. As such, the current
|
24
|
# solution is to build the filter node here. See the associated
|
25
|
# documentation on how to build the filter:
|
26
|
# http://www.tdwg.org/dav/subgroups/tapir/1.0/docs/tdwg_tapir_specification_2010-05-05.htm#toc47
|
27
|
function buildFilter() {
|
28
|
$filter =
|
29
|
'<equals>' .
|
30
|
'<concept id="http://rs.tdwg.org/dwc/dwcore/Kingdom"/>' .
|
31
|
'<literal value="Plantae"/>' .
|
32
|
'</equals>';
|
33
|
return $filter;
|
34
|
}
|
35
|
|
36
|
?>
|