Thank you Christian,
You may be right. But in my case it goes wrong before it comes to XML.
I am logging the SolrDocument before sending to Solr:
SolrInputDocument(fields: [item.id=ecc9c18e-4e91-4e7a-8e61-eb88472f8f0a,
item.public=true, item.handle=nls/3, item.lastmodified=2017-10-16
23:18:01.117, item.submitter=e...@nomail.xx, item.deleted=false,
item.collections=col_nls_2, item.communities=com_nls_1,
metadata.dc.coverage.spatial=София, България,
metadata.dc.creator=Карастоянов, Д.,
I am logging the SolrDocument after Solr returns it:
SolrDocument{item.id=ecc9c18e-4e91-4e7a-8e61-eb88472f8f0a,
item.public=true, item.handle=nls/3, item.lastmodified=Mon Oct 16 23:18:01
EEST 2017, item.submitter=e...@nomail.xx, item.deleted=false,
item.collections=[col_nls_2], item.communities=[com_nls_1],
metadata.dc.coverage.spatial=[?????, ????????],
metadata.dc.creator=[???????????, ?.],
I tried querying Solr from my own standalone application - same way as
DSpace does - same version of the Solr client - the result is as above.
Finally I am querying Solr from the browser and I am getting a correct
response:
<arr name="metadata.dc.coverage.spatial"><str>София,
България</str></arr><arr name="metadata.dc.creator"><str>Карастоянов,
Д.</str></arr>
Which makes me think that there is a problem with the Solr client - either
configuration missing or something wrong in this exactly version.
On Tuesday, October 24, 2017 at 8:58:19 AM UTC+3, Christian Scheible wrote:
>
> Hi together,
>
> we are currently investigating the same problem.
> It's because there are non valid XML 1.0 Characters in the metadata (like
> surrogate pairs).
>
> This block explains it and shows a method how to get rid of them:
>
>
> http://blog.mark-mclaren.info/2007/02/invalid-xml-characters-when-valid-utf8_5873.html
>
> If I have time I am going to make a pull request for this issue.
>
> Hope this helps
> Christian
>
> Am 23.10.2017 um 22:20 schrieb Evgeni Dimitrov:
>
> The problem with
>
>
> http://localhost:8080/oai/request?verb=GetRecord&metadataPrefix=xoai&identifier=oai:localhost:nls/3
>
> not working is related to metadata with non-ASCII characters. The strange
> thing is that the added log shows that DSpace gets with SolrServer.query()
> the metadata with the non-ASCII characters distorted. But when Solr is
> queried in the browser:
>
> http://localhost:8080/solr/oai/select?q=item.handle:nls/3
>
> then the non-ASCII characters are correct. I can not figure out why . . .
>
>
> 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>
>>
>>
> --
> 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...@googlegroups.com <javascript:>.
> To post to this group, send email to dspac...@googlegroups.com
> <javascript:>.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
--
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.
