Custom Query (420 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (37 - 39 of 420)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Ticket Resolution Summary Owner Reporter
#843 fixed GS3 OAImappings structure needs to be more XML nobody ak19
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">

<metadata name="Title"/> <metadata name="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 nobody ak19
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:

<td valign="top">[link][icon]link</td> <td valign="top">[ex.equivDocLink][ex.equivDocIcon][ex./equivDocLink]</td> <td valign="top">[highlight] {Or}{[dc.Title],[exp.Title],[ex.Title],Untitled} highlight{If}{[dc.Creator],: [sibling(All', '):dc.Creator]}</td>

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 &#44;, things work as expected:

<td valign="top">[link][icon]link</td>

<td valign="top">[ex.equivDocLink][ex.equivDocIcon][ex./equivDocLink]</td>

<td valign="top">[highlight]

{Or}{[dc.Title],[exp.Title],[ex.Title],Untitled} highlight{If}{[dc.Creator],:[sibling(All'&#44; '):dc.Creator]}</td>

#838 fixed Demo collection improvement nobody davidb
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.

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.