That was it! Thank you very much.

Shawn

On Aug 12, 2014, at 1:03 PM, Luiz dos Santos <[email protected]> wrote:

> Hi,
> 
>    Did you already try to perform a clean OAI cache? 
> https://wiki.duraspace.org/display/DSDOC3x/OAI+2.0+Server#OAI2.0Server-OAIManager%28SolrDataSource%29
> 
> regards
> Luiz
> 
> 
> 
> Em 12/08/2014 12:45, "Shawn M. Kiewel" <[email protected]> escreveu:
> Nope, they’re displaying just fine. An example can be seen in the first link 
> I included.
> 
> Shawn
> 
> On Aug 12, 2014, at 12:42 PM, Luiz dos Santos <[email protected]> wrote:
> 
>> Hi shawn,
>>   in the xmlui, are you getting the same charset problem? 
>> regards
>> Luiz
>> 
>> Em 12/08/2014 12:17, "Shawn M. Kiewel" <[email protected]> escreveu:
>> I am running DSpace 3.2, using a modified Reference theme with xmlui, and 
>> have discovery enabled.
>> 
>> I am experiencing encoding issues with the OAI provider. Reference records:
>> 
>> http://athenaeum.libs.uga.edu/handle/10724/24086
>> http://athenaeum.libs.uga.edu/oai/request?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:ugakr.libs.uga.edu:10724/24086
>> 
>> I saw in the documentation that there are two common problems with encoding 
>> issues:
>> 
>> 1) servlet connector port has to use the correct encoding 
>> 
>> I have verified that the encoding is set in the JAVA_OPTS:
>> JAVA_OPTS="-Xmx1024M -Xms64M -XX:MaxPermSize=512M -Dfile.encoding=UTF-8 
>> -Xusealtsigs -XX:-UseConcMarkSweepGC"
>> 
>> 2) Ensure the locale is set for the script running the oai import; ensure 
>> the locale is installed
>> 
>> Existence:
>> $ locale -a
>> C
>> POSIX
>> en_CA
>> en_CA.ISO8859-1
>> en_CA.UTF-8
>> en_US
>> en_US.ISO8859-1
>> en_US.ISO8859-15
>> en_US.ISO8859-15@euro
>> en_US.UTF-8
>> es
>> es_MX
>> es_MX.ISO8859-1
>> es_MX.UTF-8
>> fr
>> fr_CA
>> fr_CA.ISO8859-1
>> fr_CA.UTF-8
>> iso_8859_1
>> 
>> I explicitly set the locale to en_US.UTF-8 and reimported everything.
>> 
>> dspace@ugakr:/home/dspace > export LANG=en_US.UTF-8
>> dspace@ugakr:/home/dspace > /dspace/prod/bin/dspace oai import -c
>>  INFO [main] (DSpaceKernelInit.java:52) - Created new kernel: 
>> DSpaceKernel:org.dspace:name=9ab102db-1257-4af3-8408-429bb3727acb,type=DSpaceKernel:lastLoad=null:loadTime=0:running=false:kernel=null
>>  INFO [main] (ConfigurationManager.java:1224) - Loading from classloader: 
>> file:/ds00/dspace/prod/config/dspace.cfg
>>  INFO [main] (ConfigurationManager.java:1224) - Using dspace provided log 
>> configuration (log.init.config)
>>  INFO [main] (ConfigurationManager.java:1224) - Loading: 
>> /dspace/prod/config/log4j.properties
>> OAI 2.0 manager action started
>> Clearing index
>> Index cleared
>> Using full import.
>> Full import
>> 100 items imported so far…
>> 
>> After reimport, encoding issues remain, as can be seen at above url.
>> 
>> Suggestions?
>> 
>> Thanks,
>> Shawn
>> 
>> ------------------------------------------------------------------------------
>> 
>> _______________________________________________
>> DSpace-tech mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>> List Etiquette: 
>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
> 
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette: 
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

------------------------------------------------------------------------------
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to