Re: [Dspace-tech] Question about metedata localizaton

2014-10-31 Thread Alex Dubiv
 Hi Helix84!
Thank you for quick reply!
I see there's no relatively  easy way to do it on our current 4.2 
installation ))
After some more searching I found a thread of  Kostas Stamatis  with similar 
problem. , I've contacted with him and got reply:
*
Dear Alex,
as helix mentioned in his reply, the pull request shown in  
https://github.com/DSpace/DSpace/pull/660  was to be included in DSpace 5.0 but 
we have cancelled the contribution because even if the code is working (as you 
can see from the demos) we haven’t included all the cases so it is somehow 
incomplete.
 
However, I think that in your case it suits very well. I also believe that even 
if it is build on top of the master branch, you can apply the patch to DSpace 
4.2 as well.
 
So, what you have to do actually is the following: go to  
https://github.com/DSpace/DSpace/pull/660/files  and see all the files that I 
have changed in order to accomplish the functionality. Do the same changes to 
your files, as well. The changes mention the line of code, but since it is 
build on top of master and not on top of 4.2, these lines can be slightly 
different. But do not expect radical changes.
 
After that go to  https://jira.duraspace.org/browse/DS-2163  and download the 
documentation to see how to configure the extension in order to achieve what 
you want.
 
Hope it helps.
***

So I will try to patch 4.2 in order to get functionality today.
Thank you all for help!

Thu, 30 Oct 2014 16:28:15 +0100 от helix84 heli...@centrum.sk:
Hi Alex,

you're raising valid concerns regarding localization. There was code
proposed to address that in DSpace 5 [1], unfortunately it was
postponed by the contributor for technical reasons, but we'll likely
see it reworked in DSpace 6. I also proposed an improvement to facets
which would include an ability to localize them (regardless of their
actual values, so that you could localize en_US to американський
англійський) in [2], but there is no implementation of that.

Apart from facets, it's desirable to localize Collection and Community
names. The foundation for this has been laid in DSpace 5 by [3], but
it's not yet represented in UI elements, to be addressed as the next
step.

In other words, we're slowly getting there. You can either wait for
DSpace 6 or chip in and submit a patch if you have Java skills.

[1]  https://jira.duraspace.org/browse/DS-2163
[2]  https://jira.duraspace.org/browse/DS-1141
[3]  https://jira.duraspace.org/browse/DS-1582


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

[Dspace-tech] Question about metedata localizaton

2014-10-30 Thread Alex Dubiv
 Greetings!

I'm new in DSpace but trying to get deeper into it.
My name is Alex and I'm from Ukraine - I managed to localize almost all parts 
of interface and forms of our Dspace installation.
But I have one critical question about data organization and translation.

In the input form of publication submission I've tried to extend the vocabolary 
of dc:type metadata field (file input-forms_uk.xml) to add different types op 
papers: Thesis of article, Full article, Report etc with their UA translations.
Then I've added in discovery.xml filters and facets configuration to that 
type field. It's works great - in input form of submission I see Ukrainian 
type names and facets are working really great.

BUT in facets and in search condition type VALUES are NOT translated - the are 
original - english (( 

What is the best solution to make facet values localized depending on chosen 
interface language?
I suppose I can hard-code UA-translated values into forms - but this will 
remove Dublin Core compatibility (I guess?..). In general it seems that I need 
to create some additional metadata field (dc:type should I guess describe type 
in sense of media: video,text, audio, presentation etc.)
At the end I need some kind of dc:publication_type which will describe 
different types of text publications and they must be localized depending on 
user language and be available in facets.

Thank you in advance!

--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette