[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[EP-tech] Re: About compounds
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!
From: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Ian Stuart
Sent: 08 July 2014 16:04
To: eprints-tech at ecs.soton.ac.uk
Subject: [EP-tech] Re: About compounds
On 08/07/14 15:54, Gilles Fourni? wrote:
> 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
> Is it safe to do so ? Or are there risks to break something ?
Yes, adding extra fields is easy..... but only 1 level deep!
> 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 ?
I've not seen one.... not without writing your own rendering routines
(which are eminently doable..)
Developer: ORI, RJ-Broker, and OpenDepot.org
Bibliographics and Multimedia Service Delivery team,
The University of Edinburgh.
This email was sent via the University of Edinburgh.
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/