Changeset 21793
- Timestamp:
- 2010-03-15T15:41:11+13:00 (14 years ago)
- Location:
- main/trunk/greenstone3/web/sites/localsite/collect
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
main/trunk/greenstone3/web/sites/localsite/collect/gs2mgdemo/etc/collectionConfig.xml
r21788 r21793 81 81 <serviceRack name="OAIPMH"> 82 82 <ListMetadataFormats> 83 84 83 <!--What metadata sets to support is collection specific. To support other metadata schema, simply add a metadataFormat element here. 84 The support of unqualified Dublin Core metadata set is mendatory in the oai specification. 85 85 --> 86 <metadataFormat metadataPrefix="oai_dc"> 87 <metadataPrefix>oai_dc</metadataPrefix> 88 <schema>http://www.openarchives.org/OAI/2.0/oai_dc.xsd</schema> 89 <metadataNamespace>http://www.openarchives.org/OAI/2.0/oai_dc/</metadataNamespace> 90 <mappingList> 91 <!-- 92 The mapping is in the form: <publicly supported metadata name>,<mapped metadata name>, short as <A>,<B> 93 The first metadata name is medatory; if there is no mapped name followed, then the first name must be used by the records and 94 searchable in the database, otherwise it is the mapped name stored in the database. The number of mapping elements matches the 95 number of external metadata of the records. If only one name is present, the returned metadata will use this name plus the retrieved value; 96 if both <A>,<B> are present, the returned metadata will use <A>'s name plus <B>'s value retrieved from database. 97 98 **Bear in mind: if this mapping list is not present, the standard dc. metadata names (15 in total) will be used to retrieve metadata in the database. 99 --> 100 <mapping>dc.Title,dls.Title</mapping> 101 <mapping>dc.Subject,dls.Subject</mapping> 102 <mapping>dc.Language,dls.Language</mapping> 103 <mapping>dc.Organization,dls.Organization</mapping> 104 </mappingList> 105 </metadataFormat> 106 </ListMetadataFormats> 86 <metadataFormat metadataPrefix="oai_dc"> 87 <metadataPrefix>oai_dc</metadataPrefix> 88 <schema>http://www.openarchives.org/OAI/2.0/oai_dc.xsd</schema> 89 <metadataNamespace>http://www.openarchives.org/OAI/2.0/oai_dc/</metadataNamespace> 90 <!-- a custom mapping as this collection doesn't have dc metadata --> <mappingList> 91 <mapping>dc:title,dls.Title</mapping> 92 <mapping>dc:subject,dls.Subject</mapping> 93 <mapping>dc:language,dls.Language</mapping> 94 <mapping>dc:publisher,dls.Organization</mapping> 95 </mappingList> 96 </metadataFormat> 97 </ListMetadataFormats> 107 98 </serviceRack> 108 99 </serviceRackList> -
main/trunk/greenstone3/web/sites/localsite/collect/gs2mgppdemo/etc/collectionConfig.xml
r21778 r21793 85 85 <!-- comment out the following serviceRack if you want to disable OAI for this collection --> 86 86 <serviceRack name="OAIPMH"> 87 <ListMetadataFormats>88 <!--What metadata sets to support is collection specific. To support other metadata schema, simply add ametadataFormat element here.87 <ListMetadataFormats> 88 <!--What metadata sets to support is collection specific. To support other metadata schema, add another metadataFormat element here. 89 89 The support of unqualified Dublin Core metadata set is mandatory in the oai specification. 90 90 --> 91 91 <metadataFormat metadataPrefix="oai_dc"> 92 92 <metadataPrefix>oai_dc</metadataPrefix> 93 93 <schema>http://www.openarchives.org/OAI/2.0/oai_dc.xsd</schema> 94 94 <metadataNamespace>http://www.openarchives.org/OAI/2.0/oai_dc/</metadataNamespace> 95 <!--<metadataElements>dc.Title,dc.Creator,dc.Subject,dc.Description,dc.Publisher,dc.Contributor,dc.Date,dc.Type,dc.Format,dc.Identifier,dc.Source,dc.Language,dc.Relation,dc.Coverage,dc.Rights</metadataElements> 96 --> 97 <mappingList> 98 <!-- 99 The mapping is in the form: <publicly supported metadata name>,<mapped metadata name>, short as <A>,<B> 100 The first metadata name is medatory; if there is no mapped name followed, then the first name must be used by the records and 101 searchable in the database, otherwise it is the mapped name stored in the database. The number of mapping elements matches the 102 number of external metadata of the records. If only one name is present, the returned metadata will use this name plus the retrieved value; 103 if both <A>,<B> are present, the returned metadata will use <A>'s name plus <B>'s value retrieved from database. 104 105 **Bear in mind: if this mapping list is not present, the standard dc. metadata names (15 in total) will be used to retrieve metadata in the database. 106 107 **The only case when this mapping is not present is that: 1. this metadata format is oai_dc; 2. the metadata is also stored in the database by Dublin Core's names. 108 --> 109 <mapping>dc.Title,dls.Title</mapping> 110 <mapping>dc.Subject,dls.Subject</mapping> 111 <mapping>dc.Language,dls.Language</mapping> 112 <mapping>dc.Organization,dls.Organization</mapping> 113 <!-- This mapping example means that the dc.Title is requested and the value of the metadata Title, which is used in this repository, is returned as response. --> 95 <!-- a custom mapping as this collection doesn't have dc metadata --> <mappingList> 96 <mapping>dc:title,dls.Title</mapping> 97 <mapping>dc:subject,dls.Subject</mapping> 98 <mapping>dc:language,dls.Language</mapping> 99 <mapping>dc:publisher,dls.Organization</mapping> 114 100 </mappingList> 115 101 </metadataFormat> 116 <!--117 This metadata format is an example of user created metadata fields118 <metadataFormat metadataPrefix="oai_gs">119 <metadataPrefix>oai_gs</metadataPrefix>120 <schema>http://www.greenstone.org/OAI/2.0/oai_gs.xsd</schema>121 <metadataNamespace>http://www.greenstone.org/OAI/2.0/oai_gs/</metadataNamespace>122 <mappingList>123 <mapping>dls.Title</mapping>124 <mapping>dls.Subject</mapping>125 <mapping>dls.Language</mapping>126 <mapping>dls.Organization</mapping>127 </mappingList>128 </metadataFormat>129 -->130 102 </ListMetadataFormats> 131 103 </serviceRack>
Note:
See TracChangeset
for help on using the changeset viewer.