Hello Urban, A simple and quick solution to the bilingually issue of collections/ communities in DSpace is to use a delimiter, like the bar | , in between two text describing these entities and their metadata fields as needed. All is required is to split the text at viewing time so that only the text in the currently active is displayed.
Here you will see the Arabic version of the communities/collections list: https://repo-nu.maktabat-online.com/community-list Now switch the language to the English interface, using the world icon on top, and you will see them all appear in English. The same approach has been applied to the facets elements, where now see controlled values like names of formats/ types, universities/ colleges/ departments, entities, etc. in multiple languages. Thanks, Massoud KnowledgeWare Sent from my iPhone > On 4 Oct 2022, at 2:20 PM, Urban Andersson <[email protected]> wrote: > > I believe this is the way to go! It would also be a sustainable solution, > since you could also add more/new languages when needed, and there would be > no changes to the backend/data model. And I presume the default lang > specified would be used when there (for some reason) is no match. > > / Urban > >> måndag 3 oktober 2022 kl. 17:14:21 UTC+2 skrev [email protected]: >> On Mon, Oct 03, 2022 at 07:21:31AM -0700, [email protected] wrote: >> > Bonjour, >> > >> > I agree that this is a limitation in DSpace. As collection and community >> > are items in DSPace (and thus have there own metadata), maybe a way to >> > solve this problem would be to allow language selections at the metadata >> > level, like it could be done already for objects metadata (i.e abstracts). >> > For collections, it would look like this: >> > [image: dspace-multilingual-collection-metadata.png] >> > What do you think of this avenue to solve the problem? >> > >> > There is already an issue for this on Github dspace-angular >> > repository: https://github.com/DSpace/dspace-angular/issues/1464. We could >> > build on it. >> > >> > Thanks! >> > >> > Pierre Lasou >> > Université Laval >> > >> > >> > On Friday, September 30, 2022 at 5:22:08 AM UTC-4 [email protected] wrote: >> > >> > > Not being able to use language controlled community and collection names >> > > has always (I think) been a major limitation in DSpace. In earlier (JSP) >> > > versions we solved this by using a workaround, similar to this: >> > > https://groups.google.com/g/dspace-community/c/6dwt-gjVPTo >> > > but this seems not quite as easy to accomplish in Angular. >> > > >> > > Has anyone else had a look at this, and are there any suggestions on how >> > > to approach it? >> > > Either by manipulating the app source or the data that is returned by >> > > the >> > > backend? I'd rather not write a new extension, but maybe this is the >> > > only >> > > way? >> > > >> > > Also, it would be nice if introductory texts (HTML) etc. of >> > > communities/collections could be presented in multiple languages. This >> > > could quite easily be accomplished by using CSS and named divs. But >> > > unfortunately html attributes, such as id and style, seem to be removed >> > > in >> > > the html output - i.e. <div id="swedish">text</div> is transformed to >> > > <div>text</div> in the UI. Or maybe I am doing something wrong here? >> > > >> > > Any thoughts or suggestions would be very welcome! If someone is already >> > > working on this I'd be happy to help out if I can. >> > > >> > > Urban Andersson >> > > Chalmers University of Technology >> >> Do you mean that the community and collection names should be >> presented to the user in the best available match to user's requested >> locale? That should not be difficult to implement, since these names >> are the values of the corresponding 'dc.title' metadata rows for those >> objects, and metadata fields can have multiple values with different >> locales. >> >> Many other features of Collection are stored in metadata: >> >> o Introductory text: dc.description >> o Short Description: dc.description.abstract >> o Copyright text: dc.rights >> o License: dc.rights.license >> >> I haven't found where News is stored. >> >> -- >> Mark H. Wood >> Lead Technology Analyst >> >> University Library >> Indiana University - Purdue University Indianapolis >> 755 W. Michigan Street >> Indianapolis, IN 46202 >> 317-274-0749 >> www.ulib.iupui.edu > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-community/ff6dc936-4feb-4af8-ba88-daeeed131e02n%40googlegroups.com. -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/F3A6FD64-A3D7-4420-98DC-4726FC3E4C55%40kwareict.com.
