Currently DSpace returns (through OAI) multi language fields as multiple 
fields with the same tag 

Practical example; I have an article with two descriptions, one in english 
and one in portuguese.
When I get this article's xml through OAI, i get the descriptions in the 
following format:

...
<description> Here be description</description>
<description> Here be portuguese description</description>
...

I believe this is problematic because it makes very difficult to detect the 
language of the field and harvest both (for example, VuFind only gets the 
first description. see [1]).

Also, please correct me if i'm wrong, but is a fault in DSpace on complying 
with Dublin Core guidelines, see Recommendation 9: 
*Where the language of the value is indicated, it should be encoded using 
the 'xml:lang' attribute.*From 
http://dublincore.org/documents/dc-xml-guidelines/.

I know that, by default, it's not obligatory to have a language field, but 
shouldn't be the case when you have fields with more than one language?

Can somebody confirm that? I was afraid that the problem was on VuFind 
side, i was looking at the article's xml returned from OAI stored in VuFind 
folders, but i believe thesse XMLs are exact ones returned by DSpace, and 
directly searching through DSpace OAI interface (dspacedomain/oai/request) 
gave me conffidence that its DSpace whos returning these XMLs.

[1]https://sourceforge.net/p/vufind/mailman/message/34785485/

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Reply via email to