Custom Query (420 matches)
Results (37 - 39 of 420)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#843 | fixed | GS3 OAImappings structure needs to be more XML | ||
Description |
See web\WEB-INF\classes\OAIConfig.xml and gs2\collect\modelcol\etc\collectionConfig.xml At present it looks like: <mapping>dc:title,Title</mapping> for each mapping to dc:Title. Want XML structure, so that multiple mappings can be specified for the same dc:Title. It can then look like: <mapping type="dc:title">
</mapping> The above will map both ex.Title and dc.Title to oa_dc's dc:title |
|||
#840 | invalid | RSyncTextArea requires escaping entity within a GS2 format statement | ||
Description |
RSyncTextArea requires escaping comma with entity in the following GS2 format statement: The assoc file demo collection on nzdl at http://www.nzdl.org/gsdlmod?a=p&p=about&c=assocext-e contains the following format statement:
The last line causes the displayed output to appear like: greenstone1 '):dc.Creator]} instead of greenstone1 :pinky, lala By converting the comma separator for siblings to its html entity equivalent of ,, things work as expected: <td valign="top">[link][icon]link</td>
<td valign="top">[highlight]
|
|||
#838 | fixed | Demo collection improvement | ||
Description |
Now we have Restful URLs for Greenstone3, the lucene-jdbm-demo collection should be switched to using OIDtype metadata, so its document identifiers can be even swisher than the HASHxxxx form. There should be a way to put this into the collection configuration file so it happens automatically, rather then the person building the collection needing to remember to add it in on the command line. |