1 | This collection talks to the iVia installation at INFOMINE, Riverside,
|
---|
2 | California. The software should work with any iVia installation.
|
---|
3 |
|
---|
4 | Cgi scripts are called to do searching of and retrieval from the database.
|
---|
5 | All three are fairly generic CGI scripts; iVia's "theming" ability is used to
|
---|
6 | get the data back in the format we want-- there is a gsdl3 theme.
|
---|
7 |
|
---|
8 | To create a new collection that talks to an iVia database, you need to create
|
---|
9 | the two configuration files, collectionConfig.xml, and buildConfig.xml.
|
---|
10 | The collectionConfig.xml needs to contain any display information for the
|
---|
11 | collection, and any metadata that is available. Also it can contain format
|
---|
12 | information for document display or search result lists if the default is
|
---|
13 | not useful.
|
---|
14 |
|
---|
15 | The buildConfig.xml file just needs to specify the InfomineProxy serviceRack
|
---|
16 | class.
|
---|
17 |
|
---|
18 | The following describes the iVia cgi scripts.
|
---|
19 |
|
---|
20 | For performing a search:
|
---|
21 | ************************
|
---|
22 |
|
---|
23 | http://infomine.ucr.edu/cgi-bin/canned_search
|
---|
24 |
|
---|
25 | Parameters:
|
---|
26 | Required parameters: theme=gsdl3&query=xxx
|
---|
27 | Useful parameters: no_of_records_per_page=10&start_page_no=1&fields='kw,su'
|
---|
28 | Other parameters: http://infomine.ucr.edu/help/adders/index.php?section=11
|
---|
29 | Example: http://infomine.ucr.edu/cgi-bin/canned_search?query=tree&
|
---|
30 | theme=gsdl3&no_of_records_per_page=10&start_page_no=1
|
---|
31 |
|
---|
32 | Fields include Title (ti), Subject (su), Keyword (kw), Author (au),
|
---|
33 | Description (de) and full text (fu). 'all' will search all fields.
|
---|
34 | It's possible to do uch more advanced searches including phrase searching
|
---|
35 | and bolean queries.
|
---|
36 |
|
---|
37 | The canned_search result page will look something like this:
|
---|
38 | Resources: 58
|
---|
39 | Ids: 1015 22128 1730 6020 2981 1014 20147 2097 46569 4360
|
---|
40 |
|
---|
41 | For getting an HTML representation of a record:
|
---|
42 | ***********************************************
|
---|
43 |
|
---|
44 | http://infomine.ucr.edu/cgi-bin/view_record
|
---|
45 |
|
---|
46 | Parameters:
|
---|
47 | Required parameters: theme=gsdl3&record_id=x
|
---|
48 | Example: http://infomine.ucr.edu/cgi-bin/view_record?theme=gsdl3&
|
---|
49 | record_id=2097
|
---|
50 |
|
---|
51 | The result page will be an HTML fragment; specifically, it will be an HTML
|
---|
52 | table. Again, the formatting is quite flexible. There's one current
|
---|
53 | problem: a lot of the data is displayed as hypertext links to new infomine
|
---|
54 | searches; This should be changed eventually.
|
---|
55 |
|
---|
56 | For now, the Greenstone services process the records, replacing infomine
|
---|
57 | links with Greenstone links where possible.
|
---|
58 |
|
---|
59 | For getting metadata for a set of records:
|
---|
60 | ******************************************
|
---|
61 |
|
---|
62 | http://infomine.ucr.edu/cgi-bin/view_record_set
|
---|
63 |
|
---|
64 | Parameters:
|
---|
65 | Required parameters: theme=gsdl3&record_id_list=id1,id2,id3
|
---|
66 | Optional parameter: field_list=f1,f2,f3
|
---|
67 | Example: http://infomine.ucr.edu/cgi-bin/view_record_set?theme=gsdl3&
|
---|
68 | record_id_list=1015,2128,1730&field_list=url,title
|
---|
69 |
|
---|
70 | The result will look like this:
|
---|
71 |
|
---|
72 | Record: 1015
|
---|
73 | url: http://www.fruit.affrc.go.jp/index-e.html
|
---|
74 | title: National Institute of Fruit Tree Science (Japan)
|
---|
75 |
|
---|
76 | Record: 2128
|
---|
77 | url: http://www.publish.csiro.au/journals/ajb/
|
---|
78 | title: Australian Journal of Botany
|
---|
79 |
|
---|
80 | Record: 1730
|
---|
81 | url: http://usda.mannlib.cornell.edu/reports/erssor/specialty/fts-bb/
|
---|
82 | title: Fruit and Tree Nuts : USDA Economics and Statistics System
|
---|
83 |
|
---|
84 | There are many different metadata fields that can be requested, including
|
---|
85 | keywords, subjects, description, access, expert_created, foreign_source,
|
---|
86 | foreign_id, and so on.
|
---|
87 |
|
---|
88 | Note that the metadata always fits on one line (whitespace is explicitly
|
---|
89 | normalised to space) to make parsing easier. Generally, the metadata is
|
---|
90 | in ISO-8859-15 format (i.e. ISO-8859-1 plus the Euro currency symbol).
|
---|
91 | Metadata is usually plain text, though the description field may contain
|
---|
92 | HTML entities and limited set of HTML elements (bold tags, italic tags,
|
---|
93 | links, and a few others).
|
---|
94 |
|
---|