Folks

I'm testing CRIS Dspace distro and have a couple of doubts:

1. Is there a way to avoid chinese name for researchers? At the same time,
I need to delete it from browse options.

Simply go to administer -> CRIS Module -> Researchers Pages -> Layout 
configuration (Group metadata) and select the box where the chinese name is, now you can 
hide it or delete it.

2. I've inserted an item into an specific collection, can access to the
researchers without problem and access to their personal profiles from the
item view, but if I browse this collection by researcher appears that there
is no Entry in this index. It's odd because if I browse the entire
repository by researcher appears all the registered researchers and if I
click, access to personal bio with publications and projects.

It never worked for me too, neither 3.2 nor 4.1.1


3. About i18n, I encountered some contradictory information about where to
put messages file in JSPUI, inside META-INF or inside WEB-INF/classes? BTW,
I've seen that some parts of CRIS could not be internationalized, isn't it?
I mean for instance, I could change legends

INSERT INTO "public"."cris_ou_pdef" VALUES ('1000', '1', 'f', '70', 'em',
'em',  '0', null, 'Director', '0', 'em', 't', 'f', 'f', '800', 'f',
'director', 'f', 'f', '1000');
INSERT INTO "public"."cris_ou_pdef" VALUES ('1050', '3', 'f', '70', 'em',
'em',  '3', null, 'Organization name', '0', 'em', 't', 'f', 'f', '999',
'f', 'name', 'f', 'f', '1050');
INSERT INTO "public"."cris_ou_pdef" VALUES ('1651', '1', 'f', '70', 'em',
'em',  '0', null, 'Parent OrgUnit', '0', 'em', 'f', 'f', 'f', '700', 'f',
'parentorgunit', 'f', 'f', '1651');
INSERT INTO "public"."cris_ou_pdef" VALUES ('1652', '1', 'f', '0', 'em',
'em',  '0', null, 'Scientifics Board', '0', 'em', 'f', 'f', 'f', '10', 't',
'boards', 'f', 'f', '1652');
INSERT INTO "public"."cris_ou_pdef" VALUES ('1653', '1', 'f', '0', 'em',
'em',  '3', null, 'Established', '0', 'em', 'f', 't', 'f', '40', 'f',
'date', 'f', 'f', '1653');
INSERT INTO "public"."cris_ou_pdef" VALUES ('1700', '1', 'f', '0', 'em',
'em', '0', null, null, '0', 'em', 'f', 'f', 'f', '0', 'f', 'description',
'f', 'f', '1700');
INSERT INTO "public"."cris_ou_pdef" VALUES ('1701', '1', 'f', '15', 'em',
'em',  '13', null, null, '0', 'em', 'f', 'f', 'f', '1000', 'f', 'logo',
'f', 'f', '1701');

To spanish, but anyway there is no way to maintain both languages. Or I'm
wrong?

I don't really know if there are some parts that cannot be translated in order 
to set different languages, but the labels you mentionedspecifically  seems to 
be loaded from the database  so without doing something extra it wouldn't work.
About the path of the language file... this module doesn't use i18, it uses 
Messages.properties because is JSP interface, this file is located in the 
source of dspace 
in|[dspace-source]/dspace-api/src/main/resources/Messages.properties|
You can modify it or add another one for spanish language, and you have to 
recompile to see changes (I know, it's a pain in the ass...)

Thanks a lot for the help
Regards
Germán



------------------------------------------------------------------------

Pablo Buenaposada

Tècnic de Càlcul i Aplicacions

Consorci de Serveis Universitaris de Catalunya (CSUC)

Gran Capità, 2 (Edifici Nexus) ?08034 Barcelona

T. 93 551 6220 ?F. 93 205 6979 [email protected]

www.csuc.cat ?Twitter @CSUC_info ?Facebook ?Linkedin

Subscriu-te al butlletí (www.csuc.cat/butlleti)

------------------------------------------------------------------------
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to