Language Issue in Repository Manager and T-REX

Question

Hi Everybody,
we are trying to implement a repository manager for SAP KM. Our systems stores documents language specific in a database. Now we are wondering how we should create a view to the documents, so that every document in each language is indexed by T-REX correctly. Lets say the internal view is something like this:
   /Documents
      ->File.pdf
  /Images
      ->Image.jpg
In this case File.pdf and Image.jpg can exist in different languages. So our question is, does T-REX create an index for each language available in the portal? If so, which would be very nice, how can we get the current language T-REX is using for indexing within our RM implementation?
Otherwise we have to create virtual TOP-Level laguage folders for each language in our database that would look like this
/de
   /Documents
      ->File.pdf
  /Images
      ->Image.jpg
/en
   /Documents
      ->File.pdf
  /Images
      ->Image.jpg
We try to avoid this, since File.pdf ist a single item with different language versions.
Does anybody know the best way to solve this?
Kind Regards,
Ali

Answer 1

Hi Matthias,
I think the language handling and the mapping of default languages is application specific and should be done within the RM. In our case this available allready, since our WCMS system allready take care about that... So for a logged in user, we are able to create a language specific folder structure very nicely.
Our problem is the indexing by TREX. We wan't to make sure that every language version of the docment can be found when people searching. So in our case the perfect solution would be that TREX asks the RM for available languages in the repository and starts a crawler for each language available in the repository.
Something that I am not sure about is the presentation of the search results. Since the URL of the search result might point to a different language version than the logged in user has. So if the URL is
http://server/irj/go/km/repsotory/Documents/File.pdf
this might result to a german document, even if the searched term is in the english document. So the language must be set in the search result. For example like this
http://server/irj/go/km/repsotory/Documents/File.pdf?locale=en
This would be our preferred way to handle this issue. I think we will keep the virtual language folders until the new feature is available.
Thank you guys for this very high quality answers )
Kind Regards,
Ali