<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Tim,<br>
<br>
I am facing some problems after applying the solution you proposed
(which are probably all rational, but need to be addressed
somehow):<br>
<br>
- First of all, for previous documents, the existing title is not
shown. Nor in the "Manage deposits" section, nor in "details"
section (view part). Of course it exists in the database
eprint.title field, but it's not showing anywhere else (I suppose
this is logical, since the system doesn't know which language to
display). Shouldn't all versions be displayed, as holds for other
multi-row fields?<br>
- When editing an existing record (or adding a new one), the title
field is now a multi-rows field (it asks me to add more rows,
where each row allows me to use a different language through a
drop-down menu). Whenever I fill it out and save, EPrints warns me
about not having filled it out (since it's "mandatory"). <br>
- On edit/add, after saving the value for a specific language,
it's not shown after it has been saved, so I'm not quite sure if
it has been saved in the database.<br>
- In which database field are the new-field values stored?<br>
<br>
Thanks for all the help so far!<br>
<br>
On 24/06/2015 10:29 πμ, Timothy Miles-Board wrote:<br>
</div>
<blockquote
cite="mid:EMEW3|d927969cc19d1af3eaa055e5248538b9r5N8Ye14eprints-tech-bounces|ecs.soton.ac.uk|c850a16d-d84a-48ba-b2e3-d19901b24eb6@email.android.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p dir="ltr">---------- Forwarded message ----------<br>
From: Timothy Miles-Board <a class="moz-txt-link-rfc2396E" href="mailto:timothy.miles-board@ulcc.ac.uk"><timothy.miles-board@ulcc.ac.uk></a><br>
Date: 18 Jun 2015 11:30 pm<br>
Subject: Re: [EP-tech] How to set a field to be multilang<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:eprints-tech@ecs.soton.ac.uk">eprints-tech@ecs.soton.ac.uk</a><br>
Cc: </p>
<blockquote>
<p dir="ltr">{<br>
name => 'title',<br>
type => 'multilang',<br>
multiple => 1,<br>
fields => [ { sub_name => "text", type =>
"longtext", input_rows => 3, make_single_value_orderkey
=> 'EPrints::Extras::english_title_orderkey' } ],<br>
input_add_boxes => 1,<br>
},<br>
</p>
</blockquote>
<p dir="ltr"><br>
Tim</p>
<div class="gmail_quote">On 23 Jun 2015 9:09 am, George Mamalakis
<a class="moz-txt-link-rfc2396E" href="mailto:mamalos@eng.auth.gr"><mamalos@eng.auth.gr></a> wrote:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><font size="2"><span style="font-size:10pt"></span></font>
<div>Guys (and girls),<br>
<br>
Any news on multilingual fields? Anybody using them?<br>
<br>
Thanks!<br>
<br>
George<br>
<br>
On 18/06/2015 06:31 μμ, George Mamalakis wrote:<br>
> Hello again,<br>
><br>
> I am trying to make my EPrints installation support
multilanguage fields<br>
> (eg. title, abstract, etc.). The thing I did that
worked (which doesn't<br>
> feel right to me, though) was adding a new Metadata
field (eg. title_en)<br>
> and add it to the database and workflow. On the
documentation, on the<br>
> other hand, I saw that there is a Multilang field
type<br>
> (./perl_lib/EPrints/MetaField/Multilang.pm) which
should be used for<br>
> this purpose. The strange thing is that its perldoc
DESCRIPTION section<br>
> starts with "not done", probably meaning that it's
not implemented?<br>
> Disregarding the last comment, when I changed<br>
> ./archives/myarchive/cfg/cfg.d/eprint_fields.pl title
field to read:<br>
><br>
> {<br>
> name => 'title',<br>
> type => 'multilang',<br>
> input_rows => 3,<br>
> make_single_value_orderkey =><br>
> 'EPrints::Extras::english_title_orderkey',<br>
> },<br>
><br>
> and I reloaded epadmin, I got the following error:<br>
><br>
> "Error in field property for eprint.title: fields on
a multilang<br>
> metafield can't be undefined"<br>
><br>
> So, which is the proper way for adding multilanguage
support in fields<br>
> and display them in workflows?<br>
><br>
> Thanks for all help in advance!<br>
><br>
<br>
<br>
-- <br>
George Mamalakis<br>
<br>
IT and Security Officer,<br>
Electrical and Computer Engineer (Aristotle Univ. of
Thessaloniki),<br>
PhD (Aristotle Univ. of Thessaloniki),<br>
MSc (Imperial College of London)<br>
<br>
School of Electrical and Computer Engineering<br>
Aristotle University of Thessaloniki<br>
<br>
phone number : +30 (2310) 994379<br>
<br>
<br>
<br>
*** Options: <a moz-do-not-send="true"
href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech">
http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a><br>
*** Archive: <a moz-do-not-send="true"
href="http://www.eprints.org/tech.php/">http://www.eprints.org/tech.php/</a><br>
*** EPrints community wiki: <a moz-do-not-send="true"
href="http://wiki.eprints.org/">http://wiki.eprints.org/</a><br>
*** EPrints developers Forum: <a moz-do-not-send="true"
href="http://forum.eprints.org/">http://forum.eprints.org/</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">*** Options: <a class="moz-txt-link-freetext" href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a>
*** Archive: <a class="moz-txt-link-freetext" href="http://www.eprints.org/tech.php/">http://www.eprints.org/tech.php/</a>
*** EPrints community wiki: <a class="moz-txt-link-freetext" href="http://wiki.eprints.org/">http://wiki.eprints.org/</a>
*** EPrints developers Forum: <a class="moz-txt-link-freetext" href="http://forum.eprints.org/">http://forum.eprints.org/</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
George Mamalakis
IT and Security Officer,
Electrical and Computer Engineer (Aristotle Univ. of Thessaloniki),
PhD (Aristotle Univ. of Thessaloniki),
MSc (Imperial College of London)
School of Electrical and Computer Engineering
Aristotle University of Thessaloniki
phone number : +30 (2310) 994379
</pre>
</body>
</html>