To close the problem I should say that there is no real issue with the non-ASCII characters and OAI.
But in XOAI there is conversion between String and byte array using the platform's default charset. Which is not always UTF-8. One can fix this starting Java/Tomcat with -Dfile.encoding=UTF8 One more thing I noticed now is that in some logs in dspace.log the non-ASCII characters are replaced by ?? To get the real non-ASCII characters one can add in log4j.properties log4j.appender.A1.encoding=UTF-8 On Thursday, October 19, 2017 at 9:04:39 PM UTC+3, Evgeni Dimitrov wrote: > > I have a freshly installed DSpace 6.2 with 15 items in it. > I have not changed anything in the OAI configuration. > Two of the items have READ access for certain groups only. The rest are > accessible to everybody. > > Problem 1. > When I run > dspace oai import -c > > I get in dspace.log two exceptions (I suppose for each of the restricted > access items): > > 2017-10-19 17:55:22,650 WARN org.dspace.xoai.util.ItemUtils @ > Authorization denied for action READ on > BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null > org.dspace.authorize.AuthorizeException: Authorization denied for action > READ on BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null > > The whole text of the exception is very long. > > Problem 2. > After that I am trying > http://localhost:8080/oai/request?verb=Identify > http://localhost:8080/oai/request?verb=ListSets > http://localhost:8080/oai/request?verb=ListMetadataFormats > http://localhost:8080/oai/request?verb=ListIdentifiers&metadataPrefix=xoai > and it all works. > > But for > > http://localhost:8080/oai/request?verb=GetRecord&identifier=oai:localhost:nls/3&metadataPrefix=xoai > (nls/3 is an item accessible to everybody) > I get in the browser > > java.io.IOException: > com.lyncode.xoai.dataprovider.exceptions.WritingXmlException: Error trying > to output '' > > org.dspace.xoai.services.impl.cache.DSpaceXOAICacheService.store(DSpaceXOAICacheService.java:113) > > The whole text of the exception is very long. > > My question is - am I missing something in the configuration or is this a > known problem with DSpace 6.2? > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free. > www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > > <#CAJc2bOxUdju=Fai5GKJ3-dgzeduhdrOkBUe-Hw7v=DPRxRj87w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
