Changeset 10150
- Timestamp:
- 2005-06-22T11:36:03+12:00 (19 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gsdl/src/oaiservr/README.txt
r8182 r10150 7 7 This allows the OAI client to obtain information on the maintainer of 8 8 the server, etc. See the OAI documentation for further information on 9 the Identify verb. These configurations are kept in gsdl/etc/ main.cfg.9 the Identify verb. These configurations are kept in gsdl/etc/oai.cfg. 10 10 11 11 2) Configuring collections to be 'active' OAI collections; just as collections … … 13 13 'visible' or 'invisible' to OAI. By default, collections are NOT served 14 14 via OAI - you have to enable them by adding each collection's name to a 15 list in gsdl/etc/ main.cfg.15 list in gsdl/etc/oai.cfg. 16 16 17 17 3) Mapping your collection metadata to a "Namespace" supported by OAI. At … … 19 19 and metadata fields in a Greenstone collection must be mapped into the 20 20 Dublin Core namespace. This configuration can be done either server-wide, 21 for all collections, in gsdl/etc/oai config.cfg or in the etc/collec.cfg of21 for all collections, in gsdl/etc/oai.cfg or in the etc/collect.cfg of 22 22 each individual collection. 23 23 … … 38 38 purpose, size, origins, etc. 39 39 40 These items are kept in the following items of gsdl/etc/ main.cfg. The syntax rules for these configuration items are the same as formain.cfg - e.g. strings containing spaces should be enclosed in quotation marks. See the main Greenstone configuration documentation for further information.40 These items are kept in the following items of gsdl/etc/oai.cfg. The syntax rules for these configuration items are the same as for gsdl/etc/main.cfg - e.g. strings containing spaces should be enclosed in quotation marks. See the main Greenstone configuration documentation for further information. 41 41 42 42 * repositoryName … … 45 45 One item only, as a valid email address 46 46 * httpdomain 47 NB: in the gsdlsite.cfg file, NOT main.cfg47 NB: in the gsdlsite.cfg file, NOT oai.cfg 48 48 Should not require specific configuration if your Greenstone install 49 49 is already operational through your web server. … … 55 55 oaiinfo sponsor "The Big Cheese Corporation" 56 56 57 Sample items are already provided in the default main.cfg file - please ensure that you complete these in your preferred text editor.57 Sample items are already provided in the default oai.cfg file - please ensure that you complete these in your preferred text editor. 58 58 59 59 … … 61 61 ---------------------------- 62 62 63 In addition to the items above, one further sort of item needs to be added to gsdl/etc/ - a list of the collections that should be made available to OAI clients. This list is supplied in one or more lines in gsdl/etc/main.cfg in the form:63 In addition to the items above, one further sort of item needs to be added to gsdl/etc/oai.cfg - a list of the collections that should be made available to OAI clients. This list is supplied in one or more lines in gsdl/etc/oai.cfg in the form: 64 64 65 65 oaicollection OAIDemo HDL … … 67 67 The first item in each line should be the same - "oaicollection" - followed by one or more collection names. Each collection name should be the name of the folder/directory in the gsdl/collect directory which holds the collection. 68 68 69 Once these items have been added to gsdl/etc/ main.cfg, the final stage of the OAI configuration can begin: mapping from a collection's own metdata fields into the Dublin Core metadata fields used by OAI. This will be detailed in the folloowing section of this document.69 Once these items have been added to gsdl/etc/oai.cfg, the final stage of the OAI configuration can begin: mapping from a collection's own metdata fields into the Dublin Core metadata fields used by OAI. This will be detailed in the folloowing section of this document. 70 70 71 71 … … 85 85 The Dublin Core fieldsname should be given in the form "DC:<fieldname>", as OAI can support other metadata formats, and thus we use "DC:" to be clear that we are mapping to Dublin Core. The fieldnames available for Dublin Core can be found on the central Dublin Core website at http://www.dublincore.org/. 86 86 87 The Greenstone fieldname can be in two formats. The simpler one is simply the name of the field to map from. The more complex one has the name of the collection placed in front of the field name, followed by a colon. e.g. "demo:Title" would mean the metadata field "Title" in the collection called "demo". Using this, all mappings can be stored in the central gsdl/etc/ main.cfg file if you wish, and we recommend this approach.87 The Greenstone fieldname can be in two formats. The simpler one is simply the name of the field to map from. The more complex one has the name of the collection placed in front of the field name, followed by a colon. e.g. "demo:Title" would mean the metadata field "Title" in the collection called "demo". Using this, all mappings can be stored in the central gsdl/etc/oai.cfg file if you wish, and we recommend this approach. 88 88 89 Let us recap at this point with a few example items for a gsdl/etc/ main.cfg:89 Let us recap at this point with a few example items for a gsdl/etc/oai.cfg: 90 90 91 oaimapping Author DC:Creator92 oaimapping title DC:Title93 oaimapping Photos:fileformat DC:Format91 oaimapping Author dc.Creator 92 oaimapping dls.Title dc.Title 93 oaimapping Photos:fileformat dc.Format 94 94 95 The first item maps any occurrence of 'Author' in any collection to the Dublin Core 'Creator' field (there is no 'Author' field in DC). The second i s a straightforward linking of 'title' in any collection to DC:Title.Finally, in the specific collection 'Photos', we will map the unique metadata field 'fileformat' to the Dublin Core 'Format' field.95 The first item maps any occurrence of 'Author' in any collection to the Dublin Core 'Creator' field (there is no 'Author' field in DC). The second item maps 'dls.Title' to 'dc.Title'. Finally, in the specific collection 'Photos', we will map the unique metadata field 'fileformat' to the Dublin Core 'Format' field. 96 96 97 97
Note:
See TracChangeset
for help on using the changeset viewer.