Changeset 8159 for trunk/gsdl3/web/sites/localsite/collect/infomine/README
- Timestamp:
- 2004-09-27T14:16:58+12:00 (20 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gsdl3/web/sites/localsite/collect/infomine/README
r6238 r8159 13 13 not useful. 14 14 15 The buildConfig.xml file just needs to specify the InfomineProxy serviceRack 16 class. 15 The buildConfig.xml file needs to specify the IViaProxy serviceRack 16 class. Inside this element should be the url of the iVia installation that 17 you want to connect to. Here is an example: 18 19 <buildConfig> 20 <metadataList/> 21 <serviceRackList> 22 <serviceRack name="IViaProxy"> 23 <iViaServer url="http://infominehelper.ucr.edu"/> 24 </serviceRack> 25 </serviceRackList> 26 </buildConfig> 27 17 28 18 29 The following describes the iVia cgi scripts. … … 21 32 ************************ 22 33 23 http://infomine.ucr.edu/cgi-bin/canned_search34 <serverhome>/cgi-bin/canned_search 24 35 25 36 Parameters: … … 42 53 *********************************************** 43 54 44 http://infomine.ucr.edu/cgi-bin/view_record55 <serverhome>/cgi-bin/view_record 45 56 46 57 Parameters: … … 60 71 ****************************************** 61 72 62 http://infomine.ucr.edu/cgi-bin/view_record_set73 <serverhome>/cgi-bin/view_record_set 63 74 64 75 Parameters: … … 83 94 84 95 There are many different metadata fields that can be requested, including 85 keywords, subjects, description, access, expert_created, foreign_source,96 keywords, subjects, ivia_description, access, expert_created, foreign_source, 86 97 foreign_id, and so on. 87 98
Note:
See TracChangeset
for help on using the changeset viewer.