<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<link href="chrome://translator/skin/floatingPanel.css"
type="text/css" rel="stylesheet">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<span id="result_box" class="" lang="en"><span class="hps">Thank you</span>
<span class="hps">all for your</span> <span class="hps">advice</span><span>.</span>
<span class="hps"><br>
I'll try your suggestions.<br>
<br>
Have a nice day</span><span>.<br>
Gilles<br>
<br>
<br>
</span></span>
<div class="moz-cite-prefix">Le 08/07/2014 17:19, Sebastien Francois
a écrit :<br>
</div>
<blockquote
cite="mid:EMEW3|3e20e3808180897d880295c2bd39838bq67GJ614eprints-tech-bounces|ecs.soton.ac.uk|53BC0C0C.8090005@ecs.soton.ac.uk"
type="cite">
<pre wrap="">It's true - in fact authors ("creators", "editors"...) should probably
point to a separate dataset and you could then use the modal thing I've
demo'ed.
But! Given how "creators" is hard-coded all over EPrints, you'll need to
rewrite big chunks of the core for this to work nicely.
I think the compromise solution is to use the "id" bit (so creators_id)
as a reference to another table. That other table can contain extra data
that describes the author.
The danger with adding too many sub-fields is that you're creating an
extra table per sub-field in the DB and as you've noticed, Gilles, this
won't work on workflow/submission form.
Seb.
On 08/07/14 16:14, John Salter wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I think that something that Seb demoed at the Eprints user group recently might be useful in this scenario...
*if* you had an author dataset, (similar to the 'user' dataset), you could store authors as dataobjrefs.
Seb's demo showed something similar for Projects/Funders - using a pop-up/modal window. It was very nice!
There has been previous discussion around the subject of richer data for authors - but I can’t remember any definite endpoint to those discussions!
Cheers,
John
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">eprints-tech-bounces@ecs.soton.ac.uk</a> [<a class="moz-txt-link-freetext" href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">mailto:eprints-tech-bounces@ecs.soton.ac.uk</a>] On Behalf Of Ian Stuart
Sent: 08 July 2014 16:04
To: <a class="moz-txt-link-abbreviated" href="mailto:eprints-tech@ecs.soton.ac.uk">eprints-tech@ecs.soton.ac.uk</a>
Subject: [EP-tech] Re: About compounds
On 08/07/14 15:54, Gilles Fournié wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
The library staff wants us to describe authors with many fields
(internal id number, department, unit, ...).
So we wonder if we can add subfields to existing compounds like creators
or editors.
Obviously, we would keep existing subfields unchanged and just add new
subfields.
Is it safe to do so ? Or are there risks to break something ?
</pre>
</blockquote>
<pre wrap="">Yes, adding extra fields is easy..... but only 1 level deep!
</pre>
<blockquote type="cite">
<pre wrap="">And, as a side question, I fear that a too big compound will be unusable
: in the input form, we will get a table with many columns, which will
probably be larger than the screen width. Is there a way to have the
subfields use several rows ?
</pre>
</blockquote>
<pre wrap="">I've not seen one.... not without writing your own rendering routines
(which are eminently doable..)
</pre>
</blockquote>
<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>
<div style="bottom: auto; left: 0px; right: auto; top: 54px;
display: none;" class="translator-theme-default"
id="translator-floating-panel">
<div title="Cliquer pour traduire"
id="translator-floating-panel-button"></div>
</div>
</body>
</html>